#62 log4j errors on startup and shutdown

Fedora 3.0b1
closed-fixed
E S
None
5
2008-05-16
2008-03-21
E S
No

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.

Discussion

  • E S
    E S
    2008-03-21

    Logged In: YES
    user_id=487398
    Originator: YES

    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).

     
  • E S
    E S
    2008-05-16

    Logged In: YES
    user_id=487398
    Originator: YES

    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.

     
  • E S
    E S
    2008-05-16

    • status: open --> closed-fixed