It would be great if you could share your use case with us for the
cluster wide singleton as we have not seen much demand for such a service.
If there is sufficient interest, we can look to implementing it or seek
community contributions for it.
Re: easy for someone familiar with Shoal : I suspect the devil is in the
details.
We have never tried doing a clusterwide singleton nor have we thought
about the intricate syncronization issues that may come up such as
timing of calls to appoint a singleton particularly at cluster startup
when the group is just forming and list of members is in flux - so I'd
hesitate to share code snippets without actually spending some time
thinking about the set of use cases a singleton service is expected to
solve while taking into account support of such cases as network splits
with a predictable algo.
Having some use cases from the community members as you have started
would help us a lot.
--Shreedhar
On 3/22/11 10:12 AM, forums_at_java.net wrote:
> Joe, thanks for your reply, I know it doesn't 'support' it out of the
> box.
> JBoss has a facility, for example, a cluster barrier, that makes it
> easy to
> deploy cluster-wide singleton on JBoss. I just migrated from JBoss to
> Glassfish, and in need of similar functionality. I know it's fairly
> easy for
> someone familiar with Shoal/Glassfish to at least give me hints on how to
> develop this. Also, its a great value add, IMHO, and very useful.
>
> --
>
> [Message sent by forum member 'lprimak']
>
> View Post: http://forums.java.net/node/783542
>
>