[
https://issues.apache.org/jira/browse/ZOOKEEPER-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058428#comment-15058428
]
Flavio Junqueira commented on ZOOKEEPER-2344:
---------------------------------------------
[[email protected]] I've just had to do this for Kafka and it was not too bad,
but that might have to do with code familiarity. If you could be a bit more
specific about the cases that you found we could do more, then I'd appreciate
if you could list them here so that I can get a better idea of how to fix it.
Thanks for reporting this issue.
> Provide more diagnostics/stack traces on SASL Auth failure
> ----------------------------------------------------------
>
> Key: ZOOKEEPER-2344
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2344
> Project: ZooKeeper
> Issue Type: Improvement
> Components: java client, server
> Affects Versions: 3.4.5
> Reporter: Steve Loughran
>
> When Kerberos decides it doesn't want to work, the JRE libraries provide some
> terse and unhelpful error messages.
> The only way to debug the problem is (a) to have complete stack traces and
> (b) as much related information as possible.
> Zookeeper could do more here. Currently too much of the code loses stack
> traces; sometimes auth errors aren't reported back to the client (the
> connection is closed) +others
> Everyone who has tried to diagnose kerberos problems will appreciate
> improvements here
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
