Uploaded image for project: 'JBoss Transaction Manager'
  1. JBoss Transaction Manager
  2. JBTM-570

Failed to recover with empty Tx log

    XMLWordPrintable

Details

    • Task
    • Resolution: Won't Do
    • Major
    • None
    • 4.2.3.SP5
    • Recovery
    • None

    Description

      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.

      Attachments

        Issue Links

          relates to

          Feature Request - Feature requests from customers and/or users JBTM-587 Move potentially corrupt/zero logs once detected

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              nmcl2001 Mark Little
              toigaras@redhat.com tomohisa igarashi
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: