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
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 4.2.3.SP5
Environment: JBoss SOA Platform 4.3.0
Sun JDK 1.5.0_18
Reporter: Tomohisa igarashi
Assignee: Mark Little
If JBoss node is down when TransactionManager is at
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:
For more information on JIRA, see: http://www.atlassian.com/software/jira