Igor, thanks for looking into this. Even if the root cause is on an application end, our code mustn't generate an NPE.
Ignite dev community and *Ivan Rakov* in particular, have you seen this before? Should we file a ticket or the issue has already been resolved? - Denis On Wed, Jul 24, 2019 at 7:19 AM Игорь Беляков <igor.belyako...@gmail.com> wrote: > Hi, > > According to the logs I see that you've an issue with JVM pauses and nodes > disconnection, seems like it is a cause of the problem. Are you able to > reproduce this issue? > Also log contains data only for the last 15 seconds and for 1 node, could > you please provide full logs from all nodes in the cluster for futher > investigation? > > Regards, > Igor > > On Tue, Jul 23, 2019 at 6:02 PM Mahesh Renduchintala < > mahesh.renduchint...@aline-consulting.com> wrote: > >> Hi, >> >> >> We are seeing a null pointer exception in Ignite server node. >> >> >> java.lang.NullPointerException >> at >> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.latch.ExchangeLatchManager.canSkipJoiningNodes(ExchangeLatchManager.java:327) >> at >> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1401) >> at >> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:806) >> at >> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2667) >> at >> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2539) >> at >> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120) >> at java.lang.Thread.run(Thread.java:745) >> >> Please see attached. >> >> >> >> >> is there a known bug around this? >> >> >> regards >> >> Mahesh >> >
