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

["Barrett Oglesby (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/GEODE-10009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Barrett Oglesby resolved GEODE-10009.
-------------------------------------
    Fix Version/s: 1.15.0
       Resolution: Fixed

> The CacheClientProxy for a durable client can be terminated when it shouldn't be
> --------------------------------------------------------------------------------
>
>                 Key: GEODE-10009
>                 URL: https://issues.apache.org/jira/browse/GEODE-10009
>             Project: Geode
>          Issue Type: Bug
>          Components: client queues
>    Affects Versions: 1.15.0
>            Reporter: Barrett Oglesby
>            Assignee: Barrett Oglesby
>            Priority: Major
>              Labels: blocks-1.15.0​, pull-request-available
>             Fix For: 1.15.0
>
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)