[GEODE-10009] The CacheClientProxy for a durable client can be terminated when it shouldn't be

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.15.0
• Fix Version/s: 1.15.0
• Component/s: client queues
• Labels: blocks-1.15.0​ pull-request-available
• Assignee: Barrett Oglesby
• Reporter: Barrett Oglesby
• Created: 01/Feb/22 22:49
• Updated: 22/Jun/22 20:46
• Resolved: 08/Feb/22 18:07

Description

When the client connection is closed but the server has not left or crashed (e.g in the re-authentication failed case), its possible that two threads in a durable client can interleave in a way that causes an extra durable task to be created on the server that eventually causes the CacheClientProxy to be terminated.

Issue Links

• links to: GitHub Pull Request #7332