1 Reply Latest reply on Aug 12, 2009 9:49 PM by Sean McCauliff

    Can't get trivial transaction recovery example to work.

    Sean McCauliff Newbie

      This local transaction manager example http://www.jboss.org/community/wiki/JBossTSRecovery on the wiki does not work for me. I'm using the 4.7GA release of JBoss transactions.

      When I run Test without "-recover" I get the following output:

      2009-08-07 12:24:03,781 INFO [main:JakartaLogger.info] --- Start RecoveryActivators
      2009-08-07 12:24:03,788 INFO [main:JakartaLogger.info] [com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery_13] - Recovery manager listening on endpoint 127.0.0.1:34,039
      2009-08-07 12:24:03,792 INFO [main:JakartaLogger.info] [com.arjuna.ats.internal.arjuna.recovery.socketready] RecoveryManagerImple is ready on port 34,039
      2009-08-07 12:24:03,878 WARN [main:JakartaLogger.warn] [com.arjuna.ats.arjuna.coordinator.TxControl_1] - Name of XA node not defined. Using -701792c9:d2eb:4a7c7f53:0
      2009-08-07 12:24:03,959 INFO [main:JakartaLogger.info] [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_1] - Starting service com.arjuna.ats.arjuna.recovery.ActionStatusService on port 47306
      2009-08-07 12:24:03,961 INFO [main:JakartaLogger.info] TransactionStatusManagerItem - host: 127.0.0.1 port: 47306
      2009-08-07 12:24:03,980 INFO [main:JakartaLogger.info] [com.arjuna.ats.arjuna.recovery.TransactionStatusManager_3] - TransactionStatusManager started on port 47306 and host 127.0.0.1 with service com.arjuna.ats.arjuna.recovery.ActionStatusService
      ExampleXAResource: ExampleXAResource (Constructor)
      ExampleXAResource: setTransactionTimeout
      ExampleXAResource: start
      ExampleXAResource: ExampleXAResource (Constructor)
      ExampleXAResource: isSameRM
      ExampleXAResource: setTransactionTimeout
      ExampleXAResource: start
      ExampleXAResource: end
      ExampleXAResource: prepare
      ExampleXAResource: end
      ExampleXAResource: prepare
      ExampleXAResource: writeObject (Serialized)
      ExampleXAResource: writeObject (Serialized)
      ExampleXAResource: commit,xid=< 131075, 51, 25, -701792c9:d2eb:4a7c7f53:0--701792c9:d2eb:4a7c7f53:3, -701792c9:d2eb:4a7c7f53:4 >,onePhase=false
      ExampleXAResource: Sleeping 20000 milliseconds


      I then CTRL-C the process and then run again with "-recover" and get the following output.

      2009-08-07 12:27:58,923 INFO [main:?.?] --- Start RecoveryActivators
      2009-08-07 12:27:58,955 INFO [main:PeriodicRecovery.<init>] [com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery_13] - Recovery manager listening on endpoint 127.0.0.1:46,765
      2009-08-07 12:27:58,976 INFO [main:RecoveryManagerImple.<init>] [com.arjuna.ats.internal.arjuna.recovery.socketready] RecoveryManagerImple is ready on port 46,765
      DONE


      None of the resources are deserialized. Does anyone know why the resources are not deserialized and recovered? Should I be using jbossts-jta-4.2.3.SP5?

      Thanks!
      Sean