DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=41214>. 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 [EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
