Details

    • Type: Feature Request
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: 4.2
    • Fix Version/s: 4.2.2
    • Component/s: JTA, JTS
    • Labels:
      None

      Description

      Currently the Recovery Manager begins working as soon as JBossAS starts. When the local JTA implementation is used and there is a transaction to recover, we get the following stack trace:

      10:52:35,529 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.restorestate] [com.arjuna.ats.interna\
      l.jta.resources.arjunacore.restorestate] Exception on attempting to restore XAResource
      java.io.StreamCorruptedException: unexpected end of block data
      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1321)
      at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1912)
      at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1836)
      at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1713)
      at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
      at java.io.ObjectInputStream.readObject(ObjectInputStream.java:339)
      at com.arjuna.ats.internal.jta.resources.arjunacore.XAResourceRecord.restore_state(XAResourceRecord.java:879)
      at com.arjuna.ats.arjuna.coordinator.BasicAction.restore_state(BasicAction.java:1410)
      at com.arjuna.ats.arjuna.coordinator.BasicAction.activate(BasicAction.java:711)
      at com.arjuna.ats.arjuna.coordinator.BasicAction.activate(BasicAction.java:673)
      at com.arjuna.ats.arjuna.recovery.RecoverAtomicAction.<init>(RecoverAtomicAction.java:60)
      at com.arjuna.ats.internal.arjuna.recovery.AtomicActionRecoveryModule.doRecoverTransaction(AtomicActionRecovery\
      Module.java:178)

      This is because the rest of the system isn't yet fully initialised. The next periodic run of recovery does not suffer this problem and recovery completes successfully. We should look at delaying the start of the Recovery Manager until JBossAS is fully initialised.

        Gliffy Diagrams

          Attachments

          1. jbossts-properties.xml
            14 kB
          2. jms-ds.xml
            2 kB
          3. server.log
            16 kB

            Issue Links

              Activity

                People

                • Assignee:
                  jhalliday Jonathan Halliday
                  Reporter:
                  marklittle Mark Little
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  1 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 1 day
                    1d