[ https://issues.jboss.org/browse/WFLY-9955?page=com.atlassian.jira.plugin.... ] Amos Feng commented on WFLY-9955: --------------------------------- https://github.com/wildfly/wildfly/blob/master/transactions/src/main/java... {code} TxControl.setDefaultTimeout(resolvedValue.asInt()); ContextTransactionManager.setGlobalDefaultTransactionTimeout(resolvedValue.asInt()); {code} if the value == 0; TxControl.setDefaultTimeout(0); // the transaction will be never time out. So it is OK to set zero here ContextTransactionManager.setGlobalDefaultTransactionTimeout(0); // this is wrong, so it has to be converted to the maximum timeout which might be Integer.MAX_VALUE [~dmlloyd], I do not understand the necessary to introduce a maximum timeout attribute. I suppose to change the above codes to {code} int timeoutValue = resolvedValue.asInt(); TxControl.setDefaultTimeout(timeoutValue); if (timeoutValue > 0) { timeoutValue = Integer.MAX_VALUE; } ContextTransactionManager.setGlobalDefaultTransactionTimeout(timeoutValue); {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)