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

[Ondra Chaloupka (JIRA)]

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

Ondra Chaloupka commented on WFLY-9955:
---------------------------------------

I think there was some issue with Artemis. I just found the reference (possibly?) here: https://issues.jboss.org/browse/JBEAP-11701?focusedCommentId=13425705#comment-13425705. It seems the error has not been fixed, don't you know [~zhfeng] ?

[~dmlloyd] I'm still in doubt, sorry :), why the default timeout could not be undefined (with value set to {{0}})? For example {{XAResource}} count with such value (https://docs.oracle.com/javaee/7/api/javax/transaction/xa/XAResource.html#setTransactionTimeout-int-). 

> 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)