[
https://issues.apache.org/jira/browse/ZOOKEEPER-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740310#comment-14740310
]
Hudson commented on ZOOKEEPER-2040:
-----------------------------------
SUCCESS: Integrated in ZooKeeper-trunk #2798 (See
[https://builds.apache.org/job/ZooKeeper-trunk/2798/])
ZOOKEEPER-2040: Server to log underlying cause of SASL connection problems.
(Steve Loughran via cnauroth) (cnauroth:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1702378)
* /zookeeper/trunk/CHANGES.txt
*
/zookeeper/trunk/src/java/main/org/apache/zookeeper/server/ZooKeeperServer.java
> Server to log underlying cause of SASL connection problems
> ----------------------------------------------------------
>
> Key: ZOOKEEPER-2040
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2040
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.4.6
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Fix For: 3.4.7, 3.5.2, 3.6.0
>
> Attachments: ZOOKEEPER-2040-log-SASL-errors-001.patch,
> ZOOKEEPER-2040.002.patch
>
>
> When you have SASL connectivity problems, you spend time staring at logs
> —ideally logs with stack traces.
> ZK server can help here by including the stack traces when there is a SASL
> auth problem, rather than just giving the text of the exception.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
