[jboss-svn-commits] JBL Code SVN: r29848 - labs/jbosstm/trunk/XTS/sar/tests/dd/scripts.

[jboss-svn-commits at lists.jboss.org]

Author: adinn
Date: 2009-10-28 10:16:19 -0400 (Wed, 28 Oct 2009)
New Revision: 29848

Modified:
   labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/ATCrashDuringOnePhaseCommit.txt
   labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/ATSubordinateCrashDuringCommit.txt
   labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BACrashDuringCommit.txt
   labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BACrashDuringOnePhaseCommit.txt
Log:
modified XTS test scripts to avoid duplicate rule names which upset the latest Byteman agent

Modified: labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/ATCrashDuringOnePhaseCommit.txt
===================================================================
--- labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/ATCrashDuringOnePhaseCommit.txt	2009-10-28 13:19:40 UTC (rev 29847)
+++ labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/ATCrashDuringOnePhaseCommit.txt	2009-10-28 14:16:19 UTC (rev 29848)
@@ -274,7 +274,7 @@
 # This rule is triggered when a non-recovered participant engine
 # (ParticipantEngine) receives a prepare message. It traces the call.
 
-RULE trace coordinator prepare
+RULE trace participant prepare
 CLASS com.arjuna.wst11.messaging.engines.ParticipantEngine
 METHOD prepare
 AT SYNCHRONIZE

Modified: labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/ATSubordinateCrashDuringCommit.txt
===================================================================
--- labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/ATSubordinateCrashDuringCommit.txt	2009-10-28 13:19:40 UTC (rev 29847)
+++ labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/ATSubordinateCrashDuringCommit.txt	2009-10-28 14:16:19 UTC (rev 29848)
@@ -329,7 +329,7 @@
 # (SubordinateDurable2PCStub) is requested to send a prepared message. It
 # traces the call.
 
-RULE trace subordinate participant stub prepare
+RULE trace subordinate participant stub prepare 2
 CLASS com.arjuna.wst11.stub.SubordinateDurable2PCStub
 METHOD prepare
 AFTER INVOKE prepare
@@ -545,7 +545,7 @@
 # (SubordinateCoordinator) is requested to perform a commit. It
 # traces the call.
 
-RULE trace subordinate coordinator commit
+RULE trace subordinate coordinator commit 2
 CLASS com.arjuna.mwlabs.wscf.model.twophase.arjunacore.subordinate.SubordinateCoordinator
 METHOD commit
 AT EXIT
@@ -583,7 +583,7 @@
 # It prints a message which can be used to verify that the test has
 # progressed as expected
 
-RULE trace prepared replay
+RULE trace subordinate prepared replay
 CLASS org.jboss.jbossts.xts.recovery.coordinator.at.RecoverSubordinateCoordinator
 METHOD replayPhase2
 AT INVOKE removeRecoveredCoordinator

Modified: labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BACrashDuringCommit.txt
===================================================================
--- labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BACrashDuringCommit.txt	2009-10-28 13:19:40 UTC (rev 29847)
+++ labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BACrashDuringCommit.txt	2009-10-28 14:16:19 UTC (rev 29848)
@@ -322,7 +322,7 @@
 # a close message. It exits the JVM, simulating a crash.
 # The trigger location is on entry
 
-RULE kill JVM at participant completion close
+RULE kill JVM at coordinator completion close
 CLASS com.arjuna.wst11.messaging.engines.CoordinatorCompletionCoordinatorEngine
 METHOD close
 AT ENTRY
@@ -341,7 +341,7 @@
 # participant stub (CoordinatorCompletionCoordinatorEngine) is requested
 # to send a complete message. It traces the call.
 
-RULE trace coordinator completion close
+RULE trace coordinator completion complete
 CLASS com.arjuna.wst11.messaging.engines.CoordinatorCompletionCoordinatorEngine
 METHOD complete
 AFTER SYNCHRONIZE
@@ -430,6 +430,7 @@
 # located in the log record. It traces the create operation
 # The trigger location is at entry but the rule should only be triggered
 # after calling the super constructor
+
 RULE trace participant completion engine create
 CLASS com.arjuna.wst11.messaging.engines.ParticipantCompletionCoordinatorEngine
 METHOD <init>(String, boolean, W3CEndpointReference, State, boolean)
@@ -447,6 +448,7 @@
 # located in the log record. It traces the create operation
 # The trigger location is at entry but the rule should only be triggered
 # after calling the super constructor
+
 RULE trace coordinator completion engine create
 CLASS com.arjuna.wst11.messaging.engines.CoordinatorCompletionCoordinatorEngine
 METHOD <init>(String, boolean, W3CEndpointReference, State, boolean)

Modified: labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BACrashDuringOnePhaseCommit.txt
===================================================================
--- labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BACrashDuringOnePhaseCommit.txt	2009-10-28 13:19:40 UTC (rev 29847)
+++ labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BACrashDuringOnePhaseCommit.txt	2009-10-28 14:16:19 UTC (rev 29848)
@@ -359,7 +359,7 @@
 # participant (CoordinatorCompletionParticipantEngine) receives
 # a close message. It exits the JVM, simulating a crash.
 
-RULE kill JVM at participant completion participant close
+RULE kill JVM at coordinatior completion participant close
 CLASS com.arjuna.wst11.messaging.engines.CoordinatorCompletionParticipantEngine
 METHOD close
 AT ENTRY