[
https://issues.apache.org/jira/browse/KAFKA-7099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16523849#comment-16523849
]
Manikumar commented on KAFKA-7099:
----------------------------------
Existing issue: KAFKA-6415. This temporarily handled in KAFKA-6415 by
changing the log level to WARN.
> KafkaLog4jAppender - not sending any message with level DEBUG
> -------------------------------------------------------------
>
> Key: KAFKA-7099
> URL: https://issues.apache.org/jira/browse/KAFKA-7099
> Project: Kafka
> Issue Type: Bug
> Components: log
> Affects Versions: 0.10.2.0
> Reporter: Vincent Lebreil
> Priority: Major
>
> KafkaLog4jAppender can be stuck if it is defined at root category with level
> DEBUG
> {{log4j.rootLogger=DEBUG, kafka}}
> {{log4j.appender.kafka=org.apache.kafka.log4jappender.KafkaLog4jAppender}}
> {quote}DEBUG org.apache.kafka.clients.producer.KafkaProducer:131 - Exception
> occurred during message send:
> org.apache.kafka.common.errors.TimeoutException: Failed to update metadata
> after 60000 ms.
> {quote}
> KafkaLog4jAppender is using a KafkaProducer using itself Log4j with messages
> at levels TRACE and DEBUG. The appender used in this case is also the
> KafkaLog4jAppender.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
