1 Reply Latest reply on Mar 14, 2019 12:09 PM by Thomas Jenkinson

    XTS/RTS inbound bridging does not work on WFLY 16 because of default timeout

    Ondrej Chaloupka Master

      Transactions, imported in the inbound txbridge of XTS and RTS, have set timeout to 0 which was meant to be "never timeout". With changes in the WildFly Transaction Client ([WFTC-54] Integration with Narayana fails when timeout propagation over remote call declares it as '0' - JBoss Issue Tra… ) we can't use the value 0 as "never timeout". The new behaviour of WFTC means the 0 is counted as timeout already elapsed ([WFTC-54] Integration with Narayana fails when timeout propagation over remote call declares it as '0'). My proposal is to change the behaviour to set the timeout for the imported transaction to be the default timeout defined for the transaction manager. In the similar manner as it was done in the EJB client [EJBCLIENT-316] Incoming call from client of version prior to 2.0 sets transaction timeout to 0 - JBoss Issue Tracker .

       

      Is there some feedback about this change? mmusgrov tomjenkinson

       

      My proposed changes are here in PR

      [WFLY-11849] txbridge import transaction to use default timeout not null by ochaloup · Pull Request #1425 · jbosstm/nara…

      [WFLY-11849] Narayana XTS txbridge not permitting to start transaction when no timeout is set - JBoss Issue Tracker