Details
-
Bug
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
3.3.1
-
None
-
Reviewed
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.
Attachments
Attachments
Issue Links
- is related to
-
ZOOKEEPER-954 Findbugs/ClientCnxn: Bug type JLM_JSR166_UTILCONCURRENT_MONITORENTER
- Patch Available
-
ZOOKEEPER-835 Refactoring Zookeeper Client Code
- Open