[
https://issues.apache.org/jira/browse/CURATOR-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910475#comment-17910475
]
Kezhu Wang commented on CURATOR-529:
------------------------------------
I found more: {{reconfig}}, {{getConfig}}, {{watches}} and {{watchers}}.
I think we should either enforce {{checkState}} consistently or make
{{inBackground}} operation background and never throw synchronously. The later
probably require major refactor. So I would prefer to enforce {{checkState}} to
all zk operations.
> Sync with inBackground doesnt complete if curator client is closed
> -------------------------------------------------------------------
>
> Key: CURATOR-529
> URL: https://issues.apache.org/jira/browse/CURATOR-529
> Project: Apache Curator
> Issue Type: Bug
> Components: Client, Framework
> Affects Versions: 4.0.1
> Environment: Version: 4.0.1
> Platform: linux
> Subsystem: ubuntu
> Reporter: shivesh
> Priority: Major
>
> Calling sync with a callback on a closed client doesnt fail synchronously.
> Nor is the callback invoked with failure details.
> Following is the code snippet to reproduce the issue:
> {quote}client.close();
> client.sync().inBackground(callback, executor).forPath(path);
> {quote}
>
> This works correctly for other api calls like `getData` etc where the call
> fails synchronously.
> Expected Behaviour:
> Callback should have been called with IllegalStateException or any other
> appropriate failure. Or attempt to call sync on a closed client should have
> failed synchronously. But neither does the api fail nor is the callback
> invoked unlike it is for all other types of calls.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
