Return-Path: Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: (qmail 28714 invoked from network); 17 Jan 2008 17:33:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Jan 2008 17:33:22 -0000 Received: (qmail 1369 invoked by uid 500); 17 Jan 2008 17:33:11 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 1346 invoked by uid 500); 17 Jan 2008 17:33:11 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 1335 invoked by uid 99); 17 Jan 2008 17:33:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2008 09:33:11 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jan 2008 17:33:06 +0000 Received: by brutus.apache.org (Postfix, from userid 33) id 6987471426E; Thu, 17 Jan 2008 09:32:58 -0800 (PST) From: bugzilla@apache.org To: log4j-dev@logging.apache.org Subject: DO NOT REPLY [Bug 41214] - Deadlock with RollingFileAppender In-Reply-To: X-Bugzilla-Reason: AssignedTo Message-Id: <20080117173258.6987471426E@brutus.apache.org> Date: Thu, 17 Jan 2008 09:32:58 -0800 (PST) X-Virus-Checked: Checked by ClamAV on apache.org DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG� RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND� INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=41214 ------- Additional Comments From carnold@apache.org 2008-01-17 09:32 ------- Comments 18-20 do not appear to be related to the initial reported bug which from all the discussion appears to be a Solaris JVM bug and not a log4j bug. Comment 18 appears to be occurring due to Hibernate using an Object as a message and that Object's toString() method in turn triggers logging calls. Unfortunately log4j 1.2 is not designed to be reentrant, you can't make log4j logging calls reliably from within log4j. Options would be to configure an Object renderer that would avoid calling the problematic toString() call or removing the logging calls in the problematic toString() call. The stack traces in 19 and 20 clearly look like the problematic pre-log4j 1.2.14 AsyncAppender which had many synchronization issues. The suggest resolution there would be to upgrade to log4j 1.2.15 or later. If there are new issues, then should be logged as new bug reports. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org