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

XTS txbridge does not run commit when 1PC is used, prepared phase fails on crash recovery later

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 5.9.6.Final
    • 5.9.5.Final
    • XTS
    • None
    • Hide

      From the PR https://github.com/jbosstm/narayana/pull/1391 running the test

      mvn clean install -Parq -Dtest=InboundCrashRecoveryTests#testCrashCommit
      Show
      From the PR https://github.com/jbosstm/narayana/pull/1391 running the test mvn clean install -Parq -Dtest=InboundCrashRecoveryTests#testCrashCommit
    • Workaround Exists
    • Hide

      Forbid the 1PC to be used. Either in WFLY config

      <system-properties>
    <property name="CoordinatorEnvironmentBean.commitOnePhase" value="false"/>
</system-properties>

      or with system property

      -DCoordinatorEnvironmentBean.commitOnePhase=false
      Show
      Forbid the 1PC to be used. Either in WFLY config <system-properties> <property name= "CoordinatorEnvironmentBean.commitOnePhase" value= " false " /> </system-properties> or with system property -DCoordinatorEnvironmentBean.commitOnePhase= false

    Description

      As it seems the crashed inbound txbridge participant finished with rollback after recovery is run on the prepared participant.

      In scenario

      • WS call to the WFLY server
      • inbound bridge injects the JTA transactions as subordinate under the WS AT one
      • prepare is called and the 2PC phase finishes
      • commit phase starts and JVM crashes
      • restart of WFLY server
      • recovery is expected to commit the participants

      the outcome is rollback for the participant not the commit as it's expected. This way the data consistency could be harmed.

      This was discussed at the forum https://developer.jboss.org/thread/279243 as follow-up to the issue JBTM-3079.

      Attachments

        1. server.log
          471 kB
          Ondrej Chaloupka
        2. stacktrace.txt
          18 kB
          Ondrej Chaloupka

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBTM-3079 InboundBridge recovery aborts live transactions

          • Critical - To be worked on immediately following BLOCKER issues.
          • 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-396 Provide one-phase commit optimization for WS-TX

          • 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

              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: