Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-26364

(8.0.z) WFTC-141 - Wildfly-transaction-client doesn't log that the transaction timeout wasn't set, when the driver returns false.

    XMLWordPrintable

Details

    Description

      As you can see in https://github.com/wildfly/wildfly-transaction-client/blob/main/src/main/java/org/wildfly/transaction/client/LocalTransaction.java#L176, the output of setTransactionTimeout is being ignored.

      Based on https://docs.oracle.com/javaee%2F6%2Fapi%2F%2F/javax/transaction/xa/XAResource.html#setTransactionTimeout(int), the output of this function determines, whether this function was successful.

      the transaction client do log that the setTransactionTimeout was not successful in case of exception being thrown, but not in case of false returned

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-26363 (7.4.z) WFTC-141 - Wildfly-transaction-client doesn't log that the transaction timeout wasn't set, when the driver returns false.

          • 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.
          • Ready for QA
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-26407 (8.0.z) Upgrade wildfly-transaction-client from 3.0.2.Final-redhat-00001 to 3.0.5.Final-redhat-00001

          • 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
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-26686 (7.4.z) WFTC-142 - Lower logging level to debug for transaction timeout

          • 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.
          • Ready for QA
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-26362 Network failure in prepare phase can cause a permanent table lock-out on Sybase

          • 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.
          • New

          Activity

            People

              lvydra Lukas Vydra
              ogerzica@redhat.com Ondrej Gerzicak
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: