[
https://issues.apache.org/jira/browse/ARIES-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18077436#comment-18077436
]
ASF subversion and git services commented on ARIES-2200:
--------------------------------------------------------
Commit dd72c2818baeb17eb6205ba67090335759a200f5 in aries-rsa's branch
refs/heads/dependabot/maven/jakarta.ws.rs-jakarta.ws.rs-api-4.0.0 from Amichai
Rothman
[ https://gitbox.apache.org/repos/asf?p=aries-rsa.git;h=dd72c281 ]
ARIES-2200 Fix ZooKeeper concurrency issue that may close the wrong client
> ZooKeeper discovery concurrency issue may close the wrong client
> ----------------------------------------------------------------
>
> Key: ARIES-2200
> URL: https://issues.apache.org/jira/browse/ARIES-2200
> Project: Aries
> Issue Type: New Feature
> Components: Remote Service Admin
> Affects Versions: rsa-1.16.1
> Reporter: Amichai Rothman
> Priority: Major
> Fix For: rsa-2.0.0
>
>
> The ZooKeeper discovery's ClientManager.stop() method calls
> zkClient.close() asynchronously, where zkClient is an instance field.
> However, by the time the async task runs, this reference could have already
> been replaced with a new client instance, e.g. in ClientManager.process
> handling of expired sessions which calls stop and immediately afterwards
> creates a new client. In such a case the close() call could inadvertently be
> invoked on the new client thus making it unusable, while leaving the old
> client unclosed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
