[GEODE-9295] entry idle expiration threads may hang

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.13.0, 1.13.1, 1.13.2, 1.13.3, 1.14.0, 1.15.0
• Fix Version/s: 1.12.4, 1.13.3, 1.14.0, 1.15.0
• Component/s: expiration
• Labels: pull-request-available
• Assignee: Darrel Schneider
• Reporter: Darrel Schneider
• Created: 20/May/21 20:39
• Updated: 28/Feb/22 18:36
• Resolved: 21/May/21 20:27

Description

GEODE-7921 in 1.13 introduced this issue. When processing a message used by entry idle expiration to find out when an entry was last accessed on any member of the cluster it now checks for a null cache, region, and entry. If any of them are null the message simply returns. The problem is that the expiration thread that sent this message waits forever for a reply. So unless the member that found a null leaves the cluster, the expiration thread will be hung waiting for a reply that will never be sent.

The fix for this is easy. We just need to send a reply of zero when we find a null.

Issue Links

• is caused by: GEODE-7921 NullPointerExceptions logged during auto-reconnect
• links to: GitHub Pull Request #6503
• links to: GitHub Pull Request #6613