tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 48716] Embedded Tomcat JULI aggressively resetting default logging configuration
Date Sun, 22 Aug 2010 14:02:14 GMT

S. Ali Tokmen <> changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |

--- Comment #10 from S. Ali Tokmen <> 2010-08-22 10:02:08
EDT ---
This is not fixed: Tomcat 6.0.29 and 7.0.2 still removes all handlers of all
Java loggers.

Here is the code executed by Catalina:

        // Clear the classloader reference in common-logging
        if (clearReferencesLogFactoryRelease) {

... which looks correct. But, JULI actually ignores the given ClassLoader and


Which basically removes all handlers of all loggers of the Java util logger.
Note that the comment on JULI says it should remvoe only things from JULI, that

The correct implementation would, I guess, look like that:

    To clean up all of the current Web application's loggers:

    get all loggers' names
    for each logger
        get all handlers
        for each handler
            if the handler's class can be loaded using the WebAppClassLoader
               AND cannot be loaded using the WebAppClassLoader's parent
              remove this handler
            else don't touch
              // that logger belongs to some other application
              // or to Tomcat itself

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message