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=33932>.
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=33932

           Summary: Problem with common logging - uses wrong logger
           Product: Tomcat 5
           Version: 5.0.28
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: [EMAIL PROTECTED]


I've deployed an application that uses common-logging with log4j to log.
common-logging and log4j jars are located in WEB-INF/lib.
With a profiler, I spotted some classes that are used internally by tomcat
(BeanUtilsBean, for example) that use the log4j logger loaded by my application.
This is very unusual, and causes memory leaks by maintaining strong ref to the
web app class loader.
I assume the problem is somewhere in common-logging, because of a context class
loared, but I dod not have time to investigate.
The workaround I've found was to put common-logging and log4j jars in 
share/libs.

-- 
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]

Reply via email to