[
https://issues.apache.org/jira/browse/ZOOKEEPER-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927849#comment-15927849
]
Rakesh R commented on ZOOKEEPER-2712:
-------------------------------------
[~hanm], Yes test case was consistently passing with Kerby dependency. Also, it
was pretty simple compares to ApacheDS but Kerby has build requirement of
jdk1.7+, http://directory.apache.org/kerby/developer-guide.html]. Since
branch-3.4.x support Java 1.6 or higher, Apache Kerby dependency is not
possible, right?
I'm still searching the root cause of this test failure, kerb related logs are
not helping much to identify the real problem.
> MiniKdc test case intermittently failing due to principal not found in
> Kerberos database
> ----------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2712
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2712
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 3.4.11
>
> Attachments:
> TEST-org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthTest.txt
>
>
> MiniKdc test cases are intermittently failing due to not finding the
> principal. Below is the failure stacktrace.
> {code}
> 2017-03-08 13:21:10,843 [myid:] - ERROR
> [NioProcessor-1:AuthenticationService@187] - Error while searching for client
> lear...@example.com : Client not found in Kerberos database
> 2017-03-08 13:21:10,843 [myid:] - WARN
> [NioProcessor-2:KerberosProtocolHandler@241] - Server not found in Kerberos
> database (7)
> 2017-03-08 13:21:10,845 [myid:] - WARN
> [NioProcessor-2:KerberosProtocolHandler@242] - Server not found in Kerberos
> database (7)
> 2017-03-08 13:21:10,844 [myid:] - WARN
> [NioProcessor-1:KerberosProtocolHandler@241] - Client not found in Kerberos
> database (6)
> 2017-03-08 13:21:10,845 [myid:] - WARN
> [NioProcessor-1:KerberosProtocolHandler@242] - Client not found in Kerberos
> database (6)
> {code}
> Will attach the detailed log to jira.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
