Heap consumption by JBossJTALocalTransactionProvider / High number of TransactionImple instances in a COMMITTED state in JBoss EAP
Issue
- Migrating from EAP 7.0 (or earlier)
- High heap usage is associated with a single instance of
org.wildfly.transaction.client.provider.jboss.JBossJTALocalTransactionProvider. - The
JBossJTALocalTransactionProviderinstance retains thousands of instances ofcom.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImplewhere_theTransaction.actionStatus == 7(ActionStatus.COMMITTED). - Transaction timeout is disabled in the system.
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 7.1
- 7.2
- 7.3
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
