[jbossts-issues] [JBoss JIRA] (JBTM-1146) XTS Demo: ServiceStateManager fails to rollback during recovery as TXID is not known.

Amos Feng (JIRA) jira-events at lists.jboss.org
Tue May 29 10:09:18 EDT 2012


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

Amos Feng commented on JBTM-1146:
---------------------------------

rollback happens when restoreState() load from shadowFile which should not exists and txId is null at this time.
It dues to renameTo function on windows will be fail when commitShadowState rename shadowFile to stateFile.
I raise JTBM-1176 to track the issue of not launching firefox sometimes.
                
> XTS Demo: ServiceStateManager fails to rollback during recovery as TXID is not known.
> -------------------------------------------------------------------------------------
>
>                 Key: JBTM-1146
>                 URL: https://issues.jboss.org/browse/JBTM-1146
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: XTS
>    Affects Versions: 5.0.0.M1
>            Reporter: Paul Robinson
>            Assignee: Amos Feng
>             Fix For: 4.16.5, 5.0.0.M2
>
>
> See: 
> http://172.17.131.2/job/btny-quickstarts/108/consoleText
> http://172.17.131.2/job/btny-quickstarts/141
> In particular, notice the NPE from:
> {code}
>     /**
>      * release a derived state previously stored using the transaction id as a lookup key
>      * @param txId the id of the transaction which created the derived state
>      */
>     protected void removeState(Object txId)
>     {
>         transactions.remove(txId);
>     }
> {code}
> I don't yet know:
> A) If recovery should even be happening in this part of the test.
> B) Assuming recovery should happen, I don't know if the outcome should be rollback; which is what it looks like is happening here.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbossts-issues mailing list