[
https://issues.apache.org/jira/browse/ZOOKEEPER-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arshad Mohammad reopened ZOOKEEPER-2330:
----------------------------------------
One Login thread is shared by many ZooKeeper objects. So it is not appropriate
to close the Login thread on ZooKeeper.close() API call.
If there are many ZooKeeper client in one jvm, ZooKeeper.close() call by any
client will close the Login thread and TGT will not be refreshed for other
client. This will lead to auth fail exceptions
So the change by this patch should be reverted back.
> ZooKeeper close API does not close Login thread.
> ------------------------------------------------
>
> Key: ZOOKEEPER-2330
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2330
> Project: ZooKeeper
> Issue Type: Bug
> Components: java client
> Affects Versions: 3.5.0
> Reporter: Arshad Mohammad
> Assignee: Arshad Mohammad
> Fix For: 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2330-01.patch
>
>
> When kerberos is used as authentication mechanism, one login thread runs in
> the background for ZooKeeper client as well ZooKeepr server.
> This problem is related to Zookeeper client and the scenario is as follows:
> # Main application connects to Zookeeper
> {code}
> ZooKeeper zooKeeper = new ZooKeeper(zookeeperConnectionString,
> sessionTimeout, this)
> {code}
> # Completes it is work with zookeeper
> # calls close() on zookeeper, and continues with rest of the application
> specific work
> Thread dump, taken after 3rd step, shows that login thread is still alive
> {code}
> "Thread-1" daemon prio=6 tid=0x04842c00 nid=0x1f04 waiting on condition
> [0x05b7f000]
> java.lang.Thread.State: TIMED_WAITING (sleeping)
> at java.lang.Thread.sleep(Native Method)
> at org.apache.zookeeper.Login$1.run(Login.java:180)
> at java.lang.Thread.run(Thread.java:722)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
