Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.3.2, 1.3.3
-
Fix Version/s: 1.3.3
-
Labels:None
-
Number of attachments :
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.
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/