zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2856) ZooKeeperSaslClient#respondToServer should log exception message of SaslException
Date Thu, 27 Jul 2017 01:36:00 GMT

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

Hudson commented on ZOOKEEPER-2856:
-----------------------------------

SUCCESS: Integrated in Jenkins build ZooKeeper-trunk #3478 (See [https://builds.apache.org/job/ZooKeeper-trunk/3478/])
ZOOKEEPER-2856: ZooKeeperSaslClient#respondToServer should log exception (hanm: rev 41b30a74ec8b33255e99d97a102de53d315c28b3)
* (edit) src/java/main/org/apache/zookeeper/client/ZooKeeperSaslClient.java


> ZooKeeperSaslClient#respondToServer should log exception message of SaslException
> ---------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2856
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2856
>             Project: ZooKeeper
>          Issue Type: Improvement
>    Affects Versions: 3.4.10, 3.5.3
>            Reporter: Pan Yuxuan
>            Assignee: Pan Yuxuan
>            Priority: Minor
>             Fix For: 3.5.4, 3.6.0, 3.4.11
>
>         Attachments: ZOOKEEPER-2856-1.patch
>
>
> When upstream like HBase call ZooKeeperSaslClient with security enabled, we sometimes
get error in HBase logs like:
> {noformat}
> SASL authentication failed using login context 'Client'.
> {noformat}
> This error occures when getting SaslException in ZooKeeperSaslClient#respondToServer
:
> {noformat}
>  catch (SaslException e) {
>                 LOG.error("SASL authentication failed using login context '" +
>                         this.getLoginContext() + "'.");
>                 saslState = SaslState.FAILED;
>                 gotLastPacket = true;
>   }
> {noformat}
> This error makes user confused without explicit exception message. So I think we can
add exception message to the log.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message