Bug 1007608 - Memory leak if hashCode of Transaction isn't stable
Summary: Memory leak if hashCode of Transaction isn't stable
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JCA
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER1
: EAP 6.2.0
Assignee: Jesper Pedersen
QA Contact: Vladimir Rastseluev
Russell Dickenson
URL:
Whiteboard:
Depends On: 999522
Blocks: 1007312 1012664
TreeView+ depends on / blocked
 
Reported: 2013-09-12 23:11 UTC by James Livingston
Modified: 2016-02-22 00:56 UTC (History)
6 users (show)

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.
Clone Of:
Environment:
Last Closed: 2013-12-15 16:17:15 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBJCA-1070 0 Critical Closed Memory leak if hashCode of Transaction isn't stable 2015-06-23 13:35:51 UTC

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