Bug 1156620 - [GSS](6.4.0) Memory leak on undeploy & too many channels caused by ejb client not disassociating
Summary: [GSS](6.4.0) Memory leak on undeploy & too many channels caused by ejb client...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.3.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.0
Assignee: Brad Maxwell
QA Contact: Pavel Slavicek
URL:
Whiteboard:
Depends On: 1198231
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-24 19:43 UTC by Brad Maxwell
Modified: 2019-08-19 12:45 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EJBCLIENT-84 0 Major Resolved If a scoped-context is created and closed with a high frequence there is a "Too many open channels" Exception 2019-09-25 19:14:23 UTC
Red Hat Issue Tracker WFLY-4016 0 Major Closed Memory leak on undeploy caused by ejb client 2019-09-25 19:14:23 UTC
Red Hat Issue Tracker WFLY-4017 0 Major Closed EjbClientContextSetupProcessor uses ServiceRegistry.getService() 2019-09-25 19:14:23 UTC

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
Note You need to log in before you can comment on or make changes to this bug.