[
https://issues.apache.org/jira/browse/ZOOKEEPER-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174126#comment-13174126
]
Oliver Wulff commented on ZOOKEEPER-126:
----------------------------------------
Why is this issue pushed to 3.5.0?
I think I saw the same issue here with 3.3.3:
java.lang.Object.wait(Native Method)
java.lang.Object.wait(Object.java:485)
org.apache.zookeeper.ClientCnxn.submitRequest(ClientCnxn.java:1317)
org.apache.zookeeper.ClientCnxn.close(ClientCnxn.java:1295)
org.apache.zookeeper.ZooKeeper.close(ZooKeeper.java:531)
- locked org.apache.zookeeper.ZooKeeper@26827e
The thread is blocked which impacts other threads then.
My guess is that the network here is not very reliable and therefore we run
into this blocking issue.
IMHO, it makes perfect sense to *not* wait for unlimited time if closing the
connection blocks.
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
