ssage-
From: Chris Hegarty [mailto:[email protected]]
Sent: 22 December 2010 17:35
To: Roman Kennke
Cc: [email protected]
Subject: Re: Potential memory leak in java.util.logging.Level
On 12/22/10 02:36 PM, Roman Kennke wrote:
Hello,
I believe java.util.logging.Level is po
d time to implement a fix.
**Roman
-Original Message-
From: Chris Hegarty [mailto:[email protected]]
Sent: 22 December 2010 17:35
To: Roman Kennke
Cc: [email protected]
Subject: Re: Potential memory leak in java.util.logging.Level
On 12/22/10 02:36 PM, Roman Kennke wrot
On 12/22/10 02:36 PM, Roman Kennke wrote:
Hello,
I believe java.util.logging.Level is potentially memory leaking. This can
happen if an application defines its own subclass of Level and is loaded by its
own classloader. Level's constructor adds a reference to the new instance of
the subclass
This is definitely a problem with web apps. (I have heard from other teams,
but not experienced it myself.) Wouldn't the correct solution be to make the
array use weak references? Of course, if it makes sense to expose more of the
api (I'm not familiar with it), then do that, too.
Joel
