Sticky transactions in JBoss EAP 7.1+

Solution Verified - Updated

Environment

Red Hat JBoss Enterprise Application Platform (EAP) 7.1

Issue

  • Sticky transactions in JBoss EAP 7.1

Resolution

The proxy will prefer the initial node as long as all applications invoked in the same transaction are located on that node (transaction stickiness)

If a second EJB is invoked which is not on that node and both applications are on another node, it will change and prefer the node with all EJBs available.

For bean managed transaction (BMT), beginTx / commit basically enables/disables transaction stickiness

SBR
Product(s)
Components
Category
Tags

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.