Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-2443

Raise a JTA HeuristicMixed if a one phase commit XAResource raises RMFAIL

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 5.2.0
    • None
    • JTA, JTS
    • None

    Description

      If a one phase commit is performed on an XAResource and it raises RMFAIL we have no way to know whether the resource committed or rolled back. We currently do not raise an exception in this scenario as an interpretation of the XA spec allows us to.

      We have had community feedback that this has an issue for user applications and having consulted with the rest of our community and no negative comments received we will modify the behavior so that this scenario results in the closest exception that JTA allows HeuristicMixed.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBTM-1702 one-phase optimization: XAException by XAResource swallowed and bean invocation falsely a success

          • 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

          Bug - A problem that impairs or prevents the functions of the product. JBTM-3148 Remote JTA EJB transaction context propagation fails to correctly run 1PC

          • 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

          Task - Represents a small unit of work that is not end-user facing. JBTM-692 Check RMFAIL for recovery

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-3200 AMQ returns wrong XA_RETRY XAException error code on connection crash for 1PC

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • 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) JBTM-2459 Add an option to allow JBTM-2443 to be enabled in 4.17

          • 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

              thjenkin@redhat.com Tom Jenkinson
              thjenkin@redhat.com Tom Jenkinson
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: