[
https://issues.apache.org/jira/browse/KAFKA-5173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998045#comment-15998045
]
Rajini Sivaram commented on KAFKA-5173:
---------------------------------------
[~ijuma] Yes, they do both look like the same issue. I would suspect
KAFKA-4703 too, even though looking at the code, I simply can't see how this
could happen. Though it clearly does. The first log shows that the login.config
system property was set, which is done in
{{SaslSetup#writeJaasConfigurationToFile}} which does also resets
{{Configuration}}. We also remove the property and clear Configuration in
teardowns. So could we have written a config file without any contexts?
KAFKA-4703 separated out creation and writing of contexts, but I don't see any
timing dependent element there either.
> SASL tests failing with Could not find a 'KafkaServer' or
> 'sasl_plaintext.KafkaServer' entry in the JAAS configuration
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-5173
> URL: https://issues.apache.org/jira/browse/KAFKA-5173
> Project: Kafka
> Issue Type: Bug
> Reporter: Ismael Juma
> Fix For: 0.11.0.0
>
>
> I've seen this a few times. One example:
> {code}
> java.lang.IllegalArgumentException: Could not find a 'KafkaServer' or
> 'sasl_plaintext.KafkaServer' entry in the JAAS configuration. System property
> 'java.security.auth.login.config' is /tmp/kafka8162725028002772063.tmp
> at
> org.apache.kafka.common.security.JaasContext.defaultContext(JaasContext.java:131)
> at
> org.apache.kafka.common.security.JaasContext.load(JaasContext.java:96)
> at
> org.apache.kafka.common.security.JaasContext.load(JaasContext.java:78)
> at
> org.apache.kafka.common.network.ChannelBuilders.create(ChannelBuilders.java:100)
> at
> org.apache.kafka.common.network.ChannelBuilders.serverChannelBuilder(ChannelBuilders.java:73)
> at kafka.network.Processor.<init>(SocketServer.scala:423)
> at kafka.network.SocketServer.newProcessor(SocketServer.scala:145)
> at
> kafka.network.SocketServer$$anonfun$startup$1$$anonfun$apply$1.apply$mcVI$sp(SocketServer.scala:96)
> at scala.collection.immutable.Range.foreach$mVc$sp(Range.scala:160)
> at
> kafka.network.SocketServer$$anonfun$startup$1.apply(SocketServer.scala:95)
> at
> kafka.network.SocketServer$$anonfun$startup$1.apply(SocketServer.scala:90)
> at
> scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
> at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:48)
> at kafka.network.SocketServer.startup(SocketServer.scala:90)
> at kafka.server.KafkaServer.startup(KafkaServer.scala:218)
> at kafka.utils.TestUtils$.createServer(TestUtils.scala:126)
> at
> kafka.integration.BaseTopicMetadataTest.setUp(BaseTopicMetadataTest.scala:51)
> at
> kafka.integration.SaslPlaintextTopicMetadataTest.kafka$api$SaslTestHarness$$super$setUp(SaslPlaintextTopicMetadataTest.scala:23)
> at kafka.api.SaslTestHarness$class.setUp(SaslTestHarness.scala:31)
> at
> kafka.integration.SaslPlaintextTopicMetadataTest.setUp(SaslPlaintextTopicMetadataTest.scala:23)
> {code}
> https://builds.apache.org/job/kafka-trunk-jdk8/1479/testReport/junit/kafka.integration/SaslPlaintextTopicMetadataTest/testIsrAfterBrokerShutDownAndJoinsBack/
> [~rsivaram], any ideas?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
