-
Enhancement
-
Resolution: Duplicate
-
P4
-
1.4.1
-
x86
-
linux
Name: rmT116609 Date: 02/03/2003
DESCRIPTION OF THE PROBLEM :
We need a way to remove Logger objects from the LogManager when they are no longer needed. There is no way to remove a Logger from LogManager and in reviewing the source code LogManager does not use weak references - it uses a simple Hashtable. Furthermore, the comment on LogManager.addLogger is misleading as it states that the implementation "may" use weak references.
We create numerous Logger objects on our server and we need a way to clean them out when a session used by that logger is terminated. Using separate Logger objects gives us the ability to have different logging levels for different
sessions. For example, if a user is having a problem I want to be ablt turn debugging on for their sesson and not all sessions on the server.
(Review ID: 180707)
======================================================================
DESCRIPTION OF THE PROBLEM :
We need a way to remove Logger objects from the LogManager when they are no longer needed. There is no way to remove a Logger from LogManager and in reviewing the source code LogManager does not use weak references - it uses a simple Hashtable. Furthermore, the comment on LogManager.addLogger is misleading as it states that the implementation "may" use weak references.
We create numerous Logger objects on our server and we need a way to clean them out when a session used by that logger is terminated. Using separate Logger objects gives us the ability to have different logging levels for different
sessions. For example, if a user is having a problem I want to be ablt turn debugging on for their sesson and not all sessions on the server.
(Review ID: 180707)
======================================================================
- duplicates
-
JDK-6274920 JDK logger holds strong reference to java.util.logging.Logger instances
- Closed
- relates to
-
JDK-4952316 RFE: Can't "release" logger instances
- Closed