[
https://issues.apache.org/jira/browse/ZOOKEEPER-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13279272#comment-13279272
]
Eugene Koontz commented on ZOOKEEPER-1437:
------------------------------------------
Hi Antonio,
I think the empty data[] is an artifact of my development process: in my
testing, I found that if I use Kerberos as the SASL metchanism, the client's
ZooKeeperSaslClient::ServerSaslResponseCallback::processResult() will be
supplied with a null data[] array when this method (processResult()) is called
for the final time. So I had to handle this situation somehow.
One could handle the null server response in a different way, as long as you
avoid accessing a null pointer, of course - you could check for the null
pointer in other places, as your patch does.
However I don't think this is related to the problem you are seeing; or at
least, I'm not able to reproduce your problem myself. I wonder if you could
supply a shell script that could reproduce it? Perhaps a script that kills and
starts the server repeatedly to cause the client to eventually fail to
authenticate?
-Eugene
> 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
>
>
> 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
