[
https://issues.jboss.org/browse/ISPN-845?page=com.atlassian.jira.plugin.s...
]
Manik Surtani commented on ISPN-845:
------------------------------------
@Galder, all tests should _not_ hardcode the JTA manager impl. Instead, the switch should
be made by using -Dinfinispan.test.jta.tm=jbosstm
See
http://community.jboss.org/wiki/InfinispanandMaven#Running_permutations_m...
I had tested ReadOnlyTxCleanupTest with JBoss TS as per the sys property (and this is
observed in the logs). Will try again and see if I can recreate your issue.
Memory leaks for 2 phase commit readonly transaction
----------------------------------------------------
Key: ISPN-845
URL:
https://issues.jboss.org/browse/ISPN-845
Project: Infinispan
Issue Type: Bug
Components: Transactions
Affects Versions: 4.2.0.Final
Reporter: Changgeng Li
Assignee: Manik Surtani
Priority: Blocker
Fix For: 4.2.1.Final
Attachments: infinispan.log
If a method that is declared with read only transactional attribute by
'@Transactional(readOnly=true)', using jboss transaction manager, and inside this
method two caches are visited, there will be memory leak after the method is invoked.
The leak happens in TransactionTable instances, localTransactions map and xid2LocalTx
map. It seems the commit phrase is skipped and the cleanup method is failed to be called
to clean entries in these two maps.
My test shows if the transaction just enlists one cache, there won't be any problems,
but I haven't test whether using DummyTransactionManagerLookup will resolve this.
This bug break our system where readOnly DAO methods are heavily used with infinispan as
hibernate second level cache.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira