Bug 971839

Summary:	JGroups Channel not closed after the channel is cleaned up
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Yong Hao Gao <hgao>
Component:	HornetQ	Assignee:	Clebert Suconic <csuconic>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1.0	CC:	mnovak, myarboro
Target Milestone:	ER7
Target Release:	EAP 6.1.1
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-16 20:29:22 UTC	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:

Description Yong Hao Gao 2013-06-07 11:40:55 UTC

Description of problem:

The jgroups channel.close() should be called after the channel is no longer used. See:
org.hornetq.api.core.JGroupsBroadcastGroupConfiguration.JGroupsBroadcastEndpoint.JChannelManager.closeChannel(ChannelKey<?>, String, JChannel)
The closing of channel will clean up threads created by jgroups. If it is not closed, those threads will linger and cause thread leak error in test (see DiscoveryTest)

Version-Release number of selected component (if applicable):


How reproducible:

Run DiscoveryTest

Steps to Reproduce:
1. If you run DiscoveryTest you'll get thread leak failure.

Actual results:
test failure

Expected results:
test pass

Additional info:

Comment 1 JBoss JIRA Server 2013-06-20 20:42:57 UTC

Clebert Suconic <clebert.suconic> updated the status of jira HORNETQ-1223 to Closed

Comment 3 Clebert Suconic 2013-08-20 16:10:46 UTC

this only affected our testcases... not an issue on production, hence no need to document it on release notes

Comment 4 Miroslav Novak 2013-08-22 11:44:55 UTC

BZ is in incorrect state. Fix for this issue is present in EAP 6.1.1.ER7(HQ 2.3.5.Final) 

Verified using provided test in EAP 6.1.1.ER7.