[jbossts-issues] [JBoss JIRA] Commented: (JBTM-570) Failed to recover with empty Tx log

[Mark Little (JIRA)]

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

Mark Little commented on JBTM-570:
----------------------------------

If there is a crash during writing of the transaction log then you can end up in a heuristic scenario. Obviously the coordinator cannot do anything (it's crashed!) and we rely on recovery to detect corrupt or zero length logs, where this message is output. However, the recovery system can't rollback the transaction: it crashed; the information about participants has gone or is unreadable. We rely on presumed abort semantics in this case on the part of the participants, though since they have gotten past prepare some may decide to commit whereas others decide to roll back.

> Failed to recover with empty Tx log
> -----------------------------------
>
>                 Key: JBTM-570
>                 URL: https://jira.jboss.org/jira/browse/JBTM-570
>             Project: JBoss Transaction Manager
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Recovery
>    Affects Versions: 4.2.3.SP5
>         Environment: JBoss SOA Platform 4.3.0
> Sun JDK 1.5.0_18
> RHEL5.3, WindowsXP_64
>            Reporter: Tomohisa igarashi
>            Assignee: Mark Little
>
> If JBoss node is down when TransactionManager is at com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore#write_state():751( after creating FOS:ofile before ofile.write() ), the following WARN message is output for a long time, and the transaction is no longer recovered because of an empty Tx log file.
> ----
>   21:41:11,731 WARN  [arjLoggerI18N] [com.arjuna.ats.arjuna.recovery.RecoverAtomicAction_4] - RecoverAtomicAction: transaction not activated, unable to replay phase 2 commit
> ----
> IMO in this case, the transaction should be rollbacked.

-- 
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