Java heap is consumed by org.wildfly.transaction.client.provider.remoting.TransactionClientChannel

Solution Verified - Updated

Environment

  • JBoss Enterprise Application Platform (EAP) 7.x

Issue

  • We face OutOfMemoryErrors with high heap consumption in org.wildfly.transaction.client.provider.remoting.TransactionClientChannels peerTransactionMap:
Class Name                                                                             | Shallow Heap | Retained Heap
----------------------------------------------------------------------------------------------------------------------
org.wildfly.transaction.client.provider.remoting.TransactionClientChannel @ 0x641980cd8|           32 | 1,007,952,088
|- peerTransactionMap org.jboss.remoting3._private.IntIndexHashMap @ 0x641980cf8       |           32 | 1,007,952,056
----------------------------------------------------------------------------------------------------------------------

Resolution

  • Update to EAP 7.4.5+ and use its updated jboss-client.jar (wildfly-transaction-client-1.1.15.Final-redhat-00001+ specifically is the independent client jar providing the fix)

Root Cause

Components
Category

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.