You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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...
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
The text was updated successfully, but these errors were encountered: