[jbossts-issues] [JBoss JIRA] Updated: (JBTM-81) Delay start of recovery manager

Delay start of recovery manager ------------------------------- Key: JBTM-81 URL: https://jira.jboss.org/browse/JBTM-81 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public(Everyone can see) Components: JTA, JTS Affects Versions: 4.2 Reporter: Mark Little Assignee: Jonathan Halliday Priority: Minor Fix For: 4.2.2 Attachments: jbossts-properties.xml, jms-ds.xml, server.log Time Spent: 1 day Remaining Estimate: 0 minutes 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.