[jboss-jira] [JBoss JIRA] (WFLY-9955) Compatibility problem: allow a timeout value of "0" to be set
[
https://issues.jboss.org/browse/WFLY-9955?page=com.atlassian.jira.plugin....
]
David Lloyd commented on WFLY-9955:
-----------------------------------
[~ochaloup] it can't be undefined because the JTA spec doesn't have such a concept
for e.g. TransactionManager, so we can't rely on providers always having that
capability. Coupled with it being considered poor practice, I don't feel like we
should introduce this as a supported behavior into any more levels than we need to.
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
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.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)