zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patrick Hunt <ph...@apache.org>
Subject Test failures (SASL) with Java 11 - any ideas?
Date Sat, 21 Jul 2018 06:02:23 GMT
Hey folks, I added a couple Jenkins jobs based on Java 11 which is set to
release in September. Jenkins is running a pre-release

java version "11-ea" 2018-09-25
Java(TM) SE Runtime Environment 18.9 (build 11-ea+19)
Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11-ea+19, mixed mode)

Anyone have insight into what's failing here?

2018-07-20 14:39:27,126 [myid:2] - ERROR
[QuorumConnectionThread-[myid=2]-3:QuorumCnxManager@268] - Exception
while connecting, id: [0, localhost/], addr: {},
closing learner connection
javax.security.sasl.SaslException: An error:
javax.security.sasl.SaslException: GSS initiate failed [Caused by
GSSException: No valid credentials provided (Mechanism level: Message
stream modified (41) - Message stream modified)]) occurred when
evaluating Zookeeper Quorum Member's  received SASL token.


Entered Krb5Context.initSecContext with state=STATE_NEW
Found ticket for learner@EXAMPLE.COM to go to
krbtgt/EXAMPLE.COM@EXAMPLE.COM expiring on Sat Jul 21 14:39:01 UTC
Service ticket not found in the subject
2018-07-20 14:39:27,127 [myid:0] - ERROR
[QuorumConnectionThread-[myid=0]-2:SaslQuorumAuthServer@133] - Failed
to authenticate using SASL



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message