4 Replies Latest reply on Dec 1, 2009 2:10 PM by Jeremy Levy

    Transaction Recovery -- XAResource + AppServerJDBCXARecovery

    Jeremy Levy Newbie

      Following the work that John Mazz has done in getting XAConnections to be recoverable from his article:

      http://management-platform.blogspot.com/2008/11/transaction-recovery-in-jbossas.html

      I have set up jbossjta-properties.xml in JBoss 4.2.3 for my XA Datasource, however it does seem to do any anything.

      On startup:

      14:45:21,763 DEBUG [AppServerJDBCXARecovery] AppServerJDBCXARecovery datasource classname = com.mysql.jdbc.jdbc2.optional.MysqlXADataSource
      14:45:21,879 DEBUG [AppServerJDBCXARecovery] Created new XAConnection
      14:47:31,896 DEBUG [AppServerJDBCXARecovery] XA datasource does not support isValid method - connection will always be recreated
      14:47:31,931 DEBUG [AppServerJDBCXARecovery] Created new XAConnection
      



      I see the above output after JBoss has started so I know at least that it's being 'configured'. But the transactions never actually get recovered..

      After a failure the following keeps repeating..

      14:51:52,252 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 29, 27, 1-7f000001:eb6b:4b0ae60f:42007f000001:eb6b:4b0ae60f:425a >
      14:51:52,279 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 29, 27, 1-7f000001:eb6b:4b0ae60f:832d7f000001:eb6b:4b0ae60f:83d1 >
      14:51:52,282 WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 29, 27, 1-7f000001:eb6b:4b0ae60f:5ebc7f000001:eb6b:4b0ae60f:5f1b >
      14:51:52,302 DEBUG [AppServerJDBCXARecovery] Created new XAConnection
      


      Shouldn't it be doing more?