1 Reply Latest reply on Dec 14, 2006 3:26 PM by marklittle

    Question about com.arjuna.ats.jta.xaRecoveryNode

      Based on the JBoss transactions documentation and my tests, it looks like in order for XA recovery to work correctly, the property value com.arjuna.ats.jta.xaRecoveryNode should be configured to match the value configured for com.arjuna.ats.arjuna.xa.nodeIdentifier.

      At Unisys, we are providing a distribution of JBoss 4.0.5 with JBoss TS 4.2.2 preconfigured. Is there some reason why we wouldn't want to add com.arjuna.ats.jta.xaRecoveryNode set to "1" to the jbossjts-properties.xml file that we distribute for our customers? We would then need to document that they should consider changing com.arjuna.ats.arjuna.xa.nodeIdentifier to some unique identifier, and they should change com.arjuna.ats.jta.xaRecoveryNode to match.

        • 1. Re: Question about com.arjuna.ats.jta.xaRecoveryNode
          marklittle

           

          "burdeasa" wrote:
          Based on the JBoss transactions documentation and my tests, it looks like in order for XA recovery to work correctly, the property value com.arjuna.ats.jta.xaRecoveryNode should be configured to match the value configured for com.arjuna.ats.arjuna.xa.nodeIdentifier.


          That's correct.


          At Unisys, we are providing a distribution of JBoss 4.0.5 with JBoss TS 4.2.2 preconfigured. Is there some reason why we wouldn't want to add com.arjuna.ats.jta.xaRecoveryNode set to "1" to the jbossjts-properties.xml file that we distribute for our customers? We would then need to document that they should consider changing com.arjuna.ats.arjuna.xa.nodeIdentifier to some unique identifier, and they should change com.arjuna.ats.jta.xaRecoveryNode to match.


          As long as the node identifier is unique to each JBossTS deployment on a particular node, the value can be whatever you want. If you don't set a value then you will get a warning and one will be created for you.