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

Error during transaction manager commit of non-XA resource does not provokes exception being thrown

    XMLWordPrintable

Details

    Description

      In case that an exception is thrown during one-phase commit of non-XA transaction participant the error is swallowed and not returned to the caller

      This can happend for example when transaction manager calls commit to the e.g. database resource and connection crash happens. Then jdbc driver returns XAException with error code like XAER_RMFAIL. This fact is not reflected by exception being thrown to the caller (e.g. EJB bean).

      This causes to the fact that user think the work was committed (e.g. INSERT to database) but in fact connection failure happened and nothing was done.

      The fix is part of the Narayana at issue https://issues.jboss.org/browse/JBTM-2983 and it should be released with Narayana 5.7.3.Final

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. JBTM-2983 Commit failure in WFLY LocalResource does not return error to the caller

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-9915 Component upgrade of Narayana to 5.8.0.Final

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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-14293 Component upgrade of Narayana to 5.8.0.Final

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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) WFLY-9679 Duplication of TestXAResource under wildfly testsuite

          • Trivial - Cosmetic problem like misspelt words or misaligned text.
          • Closed

          Activity

            People

              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              ochaloup@redhat.com Ondrej Chaloupka (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: