Hi Shazni, I have updated the code with aforesaid changes in my git fork [1]<https://github.com/amalhub/carbon4-kernel/commit/7d1711a6de7ebf04e22ec1e9634e88088b954c4f> . Please run the tests on your clustered setup.
[1] https://github.com/amalhub/carbon4-kernel/commit/7d1711a6de7ebf04e22ec1e9634e88088b954c4f Thank you & Best regards, *Amal Gunatilake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware On Tue, May 13, 2014 at 4:30 PM, Amal Gunatilake <am...@wso2.com> wrote: > Hi All, > > Following updates has been discussed on $subject. > > 1) The isCoordinator check is not necessary for publishing the cache > invalidation message. > 2) Separate the implementation of publisher and subscriber into 2 classes. > 3) Alter the implementation to support, when the isCoordinator node goes > down; the next coordinator node should get auto subscribe to the topic. > > The 3rd point was discussed to implement as follows: > > The osgi service implementation bundle will be present at all nodes. So it > will check whether "Am I the coordinator?" in a given time interval (This > time interval can be configured in cache.xml). When one node goes down then > the next coordinator will become the coordinator. At this point "Am I the > coordinator?" will get the response and it will subscribe it-self to the > topic. > > Please update the thread if there are any further updates. > > Thank you & Best regards, > > *Amal Gunatilake* > Software Engineer > WSO2 Inc.; http://wso2.com > lean.enterprise.middleware >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
