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 Thu, 07 Oct 2010 18:27:29 GMT

--- Comment #16 from S. Ali Tokmen <> 2010-10-07 14:27:23
EDT ---
(In reply to comment #15)
> Imposing JULI on the world just to be right is not reasonable.

I cannot agree more. Tomcat, as a Java application like any other, should NOT
be imposing a logger but rather reuse the existing logger.

(Bis repetita) The correct implementation for this memory leak avoiding
mechanism 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