Yes i fixed same in some other places as well. I think it is better to check in the memberRemoved() and memberAdded() so it will cover most of the other scenarios as well.
Thanks On Thu, Sep 26, 2013 at 9:53 AM, Afkham Azeez <[email protected]> wrote: > > On Thu, Sep 26, 2013 at 9:49 AM, Ajith Vitharana <[email protected]> wrote: > >> ntask > > > The ntask ClusterGroupCommunicator.isLeader code has to be changed to > first check whether the Hazelcast lifecycle service is active before > calling into Hazelcast > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **[email protected]* <[email protected]>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > -- *Shelan Perera* Senior Software Engineer ** Integration Technology Group *WSO2, Inc. : wso2.com* lean.enterprise.middleware. *Blog* : blog.shelan.org *Linked-i*n : http://www.linkedin.com/pub/shelan-perera/a/194/465 *Twitter* : https://twitter.com/#!/shelan *Mobile* : +94 772 604 402
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
