Memory Leak in TMLib: RMInterface(java) registerRegion object do not get cleaned up

Bug #1325687 reported by Narendra Goyal
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Trafodion
Fix Released
High
Narendra Goyal

Bug Description

As reported by Peter during the performance runs, there is memory leak in the mxosrvr when running with transactions.

Further investigation, found that the leak is due to the objects being allocated in RMInterface.registerTransaction - and then not getting de-referenced (as the commitTransaction flow does not go through the RMInterface).

Tags: dtm
information type: Proprietary → Public
Revision history for this message
Atanu Mishra (atanu-mishra) wrote :

This defect was repaired in the June release.

Changed in trafodion:
milestone: none → r0.8
status: New → Fix Committed
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.