You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "nicu marasoiu (JIRA)" <ji...@apache.org> on 2012/09/22 13:15:07 UTC
[jira] [Created] (KAFKA-524) Kafka Appender causes Log4j Deadlock
nicu marasoiu created KAFKA-524:
-----------------------------------
Summary: Kafka Appender causes Log4j Deadlock
Key: KAFKA-524
URL: https://issues.apache.org/jira/browse/KAFKA-524
Project: Kafka
Issue Type: Sub-task
Reporter: nicu marasoiu
please read list comment on the parent
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KAFKA-524) Kafka Appender causes Log4j Deadlock
Posted by "nicu marasoiu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KAFKA-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
nicu marasoiu updated KAFKA-524:
--------------------------------
Description:
If you remove all log4j.properties from classpath (and prvent any log4j intialization previous to the one which involves kafka appender), and put KAFKA appender on rootLogger, then, even if you exclude the KAFKA appender from logger.kafka and logger.org, you get a Log4j deadlock when zookeeper send thread tries to issue a LOG.info, and for that it locks the root category (as its correct category, say org, is not yet set up in log4j, who is still in activateOptions on kafka appender).
please read comments on the parent and ask any questions to nmarasoi@adobe.com
was:please read list comment on the parent
> Kafka Appender causes Log4j Deadlock
> ------------------------------------
>
> Key: KAFKA-524
> URL: https://issues.apache.org/jira/browse/KAFKA-524
> Project: Kafka
> Issue Type: Sub-task
> Reporter: nicu marasoiu
>
> If you remove all log4j.properties from classpath (and prvent any log4j intialization previous to the one which involves kafka appender), and put KAFKA appender on rootLogger, then, even if you exclude the KAFKA appender from logger.kafka and logger.org, you get a Log4j deadlock when zookeeper send thread tries to issue a LOG.info, and for that it locks the root category (as its correct category, say org, is not yet set up in log4j, who is still in activateOptions on kafka appender).
> please read comments on the parent and ask any questions to nmarasoi@adobe.com
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira