WFTC-54 - Integration with Narayana fails when timeout propagation over remote call declares it as '0' causing UserTransaction timeout to not work -------------------------------------------------------------------------------------------------------------------------------------------------- Key: WFLY-11607 URL: https://issues.jboss.org/browse/WFLY-11607 Project: WildFly Issue Type: Bug Components: Transactions Reporter: Ivo Studensky Assignee: Ivo Studensky Priority: Major If the remote call passes transaction context where timeout is set as `0` then Narayana consider that value as transaction which should never be timetouted. But the wfly txn client consider the `0` as correct timeout value which means kind of `immediate timeout`. The Narayana AtomicAction class consider it as -1[2] (which is used for subordinate transaction[3]) while the transaction reaper consider the value of no timeout to be 0[4]. The client decreases[1] the timeout based on how much time elapsed from the transaction was started till time the remote call is to be accomplished. That means the timeout `0` can be passes even the transaction is not meant as `to never timeout`. [1] https://github.com/wildfly/wildfly-transaction-client/blob/1.1.2.Final/sr... [2] https://github.com/jbosstm/narayana/blob/5.9.2.Final/ArjunaCore/arjuna/cl... [3] https://github.com/jbosstm/narayana/blob/5.9.2.Final/ArjunaJTA/jta/classe... [4] https://github.com/jbosstm/narayana/blob/5.9.2.Final/ArjunaCore/arjuna/cl...