-
Bug
-
Resolution: Done
-
Major
-
4.0.13.Final
-
None
This is follow-up to change in WildFly transaction client by WFTC-54. The transaction with timeout of 0 does not accept enlistment of resources anymore and throws SystemException.
The incoming call from ejb client of version prior to 2.0 sets the transaction timeout to 0. That would cause canceling the processing of any incoming call from clients prior to that version.
The transaction should be set with default timeout instead of 0.
- is cloned by
-
JBEAP-16402 (7.2.z) EJBCLIENT-316 - Incoming call from client of version prior to 2.0 sets transaction timeout to 0
- Closed
- is related to
-
WFLY-11849 Narayana XTS txbridge not permitting to start transaction when no timeout is set
- Closed
- relates to
-
WFTC-54 Integration with Narayana fails when timeout propagation over remote call declares it as '0'
- Resolved
-
WFLY-11687 Upgrade JBoss EJB Client to 4.0.14.Final
- Closed