> > To explain further what I am trying to do on shutdown. > > Some of the data I will store to Hazelcast will be instance specific data > (e.g. for example who is connected to the current karaf instance). This > immediately becomes invalid if the karaf instance shuts down (as a user > cannot be connected to a karaf instance that isn't running). > > Any users of this instance-specific data will, of course, need to check > somehow whether this data is invalid (since the specific karaf instance may > shutdown abnormally, by a "kill -9" or a power loss). However, it would be > nice on a clean shutdown to be able to make sure all the specific instance > data is cleared. One way to clear it is to clean it out is to delete > invalid > entries in Activator.stop. But to do this the Hazelcast instance would > still > need to be active at that time (which I am finding is not always the case). > > Does this make sense? What do you think? >
Hazelcast provides member listeners, that will be trigger when a member joins or leaves the cluster. Maybe they could help you with that. -- *Ioannis Canellos* * FuseSource <http://fusesource.com> ** Blog: http://iocanel.blogspot.com ** Apache Karaf <http://karaf.apache.org/> Committer & PMC Apache ServiceMix <http://servicemix.apache.org/> Committer Apache Gora <http://incubator.apache.org/gora/> Committer *
