I got this analysis from a user and am not quite sure what
to make of it yet, but thought I would forward it to the
list to see if anyone has opinions or it makes more sense
to them than it does to me at this point. Here's the note.
"I've found a few app ClassLoader leaks in Derby.
...The first one looks like Derby created a long-running
thread and copying the context class loader. To fix, the
context class loader should be saved/set/restored around the
creation of the new thread so that it copies some benign class
loader instead (e.g., null or getClass().getClassLoader()):
0x42278e58 java/lang/[EMAIL PROTECTED]
[truncating at running thread LEAK]
Object: 0x42278e58 java/lang/[EMAIL PROTECTED]
Children:
0x42278ee0 java/lang/[EMAIL PROTECTED]
0x4226e558 java/lang/[EMAIL PROTECTED]
0x42278e40
org/apache/derby/impl/services/monitor/[EMAIL PROTECTED]
0x419cfac0
The second is another long running thread. The same applies:
0x426fe7a0 java/lang/[EMAIL PROTECTED]
[truncating at running thread LEAK]
Object: 0x426fe7a0 java/lang/[EMAIL PROTECTED]
Parents:
0x4226e5a8 [Ljava/lang/Thread;@6f386f38
0x426fe548
org/apache/derby/iapi/services/context/[EMAIL PROTECTED]
Children:
0x426fe838 java/lang/[EMAIL PROTECTED]
0x4226e558 java/lang/[EMAIL PROTECTED]
0x426fe4f8
org/apache/derby/impl/services/daemon/[EMAIL PROTECTED]
0x419cfac0
The third is a TimerThread owneed , which is created when a
Timer is created. The same applies:
0x425ac538 java/util/[EMAIL PROTECTED]
[truncating at running thread LEAK]
Object: 0x425ac538 java/util/[EMAIL PROTECTED]
Parents:
0x41faaf58 [Ljava/lang/Thread;@3c583c58
Object: 0x425ac510 java/util/[EMAIL PROTECTED]
Parents:
0x425ac500
org/apache/derby/impl/services/timer/[EMAIL PROTECTED]
6e2
Thanks for any input. I will follow up with the user and
see if I can get some more details and translate into
something we can file in Jira.
Kathey
