You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Michael Han (JIRA)" <ji...@apache.org> on 2017/03/13 16:22:10 UTC
[jira] [Updated] (ZOOKEEPER-2407) EventThread in ClientCnxn can't
be closed when SendThread exits because of auth failed during reconnection
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Han updated ZOOKEEPER-2407:
-----------------------------------
Fix Version/s: (was: 3.5.3)
3.5.4
> EventThread in ClientCnxn can't be closed when SendThread exits because of auth failed during reconnection
> ----------------------------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2407
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2407
> Project: ZooKeeper
> Issue Type: Bug
> Affects Versions: 3.5.1
> Reporter: sunhaitao
> Assignee: sunhaitao
> Fix For: 3.5.4, 3.6.0
>
> Attachments: zookeeper-2407.patch
>
>
> EventThread in ClientCnxn can't be closed when SendThread exits because of auth failed during reconnection.
> for send thread if it is in authfailed state, the send thread exits,but the event thread is still running.
> observation:
> use jstack tho check the thread running they find the send thread no longer exists but event thread is still threre
> even when we call zookeeper.close(),the eventthread is still there.
> Stack trace:
> sun.misc.Unsafe.park(Native Method)
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
> java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
> org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:514)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)