[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ] Thomas Mäder commented on JBIDE-21857: -------------------------------------- After looking at this, I believe that this is not a problem with the behavior of our tooling, but in EAP. Here's what I did: 1. I was able to verify that Runtime.gc() is reliably called twice after the reload of the module 2. I can reproduce the problem by running the jboss-kitchensink example and by putting a breakpoint in MemberRepository.findAllOrderedByName both locally (eap 6.4 and 7.0) and on openshift (eap 7.0). Therefore it's likely NOT openshift tooling specific. 3. When I look at heap dumps from after a couple of times reproducing the problem, I see that there are references to an instance of MemberController in a ThreadLocal for each time I try to do HCR. 4. When I let the request I am in run to completion and then suspend the request thread, the thread local still references the MemberController instance. I suspect that the HCR leads to an exception and that the ThreadLocal is not properly cleaned up. I don't stand a chance of debugging the apparent EAP problem in a reasonable time. I suggest involving an expert on EAP/Wildfly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)