With the introduction of Lazy UT in CR2 (JBEAP-12998) HTTP UT support was broken, however this went undetected by the testsuite due to another bug (EJBCLIENT-247) that covered up the failure by rerouting the proxy over standard the standard remoting protocol, thereby causing the tests to verify remoting behavior as opposed to HTTP behavior. EJBCLIENT-247 was superseded by JBEAP-13343
- incorporates
-
WEJBHTTP-5 Transaction location is never set with RemoteUT
- Resolved
- is caused by
-
EJBCLIENT-247 EJB client allows failover of an EJB invocation with an active client transaction obtained via legacy EJBClient method
- Resolved
-
JBEAP-12998 [GSS](7.1.0) UserTransaction should be lazy to allow node selection (loadbalancing) even if the invocations stick to one node
- Closed
- is incorporated by
-
JBEAP-13343 [GSS] JTA based transaction stickiness
- Closed
-
JBEAP-13363 Upgrade WildFly HTTP client components to 1.0.4.Final
- Closed