[
https://issues.apache.org/jira/browse/DERBY-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kathey Marsden updated DERBY-3745:
----------------------------------
Attachment: derby-3745_10.3_diff.txt
Attached is a patch for this issue for the 10.3 branch. This takes care of the
leak for 10.3, but the same change on trunk still shows a leak related to
com/ibm/lang/management/MemoryNotificationThread
There must be some additional change related to jmx that is necessary. I
would like to go ahead and check in this change to get a fix for 10.3 and track
down the trunk issue separately.
I wasn't sure how to add a test for this, so didn't. I verified manually using
the IBM Heap analyzer and the test program supplied by the user.
I am running regresssion tests now.
> Derby can leak classloaders in an app server environment
> --------------------------------------------------------
>
> Key: DERBY-3745
> URL: https://issues.apache.org/jira/browse/DERBY-3745
> Project: Derby
> Issue Type: Bug
> Components: Services
> Affects Versions: 10.3.3.0, 10.4.1.3, 10.5.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Attachments: derby-3745_10.3_diff.txt
>
>
> A user reported potential class loader 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
> For more info, see thread at:
> http://www.nabble.com/ClassLoader-leaks--td18121374.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
