You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Eric Shu (Jira)" <ji...@apache.org> on 2020/01/17 23:00:06 UTC

[jira] [Created] (GEODE-7725) AbstractGatewaySender.getSynchronizationEvent should be able to handle region is null case

Eric Shu created GEODE-7725:
-------------------------------

             Summary: AbstractGatewaySender.getSynchronizationEvent should be able to handle region is null case
                 Key: GEODE-7725
                 URL: https://issues.apache.org/jira/browse/GEODE-7725
             Project: Geode
          Issue Type: Bug
          Components: wan
            Reporter: Eric Shu


Currently NPE could be thrown:

java.lang.NullPointerException
	at org.apache.geode.internal.cache.wan.AbstractGatewaySender.getSynchronizationEvent(AbstractGatewaySender.java:1471)
	at org.apache.geode.internal.cache.wan.GatewaySenderQueueEntrySynchronizationOperation$GatewaySenderQueueEntrySynchronizationMessage.getSynchronizationEvents(GatewaySenderQueueEntrySynchronizationOperation.java:233)
	at org.apache.geode.internal.cache.wan.GatewaySenderQueueEntrySynchronizationOperation$GatewaySenderQueueEntrySynchronizationMessage.process(GatewaySenderQueueEntrySynchronizationOperation.java:201)
	at org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:372)
	at org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:436)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at Rjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:475)
	at org.apache.geode.distributed.internal.ClusterOperationExecutors.doProcessingThread(ClusterOperationExecutors.java:406)
	at org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:119)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)