13 Replies Latest reply on Sep 16, 2008 9:10 AM by Mark Little

    Recovery Warning

    Horea Abrudan Newbie

      Hi,

      We started using the TS for distributed trx coordintation and are getting the following warning:

      2008-08-05 15:12:37,526 [main] WARN com.arjuna.ats.jts.logging.loggerI18N - [com.arju
      na.ats.internal.jts.recovery.RecoveryEnablement_1] [com.arjuna.ats.internal.jts.recove
      ry.RecoveryEnablement_1] - added ORBAttribute for recoveryCoordinatorInitialiser
      2008-08-05 15:12:39,463 [main] WARN com.arjuna.ats.jts.logging.loggerI18N - [com.arju
      na.ats.internal.jts.recovery.RecoveryEnablement_1] [com.arjuna.ats.internal.jts.recove
      ry.RecoveryEnablement_1] - added ORBAttribute for recoveryCoordinatorInitialiser
      2008-08-05 15:12:41,298 [main] WARN com.arjuna.ats.jts.logging.loggerI18N - [com.arju
      na.ats.internal.jts.recovery.RecoveryEnablement_1] [com.arjuna.ats.internal.jts.recove
      ry.RecoveryEnablement_1] - added ORBAttribute for recoveryCoordinatorInitialiser
      2008-08-05 15:12:48,809 [RecoveryManagerScanThread] WARN com.arjuna.ats.arjuna.loggin
      g.arjLoggerI18N - [com.arjuna.ats.arjuna.recovery.RecoverAtomicAction_4] - RecoverAtom
      icAction: transaction not activated, unable to replay phase 2 commit
      2008-08-05 15:12:52,722 [RecoveryManagerScanThread] WARN com.arjuna.ats.arjuna.loggin
      g.arjLoggerI18N - [com.arjuna.ats.arjuna.recovery.RecoverAtomicAction_4] - RecoverAtom
      icAction: transaction not activated, unable to replay phase 2 commit

      It is not related to disk space as it was suggested somewhere else.
      Any other suggestions?

      Thanks,
      Adrian

        • 1. Re: Recovery Warning
          Horea Abrudan Newbie

          In addition I found these other warnings posted in the log file:

          2008-08-18 14:10:14,929 [Thread-17] WARN com.arjuna.ats.jta.logging.loggerI18N - [com
          .arjuna.ats.internal.jta.resources.arjunacore.commitxaerror] [com.arjuna.ats.internal.
          jta.resources.arjunacore.commitxaerror] XAResourceRecord.commit - xa error XAException
          .XAER_NOTA
          2008-08-18 14:10:15,605 [Thread-17] WARN com.arjuna.ats.jta.logging.loggerI18N - [com
          .arjuna.ats.internal.jta.resources.arjunacore.commitxaerror] [com.arjuna.ats.internal.
          jta.resources.arjunacore.commitxaerror] XAResourceRecord.commit - xa error XAException
          .XAER_NOTA
          2008-08-18 14:10:15,608 [Thread-17] WARN com.arjuna.ats.arjuna.logging.arjLoggerI18N - [com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore_9] - ShadowingStore::remove_state() - access problems on -6d2186c9:e7e7:48a9c0f0:2cb5a and /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction
          2008-08-18 14:10:15,608 [Thread-17] WARN com.arjuna.ats.arjuna.logging.arjLoggerI18N
          - [com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore_10] - ShadowingStore::remove_state() - state -6d2186c9:e7e7:48a9c0f0:2cb5a does not exist for type /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction

          --
          Adrian

          • 2. Re: Recovery Warning
            Mark Little Master

             

            "abrudho" wrote:
            Hi,

            We started using the TS for distributed trx coordintation and are getting the following warning:

            2008-08-05 15:12:37,526 [main] WARN com.arjuna.ats.jts.logging.loggerI18N - [com.arju
            na.ats.internal.jts.recovery.RecoveryEnablement_1] [com.arjuna.ats.internal.jts.recove
            ry.RecoveryEnablement_1] - added ORBAttribute for recoveryCoordinatorInitialiser


            This is an interesting one because the actual message is definitely broken and we'll fix that. But ignoring that, it's supposed to be telling you that it has not been able to find the right supported ORB.


            2008-08-05 15:12:39,463 [main] WARN com.arjuna.ats.jts.logging.loggerI18N - [com.arju
            na.ats.internal.jts.recovery.RecoveryEnablement_1] [com.arjuna.ats.internal.jts.recove
            ry.RecoveryEnablement_1] - added ORBAttribute for recoveryCoordinatorInitialiser
            2008-08-05 15:12:41,298 [main] WARN com.arjuna.ats.jts.logging.loggerI18N - [com.arju
            na.ats.internal.jts.recovery.RecoveryEnablement_1] [com.arjuna.ats.internal.jts.recove
            ry.RecoveryEnablement_1] - added ORBAttribute for recoveryCoordinatorInitialiser
            2008-08-05 15:12:48,809 [RecoveryManagerScanThread] WARN com.arjuna.ats.arjuna.loggin
            g.arjLoggerI18N - [com.arjuna.ats.arjuna.recovery.RecoverAtomicAction_4] - RecoverAtom
            icAction: transaction not activated, unable to replay phase 2 commit
            2008-08-05 15:12:52,722 [RecoveryManagerScanThread] WARN com.arjuna.ats.arjuna.loggin
            g.arjLoggerI18N - [com.arjuna.ats.arjuna.recovery.RecoverAtomicAction_4] - RecoverAtom
            icAction: transaction not activated, unable to replay phase 2 commit


            This means that we have not been able to activate the log image for a recovering transaction. Could be related to the previous warning if you have not got a good configuration.

            • 3. Re: Recovery Warning
              Mark Little Master

               

              "abrudho" wrote:
              In addition I found these other warnings posted in the log file:

              2008-08-18 14:10:14,929 [Thread-17] WARN com.arjuna.ats.jta.logging.loggerI18N - [com
              .arjuna.ats.internal.jta.resources.arjunacore.commitxaerror] [com.arjuna.ats.internal.
              jta.resources.arjunacore.commitxaerror] XAResourceRecord.commit - xa error XAException
              .XAER_NOTA
              2008-08-18 14:10:15,605 [Thread-17] WARN com.arjuna.ats.jta.logging.loggerI18N - [com
              .arjuna.ats.internal.jta.resources.arjunacore.commitxaerror] [com.arjuna.ats.internal.
              jta.resources.arjunacore.commitxaerror] XAResourceRecord.commit - xa error XAException
              .XAER_NOTA
              2008-08-18 14:10:15,608 [Thread-17] WARN com.arjuna.ats.arjuna.logging.arjLoggerI18N - [com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore_9] - ShadowingStore::remove_state() - access problems on -6d2186c9:e7e7:48a9c0f0:2cb5a and /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction
              2008-08-18 14:10:15,608 [Thread-17] WARN com.arjuna.ats.arjuna.logging.arjLoggerI18N
              - [com.arjuna.ats.internal.arjuna.objectstore.ShadowingStore_10] - ShadowingStore::remove_state() - state -6d2186c9:e7e7:48a9c0f0:2cb5a does not exist for type /StateManager/BasicAction/TwoPhaseCoordinator/AtomicAction

              --
              Adrian


              Two different errors, both of which are not good. Check your disk space for a start.

              • 4. Re: Recovery Warning
                Horea Abrudan Newbie

                Dr. Little,

                Thank you for the info. I would like to ask for some more clarifications - I am new to Arjuna TS:

                - how can I fix the supported ORB initialization issue? Shouldn't this be an error rather than a warning?
                - similarly, the additional warnings should be also error messages as they suggest recovery cannot proceed;
                - this is not a disk space issue in our case - plenty of space ~80GB; I was able to find an error log that mentiones a JDBC timeout exception; is it possible that this triggered the recovery? (connection timeout during phase 2 commit?)

                Some background info into our case: usign Arjuna TS from Tibco BW to coordinate among Oracle DB updates and Tibco EMS/JMS sends;
                all resources are XA enabled. The Arjuna TS and recovery service are started by the BW engine.

                Many thanks,
                Adrian

                • 5. Re: Recovery Warning
                  Mark Little Master

                  Hi Adrian. If you are using ArjunaTS as it comes with Tibco Business Works then you need to work through Tibco for support. JBossTS is 3 years ahead of ArjunaTS these days and any answers we might give you on this forum are probably going to conflict with ArjunaTS in one way or another.

                  • 6. Re: Recovery Warning
                    Horea Abrudan Newbie

                    Hi,

                    Thank you for the clarification.
                    Actually, we are not using the Arjuna that come with Tibco; we downloaded the latest JBoss TS and we are trying to integrate this with Tibco BW.

                    Just to clarify, does JBoss TS support the ORB implementation that comes with jdk 1.5?

                    java version "1.5.0_07"
                    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
                    Java HotSpot(TM) Client VM (build 1.5.0_07-b03, mixed mode, sharing)

                    Thank you,
                    Horea

                    • 7. Re: Recovery Warning
                      Horea Abrudan Newbie

                      Hi,

                      Am also wondering if there is way to find out what the issue was and with which resource from the recovery logs.

                      Thank you,
                      Adrian

                      • 8. Re: Recovery Warning
                        Mark Little Master

                        Is there some reason you aren't talking with TIBCO to get this sorted?

                        • 9. Re: Recovery Warning
                          Horea Abrudan Newbie

                          They only support an older version.
                          Also it turns out we need a separate license in order to use their integrated Arjuna TS.

                          • 10. Re: Recovery Warning
                            Mark Little Master

                            It's been a long time since I worked on the BW integration. JBossTS has certainly evolved since then. JBoss does not currently have TIBCO support as a tier N platform. For obvious reasons, our focus is JBossAS. Maybe you can convince TIBCO to upgrade their support and adopt JBossTS? We'd be happy to assist if necessary.

                            • 11. Re: Recovery Warning
                              Horea Abrudan Newbie

                              I understand.

                              However, can you give me some pointers on where to look to gather some more info? I want to undestand what is the error about and what is our exposure.

                              Thank you,
                              Adrian

                              • 12. Re: Recovery Warning
                                Horea Abrudan Newbie


                                Again, does anybody know of any diagnostics that we can run to find the cause of these warnings?

                                Much appreciated,
                                Adrian

                                • 13. Re: Recovery Warning
                                  Mark Little Master

                                  Turn on full debug. Check disk space. Attach a debugger. Speak with TIBCO as to what ORB they say that BW will support.