[jboss-jira] [JBoss JIRA] (WFLY-6214) Change CMTTxInterceptor.endTransaction() handling of status'

[Tom Jenkinson (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-6214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168177#comment-13168177 ] 

Tom Jenkinson commented on WFLY-6214:
-------------------------------------

I have made it a blocker as during the work for this I noticed that the status_rolling_back was not resulting in a rollback. Although parallel commit should not be possible in CMT (I still protected for it) parallel rollback is possible due to the reaper.

> Change CMTTxInterceptor.endTransaction() handling of status'
> ------------------------------------------------------------
>
>                 Key: WFLY-6214
>                 URL: https://issues.jboss.org/browse/WFLY-6214
>             Project: WildFly
>          Issue Type: Bug
>          Components: EJB, Transactions
>            Reporter: Scott Marlow
>            Priority: Blocker
>             Fix For: 10.1.0.Final
>
>
> See recent comment [https://developer.jboss.org/message/950898#950898]
> {quote}
> Status.STATUS_COMMITTING:
> Status.STATUS_COMMITTED:
> Status.STATUS_PREPARED:
> Status.STATUS_PREPARING:
> * Someone has called commit in parallel and the transaction is trying to commit so try to commit too: call tm.commit
> {quote}
> I think that TimerCMTTxInterceptor/LifecycleCMTTxInterceptor are using CMTTxInterceptor.endTransaction(), so they shouldn't need changes.
> Status.STATUS_ROLLING_BACK can happen if the reaper has started to rollback the transaction



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)