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] 2007-01-19 07:40 ------- Btw, the 1.2.8 log4j download seems to be linked at the bottom of the page ('earlier versions') -> http://archive.apache.org/dist/logging/log4j/ . It's MD5 is 18a4ca847248e5b8606325684342701c. Your manifest matches the 1.2.8 manifest. Line 185 of Category synchronizes on the Category and then its parents (in the first stack... this ends up in RollingFileAppender), and as Ceki said, appears to be blocked in the File call. The second stack is waiting to enter that lock. Is it always the same stack trace blocked on line 126 of RollingFileAppender? If so, upgrading the JVM (or switching from Sun to IBM or IBM to Sun) might be of value - though I suspect you're constrained by the vendor's versioning. Knowing the platform and vendor of the JVM might be of value to anyone else who hits the problem, but I suspect there's little log4j could be doing in this situation. -- 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]
