?Hi,
So I think we found it: 1. For EVT_NODE_SEGMENTED, I think it is a "discovery event" and we register a listener on the tcp discovery component of the ignite configuration. 2. For other events, Ignite offer possibility to listen to local or remote events, at Ignite (global) level or at cache level. Met vriendelijke groeten/Meilleures salutations/Best regards Nicolae Marasoiu Agile Developer E [email protected]<mailto:[email protected]> [http://signature.cegeka.com/mailsignature_cgk.png] CEGEKA * 15-17 Ion Mihalache Blvd. Tower Center Building, 4th,5th,6th fl * RO-011171 Bucharest (RO) * T +40 21 336 20 65 * www.cegeka.com Volg Cegeka: [http://signature.cegeka.com/twitter.png] <http://www.twitter.com/cegeka> [http://signature.cegeka.com/linkedin.png] <http://www.linkedin.com/company/cegeka> [http://signature.cegeka.com/facebook.png] <http://www.facebook.com/Cegeka> [http://signature.cegeka.com/google-plus.png] <http://www.cegeka.be/googleplus> ________________________________ De la: Marasoiu Nicolae Trimis: 2 septembrie 2016 16:20 Către: [email protected] Subiect: Re: how to automatically exit JVM when the node stops? Hi Kamal, It seems that the only events available on the lifecycle (the classes you mentioned e.g. LifecycleBean and LifecycleEventType) are those of "node started" and "node stopped". There must other classes of events and event handlers for the case of segmentation and other events. Ignite has both messages and events, we are not sure what this would be either (message or event; local or remote). Thank you, Nicu Met vriendelijke groeten/Meilleures salutations/Best regards Nicolae Marasoiu Agile Developer E [email protected]<mailto:[email protected]> [http://signature.cegeka.com/mailsignature_cgk.png] CEGEKA * 15-17 Ion Mihalache Blvd. Tower Center Building, 4th,5th,6th fl * RO-011171 Bucharest (RO) * T +40 21 336 20 65 * www.cegeka.com Volg Cegeka: [http://signature.cegeka.com/twitter.png] <http://www.twitter.com/cegeka> [http://signature.cegeka.com/linkedin.png] <http://www.linkedin.com/company/cegeka> [http://signature.cegeka.com/facebook.png] <http://www.facebook.com/Cegeka> [http://signature.cegeka.com/google-plus.png] <http://www.cegeka.be/googleplus> ________________________________ De la: Kamal C <[email protected]> Trimis: 30 august 2016 13:35 Către: [email protected] Subiect: Re: how to automatically exit JVM when the node stops? Implement the Ignite LifeCycleBean [1] and stop the JVM on receiving the event [2] [1]: https://ignite.apache.org/releases/mobile/org/apache/ignite/lifecycle/LifecycleBean.html [2]: https://ignite.apache.org/releases/mobile/org/apache/ignite/lifecycle/LifecycleEventType.html#AFTER_NODE_STOP -- Kamal On Tue, Aug 30, 2016 at 3:31 AM, vkulichenko <[email protected]<mailto:[email protected]>> wrote: Hi, I don't think there is a generic solution for cases when an Ignite node is embedded into other application. You will always need to figure out what to do with other components of this application. You can listen to Ignite events (e.g., EVT_NODE_SEGMENTED) and act accordingly in the listener. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/how-to-automatically-exit-JVM-when-the-node-stops-tp7372p7389.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
