https://issues.apache.org/bugzilla/show_bug.cgi?id=34110
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |WONTFIX
--- Comment #7 from Mark Thomas <ma...@apache.org> 2009-06-10 08:38:22 PST ---
This clash between commons-logging in a webapp and in Tomcat is one of the
reasons for the switch to JULI in Tomcat 6. I can reproduce this on 5.5.x but I
can't see how to fix it without some major changes (ie porting JULI). That is
just too big a chance for a branch as mature as 5.5.x.
As an aside, r374893 ( https://svn.apache.org/viewcvs.cgi?view=rev&rev=374893 )
makes it clear that it is intentional that the logger is
loaded by the web application classloader.
You do get a warning that log4j is not configured properly which at least gives
you a clue that you are missing some log information.
I am therefore closing this as won't fix.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
