[
https://issues.apache.org/jira/browse/ZOOKEEPER-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Spycher updated ZOOKEEPER-126:
---------------------------------------
Attachment: ZOOKEEPER-126.patch
The latest attachment works for 3.4. It uses a latch and timeout to prevent
blocking -- not sure if we require ZK to work on JREs without concurrency utils.
It includes a test that introduces an awaitTermination() method to join send
and event threads. This functionality is not exposed in the public API though
users could subclass ZooKeeper and use it as this patch does for testing.
> zookeeper client close operation may block indefinitely
> -------------------------------------------------------
>
> Key: ZOOKEEPER-126
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-126
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Reporter: Patrick Hunt
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-126.patch, ZOOKEEPER-126.patch
>
>
> Moving the hang issue from ZOOKEEPER-63 to here. See 63 for background and
> potential patch (patch_ZOOKEEPER-63.patch).
> specifically (from James):
> "I'm thinking the close() method should not wait() forever on the disconnect
> packet, just a closeTimeout length - say a few seconds. Afterall blocking and
> forcing a reconnect just to redeliver the disconnect packet seems a bit silly
> - when the server has to deal with clients which just have their sockets fail
> anyway"
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
