Memory leak using TransactionDelegate and transaction.commit() [SPR-6991]

[spring-projects-issues]

Christophe Rodriguez opened SPR-6991 and commented

When calling transaction.commit/rollback instead of transactionManager.commit/rollback in the class TransactionDelegate.endTransaction the TransactionManager doesn't unassociate the transaction.

The list of associatedTransactions in org.apache.geronimo.transaction.manager.TransactionManagerImpl keeps de reference of the transaction indefinitely.

Beans:
<jms:jca-listener-container />
org.apache.activemq.ra.ActiveMQResourceAdapter
org.jencks.factory.TransactionManagerFactoryBean

---

Affects: 2.5.6

Referenced from: commits 4e7752c

[spring-projects-issues]

Juergen Hoeller commented

We weren't aware of that difference between TransactionManager.commit() and Transaction.commit(), and I suppose it may be somewhat specific to Geronimo. Nevertheless, we revised our arrangement there to delegate to TransactionManager.commit/rollback() underneath the Transaction cover.

So as of Spring 3.0.2, this should work fine with Geronimo as well. The change will be available in tonight's 3.0.2 snapshot. Feel free to give it an early try - let us know whether it works for you...

Juergen

[spring-projects-issues]

Christophe Rodriguez commented

Tests OK with version 3.0.2.CI-627.
There is no more memory leak.