You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2006/05/22 16:14:05 UTC

DO NOT REPLY [Bug 39631] New: - JCL 1.1 - Log4JLogger.traceLevel becomes null

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

           Summary: JCL 1.1 - Log4JLogger.traceLevel becomes null
           Product: Tomcat 5
           Version: 5.5.17
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: g.grzybek@op.pl


I think it's a classloading problem. The scenario is:
 - running tomcat 5.5.17 with TOMCAT_HOME/bin/commons-logging-api.jar updated to 1.1
 - there's no commons-logging.jar both in common and shared classloader
 - there's only one simple webapp (servlet which uses Log) with
commons-logging-adapters-1.1.jar and log4j-1.2.13.jar in its /WEB-INF/lib
 - tomcat starts
 - everything's fine
 - my simple app stops (using manager console)
 - my simple app starts again
 - there is NPE in:
SEVERE: Error reading tld listeners java.lang.NullPointerException
java.lang.NullPointerException
	at org.apache.log4j.Category.isEnabledFor(Category.java:746)
	at org.apache.commons.logging.impl.Log4JLogger.isTraceEnabled(Log4JLogger.java:327)
	at org.apache.catalina.startup.TldConfig.tldScanResourcePaths(TldConfig.java:581)

when this happens (Log4JLogger.java:327), "Log4JLogger.class.getClassLoader()"
evaluates to WebappClassLoader which has already stopped.

-- 
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


DO NOT REPLY [Bug 39631] - JCL 1.1 - Log4JLogger.traceLevel becomes null

Posted by bu...@apache.org.
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=39631>.
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=39631


g.grzybek@op.pl changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE




------- Additional Comments From g.grzybek@op.pl  2006-06-19 13:34 -------
I think this bug is just a result of #39090's memory leak problem...

*** This bug has been marked as a duplicate of 39090 ***

-- 
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org