Your examples seems correct to me. 1. What does it mean by "goes null"? 2. I do not see any assignments other than instantiation in init() method. 3. You confirm that service worked OK on some node but after some time with no topology changes it starts to throw NPE, correct? Can you please share the stack trace? Maybe it can reveal some details we missing now.
--Yakov 2016-04-06 3:10 GMT+03:00 dstieglitz <dstiegl...@stainlesscode.com>: > Following up on this... > > Sorry for the vague description of the problem, but we are experiencing > objects "going null" (as if they were garbage collected?) in our clustered > singleton. > > We have an instance variable of an object that is initialized in the > service > init() method. We have confirmed that on topology change, the object is > properly re-initialized. However, after some period of time, for example, > overnight, the object "goes null." > > Are we doing this correctly? Should we store the object in the cluster? > > The schedule class is here: > > https://github.com/dstieglitz/grails-ignite/blob/v0.4.x/src/java/org/grails/ignite/DistributedSchedulerServiceImpl.java > > The object in question is the "DistributedScheduledThreadPoolExecutor" > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Behavior-of-init-for-clustered-singleton-tp3819p3944.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
