Bug 1007608

Summary:	Memory leak if hashCode of Transaction isn't stable
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	James Livingston <jlivings>
Component:	JCA	Assignee:	Jesper Pedersen <jpederse>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Vladimir Rastseluev <vrastsel>
Severity:	unspecified	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.1.1	CC:	istudens, joallen, myarboro, ochaloup, pslavice, smumford
Target Milestone:	ER1
Target Release:	EAP 6.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	The JCA TransactionSynchronizer was found to leak memory if the Transaction hashCode was not stable. This memory leak could cause OutOfMemoryErrors after a period of time. An update to the JCA component has corrected this potential lead and the associated OutOfMemoryErrors no longer present.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-12-15 16:17:15 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:
Bug Depends On:	999522
Bug Blocks:	1007312, 1012664

Description James Livingston 2013-09-12 23:11:12 UTC

TransactionSynchronizer leaks memory if the Transaction HashCode isn't stable.  The upgrade from bug 999522 fixes this for 6.2, and this bug is being opened for tracking purposes.

Comment 1 Ivo Studensky 2013-10-03 13:41:07 UTC

Fixed in EAP 6.2.0.ER1.

Comment 3 Vladimir Rastseluev 2013-10-07 07:32:25 UTC

Verified on EAP 6.2.0 ER4

Comment 6 Scott Mumford 2013-11-18 21:53:07 UTC

Reformatted Doc Text content for inclusion in 6.2 Release Notes.