XTS Subordinate AT Coordinator passes wrong status to afterCompletion when prepare says
READ_ONLY
-------------------------------------------------------------------------------------------------
Key: JBTM-736
URL:
https://jira.jboss.org/jira/browse/JBTM-736
Project: JBoss Transaction Manager
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: XTS
Affects Versions: 4.10.0
Reporter: Andrew Dinn
Assignee: Andrew Dinn
Fix For: 4.11.0
When WSAT Subordinate Coordinator handles a commitVolatile or a rollbackVolatile call it
assumes that a commit or rollback of its durable participants has already happened and
hence that the relevant outcome has been stored in the transaction (basic action) field
finalStatus. This is used to parameterise a call to afterCompletion, thereby notifying any
local heuristic outcome. However, if the preceding prepare call returned READ_ONLY then
commitVolatile or rollbackVolatile are called without an intervening call to commit or
rollback and finalStatus will not be valid. This special case needs to be detected and
recorded at prepare so that commitVolatile and rollbackVolatile can hardwire call the
values COMMITTED or ABORTED.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira