Back to bug 1007608

Who When What Removed Added
James Livingston 2013-09-12 23:12:44 UTC Blocks 1007312
James Livingston 2013-09-12 23:15:09 UTC Doc Text Cause: TransactionSynchronizer leaked memory if the Transaction hashCode was not stable.

Consequence: The memory leak could cause OutOfMemoryErrors after a period of time.

Fix: Make the class not leak memory.

Result: There are no OutOfMemoryErrors caused by this.
Ondrej Chaloupka 2013-09-16 11:39:11 UTC CC ochaloup
mark yarborough 2013-09-26 20:26:49 UTC CC myarboro
Blocks 1012664
Ivo Studensky 2013-10-03 13:41:07 UTC Status NEW ON_QA
CC istudens
Target Milestone --- ER1
Vladimir Rastseluev 2013-10-07 07:32:25 UTC Status ON_QA VERIFIED
Scott Mumford 2013-11-18 21:53:07 UTC CC smumford
Doc Text Cause: TransactionSynchronizer leaked memory if the Transaction hashCode was not stable.

Consequence: The memory leak could cause OutOfMemoryErrors after a period of time.

Fix: Make the class not leak memory.

Result: There are no OutOfMemoryErrors caused by this.
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.
mark yarborough 2013-12-15 16:17:15 UTC Status VERIFIED CLOSED
Resolution --- CURRENTRELEASE
Last Closed 2013-12-15 11:17:15 UTC
John Skeoch 2014-01-13 00:22:36 UTC CC pslavice
John Skeoch 2016-02-22 00:56:30 UTC CC joallen

Back to bug 1007608