[jboss-jira] [JBoss JIRA] (JGRP-1834) ProbeHandler memory leak when enable_diagnostics=false
Bela Ban (JIRA)
issues at jboss.org
Wed May 7 05:00:56 EDT 2014
[ https://issues.jboss.org/browse/JGRP-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bela Ban resolved JGRP-1834.
----------------------------
Resolution: Done
Fixed on master and 3.4
> ProbeHandler memory leak when enable_diagnostics=false
> ------------------------------------------------------
>
> Key: JGRP-1834
> URL: https://issues.jboss.org/browse/JGRP-1834
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 3.2.12
> Reporter: Dennis Reed
> Assignee: Bela Ban
> Fix For: 3.4.4, 3.5
>
>
> There is a memory leak in TP#preregistered_probe_handlers when enable_diagnostics is false.
> TP#registerProbeHandler stores ProbeHandlers in the preregistered_probe_handlers list if diag_handler is null (either because TP has not been started, or enable_diagnostics is false).
> When TP is started, if enable_diagnostics is true it copies them to the diag_handler and clears out preregistered_probe_handlers.
> But if enable_diagnostics is false, preregistered_probe_handlers will never get cleared.
> This prevents anything that registered a probe handler from being GC'd. For example with a shared JGroups transport like EAP uses, this can cause an Infinispan CacheManager that has been stopped to never get GC'd.
> (This issue was noticed because of a buildup of DefaultCacheManager instances in a heap dump after an application had been redeployed a few times).
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
More information about the jboss-jira
mailing list