[jboss-jira] [JBoss JIRA] (WFLY-9955) Compatibility problem: allow a timeout value of "0" to be set

[David Lloyd (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-9955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13542906#comment-13542906 ] 

David Lloyd commented on WFLY-9955:
-----------------------------------

It is coming from there, but the behavior of that method is not going to be changed.  The change should be made in the handling of the management model attribute in the WildFly code base to allow a value of 0 (but perhaps deprecate it with a warning).  In addition I think we should have a maximum timeout attribute as I said above, but this can be a separate enhancement (with support from WFTC).

> 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: Tom Jenkinson
>
> 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)