JBEAP-12998 covered Remote User Transactions. GSS raised a related follow-up, that cluster invocations should stick to a node based on a client's usage of JTA transactions as well. The primary use-case, is alleviating issues with EntityManager flush on an SLSB that can occur when multiple nodes are involved in the same transaction. Additionally there is the possibility of database issues from multiple connections on the same Xid.
(Note to QE for verification: The solution in the linked EJBCLIENT-276 includes test coverage for both Remote UT and JTA (local tx)
- incorporates
-
EJBCLIENT-276 Add support for JTA stickiness
-
- Resolved
-
-
JBEAP-13364 EJB over HTTP always fails with UserTransaction usage
-
- Verified
-
- is incorporated by
-
-
- Verified
-
- relates to
-
JBEAP-12998 [GSS](7.1.0) UserTransaction should be lazy to allow node selection (loadbalancing) even if the invocations stick to one node
-
- Verified
-
