BTM
  1. BTM
  2. BTM-49

Suspend/resume not working as expected

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.3.2, 1.3.3
    • Fix Version/s: 1.3.3
    • Labels:
      None
    • Number of attachments :
      0

      Description

      For the following scenario:

      1. start a transaction
      2. create a prepared statement (and keep a reference to it for later use)
      3. execute the statement
      4. suspend the transaction
      5. resume the transaction
      6. execute the prepared statement a second time

      The second execution of the prepared statement (6) will run on an ended resource. (Results may vary: the current tx may get stuck or a new tx may be created)

      This happens because suspend (4) will call xaresource.end(tmsuccess) on all enlisted resources, but resume won't start them immediately.

        Activity

        Hide
        Ludovic Orban added a comment -

        Committed a fix in trunk. I've prepared and uploaded a snapshot build: http://snapshots.repository.codehaus.org/org/codehaus/btm/btm/1.3.3-20090804/

        Show
        Ludovic Orban added a comment - Committed a fix in trunk. I've prepared and uploaded a snapshot build: http://snapshots.repository.codehaus.org/org/codehaus/btm/btm/1.3.3-20090804/
        Hide
        Ludovic Orban added a comment -
        Show
        Ludovic Orban added a comment - resolved by http://snapshots.repository.codehaus.org/org/codehaus/btm/btm/1.3.3-20090829/ which will make it to 1.3.3-RC2.
        Show
        Ludovic Orban added a comment - discussed in forum: http://www.nabble.com/Suspend-resume-not-working-as-expected-td24517470.html

          People

          • Assignee:
            Ludovic Orban
            Reporter:
            Adrian Miron
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: