Bug 1156620

Summary: [GSS](6.4.0) Memory leak on undeploy & too many channels caused by ejb client not disassociating
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Brad Maxwell <bmaxwell>
Component: EJBAssignee: Brad Maxwell <bmaxwell>
Status: CLOSED CURRENTRELEASE QA Contact: Pavel Slavicek <pslavice>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3.2CC: aogburn, bmaxwell, jawilson, kkhan, myarboro, wfink
Target Milestone: CR1   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
This release of JBoss EAP 6 fixes a memory leak caused by an application deployed that is using `jboss-ejb-client.xml` to configure remote EJB clients connections. This fix also resolves another issue wherein scoped context was used and too many channels occurred (as a result of channels not being closed until all channels to a given host are closed). The channel is now closed when `Context.close()` is called even if other channels are open to the same host.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1198231    
Bug Blocks:    

Description Brad Maxwell 2014-10-24 19:43:34 UTC
EJB client application deployed with jboss-ejb-client.xml, when undeployed the classloader is not being released leading to a memory leak.  The classes are still seen in the heap.

Comment 1 JBoss JIRA Server 2014-10-24 19:52:25 UTC
Brad Maxwell <bmaxwell> updated the status of jira WFLY-4016 to Coding In Progress

Comment 4 Kabir Khan 2015-03-02 19:40:44 UTC
https://github.com/wildfly/wildfly/pull/6870 was the upstream fix (it was a rework of https://github.com/wildfly/wildfly/pull/6869)

Comment 7 Kabir Khan 2015-03-03 15:48:54 UTC
https://github.com/jbossas/jboss-eap/pull/2333

Comment 8 Kabir Khan 2015-03-05 13:22:59 UTC
The pull request has been updated to https://github.com/jbossas/jboss-eap/pull/2341

Comment 13 hsvabek 2015-03-17 08:17:16 UTC
It's ok.

Comment 14 JBoss JIRA Server 2015-03-18 02:51:08 UTC
Brad Maxwell <bmaxwell> updated the status of jira EJBCLIENT-84 to Resolved