Tracker: Bugs (Migrated to Jira)

5 log4j errors on startup and shutdown - ID: 1921874
Last Update: Settings changed ( pangloss )

On startup:

log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester).
log4j:WARN Please initialize the log4j system properly.

On shutdown:

log4j:ERROR LogMananger.repositorySelector was null likely due to error in class reloading, using NOPLoggerRepository.

E S ( pangloss ) - 2008-03-20 20:16:16 PDT

5

Closed

Fixed

E S

None

Fedora 3.0b1

Public


Comments ( 2 )

Date: 2008-05-15 21:53:19 PDT
Sender: panglossProject Admin


Fix committed to trunk (r7172). Note that to eliminate the shutdown error
message, the system property
org.apache.catalina.loader.WebappClassLoader.ENABLE_CLEAR_REFERENCES must
be set to false. This is not set by default, but the Tomcat upgrade now
allows the system property to be set.

Date: 2008-03-20 20:21:31 PDT
Sender: panglossProject Admin


For the shutdown error, see:
https://issues.apache.org/bugzilla/show_bug.cgi?id=41939
https://issues.apache.org/bugzilla/show_bug.cgi?id=42172

To address the startup error, we need to initialize log4j on startup,
e.g.:
1) log4j.properties on the classpath (e.g. fedora/WEB-INF/classes)
2) log4j initialization servlet

If #2, need to consider changes in servlet loading order (for servlet 2.4,
listeners should be loaded first).

Attached File

No Files Currently Attached

Changes ( 3 )

Field Old Value Date By
status_id Open 2008-05-15 21:53:20 PDT pangloss
resolution_id None 2008-05-15 21:53:20 PDT pangloss
close_date - 2008-05-15 21:53:20 PDT pangloss