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

Mark Little (JIRA) jira-events at lists.jboss.org
Mon Jun 29 08:36:57 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBTM-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Little updated JBTM-570:
-----------------------------

    Issue Type: Task  (was: Bug)


> 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

        



More information about the jbossts-issues mailing list