Hi Vinay, Thanks for provided description. But I am afraid it is too broad for us to start investigation, because there are lots similar cases when all works fine. Though, the problem you faced seems pretty serious to me and we definitely need to find the root cause.
Can we expect more assistance from your side with it? Any more hints - XML configuration, simplified code sample to reproduce the issue, etc. are appreciated. Vladimir. On Fri, Feb 19, 2016 at 6:32 PM, vinshar <[email protected]> wrote: > Thanks for workaround Vladimir. I am using multiple caches. Each cache has > key as long and value are POJOs. One is Program Cache of type <Long, > ProgramDto> and similar other caches exists. All had this problem. All > these > value classes are simple POJOs which implement serializable, does not > override any of Object classes methods (equals, hashcode, toString etc) and > have class attributes of type - long, String, Boolean, java.sql.Timestamp > with getter setter methods. All classes do have auto generated "private > static final long serialVersionUID " > > I also thought of a workaround of having a MBean which ,out of many other > tasks, can also restart encapsulated Ignite instance in my custom cache > manager. I landed in a issue there which i will share in a separate > thread. > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/changed-cache-configuration-and-restarted-server-nodes-Getting-exception-tp3064p3100.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
