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

Patrick Hunt updated ZOOKEEPER-794:
-----------------------------------

         Assignee: Alexis Midon
    Fix Version/s: 3.3.2
                   3.4.0
      Description: 
I noticed that ZooKeeper has different behaviors when calling synchronous or 
asynchronous actions on a closed ZooKeeper client.
Actually a synchronous call will throw a "session expired" exception while an 
asynchronous call will do nothing. No exception, no callback invocation.

Actually, even if the EventThread receives the Packet with the session expired 
err code, the packet is never processed since the thread has been killed by the 
ventOfDeath. So the call back is not invoked.



  was:

I noticed that ZooKeeper has different behaviors when calling synchronous or 
asynchronous actions on a closed ZooKeeper client.
Actually a synchronous call will throw a "session expired" exception while an 
asynchronous call will do nothing. No exception, no callback invocation.

Actually, even if the EventThread receives the Packet with the session expired 
err code, the packet is never processed since the thread has been killed by the 
ventOfDeath. So the call back is not invoked.




> Callbacks are not invoked when the client is closed
> ---------------------------------------------------
>
>                 Key: ZOOKEEPER-794
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-794
>             Project: Zookeeper
>          Issue Type: Bug
>          Components: java client
>    Affects Versions: 3.3.1
>            Reporter: Alexis Midon
>            Assignee: Alexis Midon
>             Fix For: 3.3.2, 3.4.0
>
>         Attachments: ZOOKEEPER-794.patch.txt, ZOOKEEPER-794.txt
>
>
> I noticed that ZooKeeper has different behaviors when calling synchronous or 
> asynchronous actions on a closed ZooKeeper client.
> Actually a synchronous call will throw a "session expired" exception while an 
> asynchronous call will do nothing. No exception, no callback invocation.
> Actually, even if the EventThread receives the Packet with the session 
> expired err code, the packet is never processed since the thread has been 
> killed by the ventOfDeath. So the call back is not invoked.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to