-
Bug
-
Resolution: Done
-
Blocker
-
4.2.0.Final
-
None
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.
- causes
-
ISPN-6146 XA transactions already committed in prepare as XA_RDONLY fail on commit with "ISPN000112: exception while committing: javax.transaction.xa.XAException"
- Closed
-
WFLY-6109 Using OPTIMISTIC locking results in "ISPN000112: exception while committing: javax.transaction.xa.XAException" on responseDone()
- Closed
- is duplicated by
-
ISPN-868 Running out of memory using Infinispan after adding a small number of entities
- Closed
- relates to
-
ISPN-868 Running out of memory using Infinispan after adding a small number of entities
- Closed