[GEODE-7921] NullPointerExceptions logged during auto-reconnect

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.13.0
• Component/s: membership
• Assignee: Bruce J Schuchardt
• Reporter: Bruce J Schuchardt
• Created: 27/Mar/20 20:50
• Updated: 28/Feb/22 18:36
• Resolved: 03/Apr/20 15:25

Description

In a test with disable-tcp=true I found a huge number of NPEs logged when a server auto-reconnected.

[fatal 2020/03/25 15:26:57.136 PDT <Pooled Message Processor 2> tid=0x17f] Uncaught exception processing LatestLastAccessTimeMessage@546d3459 processorId=0 sender=rs-FullRegression25213428a3i32xlarge-hydra-client-22(gemfire3_host1_32677:32677)<ec><v5>:41009
java.lang.NullPointerException
        at org.apache.geode.internal.cache.LatestLastAccessTimeMessage.process(LatestLastAccessTimeMessage.java:66)
        at org.apache.geode.distributed.internal.DistributionMessage.scheduleAction(DistributionMessage.java:376)
        at org.apache.geode.distributed.internal.DistributionMessage$1.run(DistributionMessage.java:440)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at org.apache.geode.distributed.internal.ClusterOperationExecutors.runUntilShutdown(ClusterOperationExecutors.java:442)
        at org.apache.geode.distributed.internal.ClusterOperationExecutors.doProcessingThread(ClusterOperationExecutors.java:389)
        at org.apache.geode.logging.internal.executors.LoggingThreadFactory.lambda$newThread$0(LoggingThreadFactory.java:119)
        at java.base/java.lang.Thread.run(Thread.java:834)

These came from a queue of messages built up by the QuorumChecker that were processed before a new cache was built. The QuorumChecker shouldn't be queueing cache operations. It only needs to queue membership messages.

Issue Links

• causes: GEODE-9295 entry idle expiration threads may hang
• links to: GitHub Pull Request #4898