[ https://issues.apache.org/jira/browse/ZOOKEEPER-2139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15031959#comment-15031959 ]
Arshad Mohammad commented on ZOOKEEPER-2139: -------------------------------------------- Currently one {{org.apache.zookeeper.Login}} is shared among all the {{ZookeeperSaslClient}} instances. To have multiple Kerberos authenticated Zookeeepr client in the same JVM we have create at least one Login instance for each ZooKeeper client. > Zookeeper client configuration should not be java system property > ----------------------------------------------------------------- > > Key: ZOOKEEPER-2139 > URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2139 > Project: ZooKeeper > Issue Type: Improvement > Components: java client > Affects Versions: 3.5.0 > Reporter: Surendra Singh Lilhore > Assignee: Arshad Mohammad > Fix For: 3.5.2, 3.6.0 > > Attachments: ZOOKEEPER-2139-05.patch, ZOOKEEPER-2139-06.patch, > ZOOKEEPER-2139.patch, ZOOKEEPER-2139.patch, ZOOKEEPER-2139_1.patch, > ZOOKEEPER-2139_2.patch > > > I have two ZK client in one JVM, one is secure client and second is normal > client (For non secure cluster). > "zookeeper.sasl.client" system property is "true" by default, because of this > my second client connection is failing. > We should pass all client configurations in client constructor like HDFS > client. > For example : > {code} > public ZooKeeper(String connectString, int sessionTimeout, Watcher watcher, > Configuration conf) throws IOException > { > ...... > ...... > } > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)