1 Reply Latest reply on Dec 29, 2006 3:11 AM by Mark Little

    status of transaction is different from our status

    Quande Ren Newbie

      Hi there,

      I got following information at slave server when an runtime exception comes out at the slave server where the transaction is proporgated from the master server.

      Can anyone tell me what's the meaning of it?

      17:47:42,062 WARN [loggerI18N] [com.arjuna.ats.internal.jts.orbspecific.interposition.resources.stateerror] ServerSynchronization.after_completion status of transaction is different from our status: <org.omg.CosTransactions.Status@1a8c064, org.omg.CosTransactions.Status@1eee615>

        • 1. Re: status of transaction is different from our status
          Mark Little Master

          When the interposed transaction has completed (either committed or rolled back) it is informed via after_completion of the status of the global (parent) transaction. The two statuses should be the same. Only in exceptional (i.e., heuristic) cases should they be different. For example the subordinate did what it was initially instructed to by the parent during the second phase of the commit protocol, but the parent then went and did something different, or the subordinate made an autonomous choice.

          The warning message should be printing the values of the two statuses (parent and subordinate), but is actually just printing the CORBA objects. We'll fix that http://jira.jboss.com/jira/browse/JBTM-183.