Uploaded image for project: 'IronJacamar'
  1. IronJacamar
  2. JBJCA-1378

Use new API to determine remaining transaction timeout

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • 1.4.9
    • Core
    • None

    Description

      Wildfly transaction manager no longer implements TransactionTimeoutConfiguration. ContextTransactionManager API should be used instead to determine remaining transaction timeout.

      Related discussions are in https://github.com/wildfly/wildfly-transaction-client/pull/38 and https://issues.jboss.org/browse/WFTC-40

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-13301 [GSS](7.2.0) set-tx-query-timeout does not work at all because ContextTransactionManager does not implement TransactionTimeoutConfiguration#getTimeLeftBeforeTransactionTimeout()

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-13775 [GSS](7.1.z) set-tx-query-timeout does not work at all because ContextTransactionManager does not implement TransactionTimeoutConfiguration#getTimeLeftBeforeTransactionTimeout()

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFTC-40 ContextTransactionManager needs to implement org.jboss.tm.TransactionTimeoutConfiguration

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              thofman Tomas Hofman
              thofman Tomas Hofman
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: