Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-9955

Compatibility problem: allow a timeout value of "0" to be set

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 14.0.0.Beta2
    • None
    • Transactions
    • None

      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.

              zfeng@redhat.com Zheng Feng
              dlloyd@redhat.com David Lloyd
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: