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

recovery for non-unique xids

    XMLWordPrintable

Details

    • Undefined

    Description

      The XARecoveryModule currently assumes xids are globally unique. Sadly the real world isn't that simple...

      In transaction inflow cases it's not possible to change the bqual for each RM, resulting in multiple unrelated RMs potentially having the same xid. When a subordinate transaction recovers, it must correctly match XAResourceRecords to XAResources, but can't rely on the uniqueness of the xid values to do this.

      I placed a reproducer for the issue in my own git repo (I'll convert it to a git patch later so that you can test it against an upstream branch):

      git clone https://github.com/mmusgrov/narayana
      cd narayana/
      git co 4.17-JBTM-3361-reproducer
      ./build.sh clean install -DskipTests -Pall
      ./build.sh test -f ArjunaJTA/jta/pom.xml -Dtest=ImportNonUniqueBranchTest#testNotWrapped

      Attachments

        Issue Links

          is incorporated by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-20309 [GSS](7.3.z) JBTM-3361 - recovery for non-unique xids

          • 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

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

          • 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

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. WFLY-13896 Upgrade Narayana to 5.11.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

          Feature Request - Feature requests from customers and/or users JBTM-859 support XAResourceWrapper

          • 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

          Feature Request - Feature requests from customers and/or users JBTM-622 Support for crash recovery of tx-inflow with multiple resource managers

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Open

          Activity

            People

              rhn-engineering-jhallida Jonathan Halliday
              rhn-engineering-jhallida Jonathan Halliday
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: