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=37218>. 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=37218 ------- Additional Comments From [EMAIL PROTECTED] 2005-10-24 15:48 ------- (In reply to comment #2) > Remy, please read comment #28 by Brett in > http://issues.apache.org/bugzilla/show_bug.cgi?id=26372 > > and a newer comment #31 by Brett in > http://issues.apache.org/bugzilla/show_bug.cgi?id=27371 > > Please note that http://issues.apache.org/bugzilla/show_bug.cgi?id=27371 is a > newer issue than http://issues.apache.org/bugzilla/show_bug.cgi?id=26372 which > you are likely familiar with. Brett clearly states: > > "I ran into this issue, and having written a trivial test case, I can confirm > that this zilla has nothing to do with logging (commons or log4j) or parent > classloaders etc. No amount of fiddling with library classloading will fix > it." > > So the Tomcat guys won't fix this, nor the Log4j guys. What are we left doing? > What is your advice/suggestion for resolving this issue? Completely unrelated. In this guy's case, the error will be on request processing thread (with the only result being that his request will end sooner, which is as expected 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]
