Return-Path: X-Original-To: apmail-kafka-dev-archive@www.apache.org Delivered-To: apmail-kafka-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0C4ACEE73 for ; Thu, 14 Feb 2013 17:08:13 +0000 (UTC) Received: (qmail 76853 invoked by uid 500); 14 Feb 2013 17:08:12 -0000 Delivered-To: apmail-kafka-dev-archive@kafka.apache.org Received: (qmail 76733 invoked by uid 500); 14 Feb 2013 17:08:12 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 76724 invoked by uid 99); 14 Feb 2013 17:08:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Feb 2013 17:08:12 +0000 Date: Thu, 14 Feb 2013 17:08:12 +0000 (UTC) From: "David Arthur (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (KAFKA-524) Kafka Appender causes Log4j Deadlock MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/KAFKA-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Arthur updated KAFKA-524: ------------------------------- Attachment: 0001-KAFKA-524-Defer-creating-Producer-in-log4j-appender.patch v2 of the patch > Kafka Appender causes Log4j Deadlock > ------------------------------------ > > Key: KAFKA-524 > URL: https://issues.apache.org/jira/browse/KAFKA-524 > Project: Kafka > Issue Type: Sub-task > Affects Versions: 0.7.2 > Reporter: nicu marasoiu > Labels: patch > Fix For: 0.7.2 > > Attachments: 0001-KAFKA-524-Defer-creating-Producer-in-log4j-appender.patch, 0001-KAFKA-524-Defer-creating-Producer-in-log4j-appender.patch > > > 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