[
https://issues.apache.org/jira/browse/CURATOR-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
shivesh updated CURATOR-529:
----------------------------
Description:
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:
{\{client.close(); }}
{\{client.sync().inBackground(callback, executor).forPath(path); }}
This works correctly for other api calls like `getData` etc.
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.
was:
Calling sync with a callback on a closed client doesnt fail synchronously. Nor
is the callback invoked with failure details.
{{client.close(); }}
{{client.sync().inBackground(callback, executor).forPath(path); }}
Callback should have been called with IllegalStateException or any other
appropriate failure. But the callback should be invoked just like it is for all
other types of calls.
> 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:
> {\{client.close(); }}
> {\{client.sync().inBackground(callback, executor).forPath(path); }}
>
> This works correctly for other api calls like `getData` etc.
> 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
(v7.6.3#76005)
