tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 48716] Embedded Tomcat JULI aggressively resetting default logging configuration
Date Sun, 22 Aug 2010 15:06:42 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=48716

--- Comment #12 from S. Ali Tokmen <postmaster@alishomepage.com> 2010-08-22 11:06:38
EDT ---
Hello

Well, I'm currently analyzing the java.util.logging.LogManager.java (version:
1.55 09/05/17 | SUN PROPRIETARY/CONFIDENTIAL.)

JULI calls:

    java.util.logging.LogManager.getLogManager()

that, returns the following:

    // The global LogManager object
    private static LogManager manager;

The static "manager" variable is defined in java.util.logging.LogManager, which
is in the Java SE classloader. It is therefore the same instance for all the
JVM.

That (UNIQUE) instance has an attribute:

    private Hashtable<String,Logger> loggers = new Hashtable<String,Logger>()

Finally, getLoggerNames() returns:

    public synchronized Enumeration<String> getLoggerNames() {
    return loggers.keys();
    }

As a result, I do not see how come
java.util.logging.LogManager.getLogManager().reset() could reset anything else
than the whole JVM's loggers, hence how this bug can be resolved fixed.

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message