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

Compensation should not be considered done in case of network error

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 5.9.0.Final
    • 5.7.1.Final
    • LRA
    • None
    • Hide
      # Shell 1: listen for connections and print output
      nc -kl 9999
      
      # Shell 2: create a saga
      COORDINATOR_URL=http://localhost:8080/lra-coordinator
      echo "Creating new LRA"
      LRA_URL=$(curl -X POST $COORDINATOR_URL/start | sed "s/\"//g")
      echo "Joining LRA"
      curl -X PUT $LRA_URL -d http://localhost:9999
      echo "Cancel LRA"
      curl -X PUT $LRA_URL/cancel
      
      # From shell 1: ctrl+c to terminate the connection
      # In shell 2: "Compensated" is returned
      # Subsequent "curl $LRA_URL" in shell 2 returns "Invalid transaction id", meaning that LRA is forgotten
      # Restarting "nc -kl 9999" on shell 1 does not produce output anymore
      
      Show
      # Shell 1: listen for connections and print output nc -kl 9999 # Shell 2: create a saga COORDINATOR_URL=http: //localhost:8080/lra-coordinator echo "Creating new LRA" LRA_URL=$(curl -X POST $COORDINATOR_URL/start | sed "s/\" //g") echo "Joining LRA" curl -X PUT $LRA_URL -d http: //localhost:9999 echo "Cancel LRA" curl -X PUT $LRA_URL/cancel # From shell 1: ctrl+c to terminate the connection # In shell 2: "Compensated" is returned # Subsequent "curl $LRA_URL" in shell 2 returns "Invalid transaction id" , meaning that LRA is forgotten # Restarting "nc -kl 9999" on shell 1 does not produce output anymore

      In case of network error on the call to "/compensate" made by the coordinator to the participant, the LRA is considered compensated, hence the compensate action is not retried again. This is not the expected behavior.

              rhn-engineering-mmusgrov Michael Musgrove
              nicolaferraro Nicola Ferraro (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: