Bug 39631 - JCL 1.1 - Log4JLogger.traceLevel becomes null
Summary: JCL 1.1 - Log4JLogger.traceLevel becomes null
Status: RESOLVED DUPLICATE of bug 39090
Alias: None
Product: Tomcat 5
Classification: Unclassified
Component: Catalina (show other bugs)
Version: 5.5.17
Hardware: PC Windows XP
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-22 14:14 UTC by Grzegorz Grzybek
Modified: 2006-06-19 06:34 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Grzegorz Grzybek 2006-05-22 14:14:05 UTC 
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.
Comment 1 Grzegorz Grzybek 2006-06-19 13:34:12 UTC 
I think this bug is just a result of #39090's memory leak problem...

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