Bug 1156620 – [GSS](6.4.0) Memory leak on undeploy & too many channels caused by ejb client not disassociating

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

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...

Status:	VERIFIED

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	EJB (Show other bugs)
Sub Component:
Version:	6.3.2
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	CR1
Target Release:	EAP 6.4.0
Assigned To:	Brad Maxwell
QA Contact:	Pavel Slavicek
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1198231
Blocks:
	Show dependency tree / graph

Reported:	2014-10-24 15:43 EDT by Brad Maxwell
Modified:	2018-07-31 17:49 EDT (History)
CC List:	6 users (show)

See Also:
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:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	EJBCLIENT-84	Major	Resolved	If a scoped-context is created and closed with a high frequence there is a "Too many open channels" Exception	2018-01-25 07:39 EST
JBoss Issue Tracker	WFLY-4016	Major	Closed	Memory leak on undeploy caused by ejb client	2018-01-25 07:39 EST
JBoss Issue Tracker	WFLY-4017	Major	Closed	EjbClientContextSetupProcessor uses ServiceRegistry.getService()	2018-01-25 07:39 EST

Groups: None (edit)

Description Brad Maxwell 2014-10-24 15:43:34 EDT

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 15:52:25 EDT

Brad Maxwell <bmaxwell@redhat.com> updated the status of jira WFLY-4016 to Coding In Progress

Comment 4 Kabir Khan 2015-03-02 14:40:44 EST

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 10:48:54 EST

https://github.com/jbossas/jboss-eap/pull/2333

Comment 8 Kabir Khan 2015-03-05 08:22:59 EST

The pull request has been updated to https://github.com/jbossas/jboss-eap/pull/2341

Comment 13 hsvabek 2015-03-17 04:17:16 EDT

It's ok.

Comment 14 JBoss JIRA Server 2015-03-17 22:51:08 EDT

Brad Maxwell <bmaxwell@redhat.com> 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.