Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-352

Memory leak in TransactionReaper._timeouts

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 4.3.0.GA
    • Fix Version/s: 4.4.CR1
    • Component/s: Transaction Core
    • Labels:
      None
    • 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

      Description

      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.

        Gliffy Diagrams

          Attachments

          1. OTSManager.java
            9 kB
          2. PseudoControlWrapper.java
            7 kB
          3. TransactionReaper.java
            35 kB
          4. TransactionReaper.zip
            8 kB

            Activity

              People

              • Assignee:
                adinn Andrew Dinn
                Reporter:
                szivan Ivan Szanto
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: