[jboss-jira] [JBoss JIRA] Commented: (JBAS-7710) memory leak in DeadlockDetector

[Michal Borowiecki (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-7710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12518132#action_12518132 ] 

Michal Borowiecki commented on JBAS-7710:
-----------------------------------------

One workaround is to periodically clear the "waiting" HashMap which can be done through reflection.

> memory leak in DeadlockDetector
> -------------------------------
>
>                 Key: JBAS-7710
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7710
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: JBossAS-4.0.5.GA
>         Environment: JBoss 4.0.5.GA with JBOSSTS_4_2_3_SP7
>            Reporter: Michal Borowiecki
>
> Heap dump diagnostics revealed a memory leak in org.jboss.util.deadlock.DeadlockDetector.
> The more deadlocks are detected  the more "waiting" HashMap is growing.
> In our case the HashMap is >311MB in size. It contains 20 entries, 15 of them are > 20MB in size.
> The large size is not caused by map values but rather map keys which are of type com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple and contain a large number (couple thousand) of org.jboss.ejb.EntityEnterpriseContext references in its _txLocalResources variable.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira