8 Replies Latest reply on Nov 27, 2008 6:14 AM by Jonathan Halliday

    Can not get Local JTA recovery sample working on JBoss 4.2.2

    Sergey Zhigunov Newbie

      I am testing local JTA recovery example from http://wiki.jboss.org/wiki/JBossTSRecoveryInAS with JBoss 4.2.2.

      JBoss 4.2.2 uses JBossTM as the default TM. jbossjta_properties.xml already comes with property name="com.arjuna.ats.arjuna.recovery.recoveryExtension3" value="com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule".

      The only change I did was adding
      property name="com.arjuna.ats.jta.xaRecoveryNode" value="*".

      I did not use an EJB, but added code into MBean and triggered transaction using JMX console. The first half of the test works fine, resources get enlisted, prepared and fell asleep on commit. So I kill the JBoss. I can see the entry added to ObjectStore TwoPhaseCoordinator/AtomicAction. But when I start the JBoss again - no recovery is happening.

      I can see log entry
      2008-10-09 15:31:59,986 INFO main [TransactionManagerService] Recovery manager started

      And periodic
      2008-10-09 16:09:15,506 DEBUG Thread-6 [arjLogger] Periodic recovery - first pass <Thu, 9 Oct 2008 16:09:15>
      2008-10-09 16:09:15,506 DEBUG Thread-6 [loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.firstpass] Local XARecoveryModule - first pass
      2008-10-09 16:09:25,506 DEBUG Thread-6 [arjLogger] Periodic recovery - second pass <Thu, 9 Oct 2008 16:09:25>
      2008-10-09 16:09:25,506 DEBUG Thread-6 [loggerI18N] [com.arjuna.ats.internal.jta.recovery.info.secondpass] Local XARecoveryModule - second pass

      The only suspicions log entries on start up are the following (do not know if they indicate a problem):

      2008-10-09 15:32:00,892 DEBUG Thread-5 [arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.TransactionStatusConnector_6] - Failed to establish connection to server
      2008-10-09 15:32:00,939 DEBUG Thread-5 [arjLoggerI18N] [com.arjuna.ats.internal.arjuna.recovery.ExpiredTransactionStatusManagerScanner_3] - Removing old transaction status manager item -3f57e194:1785:48ee5ba8:0

      Can anybody help me with this problem?