Compatibility problem: allow a timeout value of "0" to be set ------------------------------------------------------------- Key: WFLY-9955 URL: https://issues.jboss.org/browse/WFLY-9955 Project: WildFly Issue Type: Bug Components: Transactions Reporter: David Lloyd Assignee: Amos Feng Fix For: 14.0.0.CR1 Previously we allowed a transaction timeout value of "0" to be set in the transaction subsystem, meaning "no transaction timeout". After the WF 11 changes, we've stopped allowing that value to be set. This behavior should be restored, with "0" translating into some "very large" value. The transaction team has indicated that using {{Integer.MAX_VALUE}} has historically exhibited problems, so a different, smaller-but-still-large value should be used in this case.