[
https://issues.apache.org/jira/browse/ZOOKEEPER-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13141608#comment-13141608
]
Gunnar Wagenknecht commented on ZOOKEEPER-1100:
-----------------------------------------------
The issue we faced was that an OutOfMemoryError was thrown in the send thread
which silently killed it. After that all other threads interacting with
ZooKeeper just hung because there was no send thread and the ZooKeeper
connection was still considered fine.
> Killed (or missing) SendThread will cause hanging threads
> ---------------------------------------------------------
>
> Key: ZOOKEEPER-1100
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1100
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Affects Versions: 3.3.3
> Environment:
> http://mail-archives.apache.org/mod_mbox/zookeeper-user/201106.mbox/%[email protected]%3E
> Reporter: Gunnar Wagenknecht
> Assignee: Rakesh R
> Fix For: 3.5.0
>
> Attachments: ZOOKEEPER-1100.patch, ZOOKEEPER-1100.patch
>
>
> After investigating an issues with [hanging
> threads|http://mail-archives.apache.org/mod_mbox/zookeeper-user/201106.mbox/%[email protected]%3E]
> I noticed that any java.lang.Error might silently kill the SendThread.
> Without a SendThread any thread that wants to send something will hang
> forever.
> Currently nobody will recognize a SendThread that died. I think at least a
> state should be flipped (or flag should be set) that causes all further send
> attempts to fail or to re-spin the connection loop.
--
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
