[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399004#comment-13399004
 ] 

Patrick Hunt commented on ZOOKEEPER-1437:
-----------------------------------------

Hi Eugene, here's the call hierarchy from Eclipse (one of many) and the root of 
my concern:

{noformat}
org.apache.zookeeper.ClientCnxn.sendPacket(Record, Record, AsyncCallback, int)
org.apache.zookeeper.client.ZooKeeperSaslClient.sendSaslPacket(byte[], 
ClientCnxn)
org.apache.zookeeper.client.ZooKeeperSaslClient.respondToServer(byte[], 
ClientCnxn)
org.apache.zookeeper.client.ZooKeeperSaslClient.ServerSaslResponseCallback.processResult(int,
 String, Object, byte[], Stat)
org.apache.zookeeper.ClientCnxn.EventThread.processEvent(Object)
org.apache.zookeeper.ClientCnxn.EventThread.run()
{noformat}

Try doing a "open call hierarchy" in eclipse for getXid.

                
> Client uses session before SASL authentication complete
> -------------------------------------------------------
>
>                 Key: ZOOKEEPER-1437
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1437
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: java client
>    Affects Versions: 3.4.3
>            Reporter: Thomas Weise
>            Assignee: Eugene Koontz
>             Fix For: 3.4.4, 3.5.0
>
>         Attachments: ZOOKEEPER-1437.patch, ZOOKEEPER-1437.patch, 
> ZOOKEEPER-1437.patch, ZOOKEEPER-1437.patch, ZOOKEEPER-1437.patch, 
> ZOOKEEPER-1437.patch, ZOOKEEPER-1437.patch, ZOOKEEPER-1437.patch, 
> ZOOKEEPER-1437.patch, ZOOKEEPER-1437.patch, ZOOKEEPER-1437.patch, 
> ZOOKEEPER-1437.patch, ZOOKEEPER-1437.patch, ZOOKEEPER-1437.patch
>
>
> Found issue in the context of hbase region server startup, but can be 
> reproduced w/ zkCli alone.
> getData may occur prior to SaslAuthenticated and fail with NoAuth. This is 
> not expected behavior when the client is configured to use SASL.

--
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

        

Reply via email to