Loading...

XML

Word

Printable

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Fix Build:
ER3
Target Release:

7.1.0.GA
Steps to Reproduce:

Hide

Uncomment the lines validating this condition here:
https://github.com/wildfly/wildfly/blob/master/testsuite/integration/clustering/src/test/java/org/jboss/as/test/clustering/cluster/ejb/remote/TransactionalRemoteStatefulEJBFailoverTestCase.java#L108

Show
Uncomment the lines validating this condition here: https://github.com/wildfly/wildfly/blob/master/testsuite/integration/clustering/src/test/java/org/jboss/as/test/clustering/cluster/ejb/remote/TransactionalRemoteStatefulEJBFailoverTestCase.java#L108

Issue only affects the case where the UserTransaction was obtained via the deprecated EJBClient.getUserTransaction(String) method.

This should throw an ISE or similar. The failover target node would lack the requisite transaction context necessary to handle the invocation.

clones

EJBCLIENT-247 EJB client allows failover of an EJB invocation with an active client transaction obtained via legacy EJBClient method