[jbossts-issues] [JBoss JIRA] Commented: (JBTM-234) setRollbackOnly consistency

[Mark Little (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBTM-234?page=comments#action_12365551 ] 
            
Mark Little commented on JBTM-234:
----------------------------------

Now in JTA the code does:

switch (_theTransaction.status())
				{
				case ActionStatus.ABORTED:
				case ActionStatus.ABORTING:
					break;
				default:
					throw new IllegalStateException(
							jtaLogger.logMesg
									.getString("com.arjuna.ats.internal.jta.transaction.arjunacore.inactive"));
				}

when it used to throw IllegalStateException if status() returned false.

> setRollbackOnly consistency
> ---------------------------
>
>                 Key: JBTM-234
>                 URL: http://jira.jboss.com/jira/browse/JBTM-234
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: JTA Implementation
>    Affects Versions: 4.2.3.SP4
>            Reporter: Mark Little
>         Assigned To: Mark Little
>            Priority: Optional
>
> OTS does not let you call rollback-only if the state of the transaction is not active. JTA doesn't make it clear whether or not that is an error. That makes it implementation dependent. At the moment both of our JTA implementations mask this issue. AS appears to not expect an exception from setRollbackOnly either, but that's may cause an issue if someone uses a different JTA.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira