[jbossts-issues] [JBoss JIRA] Commented: (JBTM-352) Memory leak in TransactionReaper._timeouts

[Mark Little (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBTM-352?page=comments#action_12406788 ] 
            
Mark Little commented on JBTM-352:
----------------------------------

"By the way, I only found two places where a non-Reapable is supplied, both in OTSManager.destroyControl. In one case the argument is a Uid, in the other a Control! I am not yet sure if the second case is correct or an error."

The use of Control is actually a legacy from our Orbix2K days and can be removed. We never register CosTransactions::Control instances these days.

> Memory leak in TransactionReaper._timeouts
> ------------------------------------------
>
>                 Key: JBTM-352
>                 URL: http://jira.jboss.com/jira/browse/JBTM-352
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Transaction Core
>    Affects Versions: 4.3.0.GA
>         Environment: Compiled 4.3.0.GA for the EAP 4.3 as JTS according to the instructions (by setting JBOSS_HOME to jboss-5.0.0.Beta4) on RHEL4.
> Run ~ 1500 JMS transactions in EAP 4.3 all configuration on RHEL4 to see it leaks.
> Used Sun jdk 1.5.0.14 
>            Reporter: Ivan Szanto
>         Assigned To: Andrew Dinn
>             Fix For: 4.4.CR1
>
>         Attachments: OTSManager.java, PseudoControlWrapper.java, TransactionReaper.java, TransactionReaper.zip
>
>
> The leak can also be seen by using the debugger to check the number of entries in TransactionReaper._timeouts after a couple of transactions.
> It appears that the TransactionReaper.insert method uses ControlWrapper objects as keys when putting elements into the hashtable, but the TransactionReaper.remove method sometimes unsuccessfully tries to use Uid ojbects to remove them.
> I will post a corrected version of TransactionReaper.java.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira