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

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

Author: adinn
Date: 2009-11-06 07:05:02 -0500 (Fri, 06 Nov 2009)
New Revision: 30055

Modified:
   labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/ATCrashDuringCommit.txt
   labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/ATCrashDuringOnePhaseCommit.txt
   labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BACrashDuringCommit.txt
   labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BACrashDuringOnePhaseCommit.txt
   labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BASubordinateCrashDuringComplete.txt
Log:
tidying up text

Modified: labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/ATCrashDuringCommit.txt
===================================================================
--- labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/ATCrashDuringCommit.txt	2009-11-06 12:03:25 UTC (rev 30054)
+++ labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/ATCrashDuringCommit.txt	2009-11-06 12:05:02 UTC (rev 30055)
@@ -27,7 +27,7 @@
 # JBossTS XTS implementation of the WS-AT 1.1 protocol using orchestration
 # rules. The basic scenario employs a coordinator and 3 web services
 # running in a single JVM but other variants are possible (see below). The
-# scenario is as follows (** indicates intercession by a TOAST rule):
+# scenario is as follows (** indicates intercession by a Byteman rule):
 #
 # AS boots
 # Cient starts a WS-AT activity
@@ -100,12 +100,12 @@
 # omitting to log the activity. In this case the lone participant should be
 # automatically compensated at restart.
 #
-# This script needs to be passed to a TOAST agent in the JVM running
+# This script needs to be passed to a Byteman agent in the JVM running
 # the coordinator service both at first boot and at reboot. Output will be
 # written to file testlog in the working directory of the AS. n.b. the rules in
 # this script only refer to code executed by the coordinator. If the client
 # (the selected XTS Service Test) or the web services are located in another
-# AS/JVM then the other JVM does not require a TOAST agent or script.
+# AS/JVM then the other JVM does not require a Byteman agent or script.
 #
 # XTS Service tests which can operate with this scenario can be selected for
 # execution at AS boot by the XTSServiceTestRunnerBean by setting system

Modified: labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/ATCrashDuringOnePhaseCommit.txt
===================================================================
--- labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/ATCrashDuringOnePhaseCommit.txt	2009-11-06 12:03:25 UTC (rev 30054)
+++ labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/ATCrashDuringOnePhaseCommit.txt	2009-11-06 12:05:02 UTC (rev 30055)
@@ -33,7 +33,7 @@
 # The general scenario differentiates between events happening in the
 # coordinator JVM (AS1) and events happening in the participant JVM (AS2)
 # and rules are categorised according as to which AS they apply to.
-# The scenario is as follows (** indicates intercession by a TOAST rule):
+# The scenario is as follows (** indicates intercession by a Byteman rule):
 #
 # AS1 boots
 # AS2 boots
@@ -103,13 +103,13 @@
 # If the coordinator is in a separate AS then it will need to be killed
 # by the test driver
 #
-# This script needs to be passed to a TOAST agent in the JVM running
+# This script needs to be passed to a Byteman agent in the JVM running
 # the coordinator service both at first boot and at reboot. Output will be
 # written to file testlog in the working directory of the AS.
 # If the participant is not running in the same JVM as the coordinator then
 # this script needs and the supplementary script ATCrashDuringOnePhaseCommitExtra.txt
-# needs to be passed to a TOAST agent in the JVM running the coordinator.
-# This script on its own eneds ot bepassed to a TOAST agent runing in the
+# needs to be passed to a Byteman agent in the JVM running the coordinator.
+# This script on its own eneds ot bepassed to a Byteman agent runing in the
 # participant JVM. Ouptut from the participant will be written to file
 # testlog in the working directory of this second JVM.
 #

Modified: labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BACrashDuringCommit.txt
===================================================================
--- labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BACrashDuringCommit.txt	2009-11-06 12:03:25 UTC (rev 30054)
+++ labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BACrashDuringCommit.txt	2009-11-06 12:05:02 UTC (rev 30055)
@@ -27,7 +27,7 @@
 # JBossTS XTS implementation of the WS-BA 1.1 protocol using orchestration
 # rules. The basic scenario employs a coordinator and 3 web services
 # running in a single JVM but other variants are possible (see below). The
-# scenario is as follows (** indicates intercession by a TOAST rule):
+# scenario is as follows (** indicates intercession by a Byteman rule):
 #
 # AS boots
 # Cient starts a WS-BA activity
@@ -129,12 +129,12 @@
 # either type of participant (alternative B). In this case the completed
 # message should not be traced.
 #
-# This script needs to be passed to a TOAST agent in the JVM running
+# This script needs to be passed to a Byteman agent in the JVM running
 # the coordinator service both at first boot and at reboot. Output will be
 # written to file testlog in the working directory of the AS. n.b. the rules in
 # this script only refer to code executed by the coordinator. If the client
 # (the selected XTS Service Test) or the web services are located in another
-# AS/JVM then the other JVM does not require a TOAST agent or script.
+# AS/JVM then the other JVM does not require a Byteman agent or script.
 #
 # XTS Service tests which can operate with this scenario can be selected for
 # execution at AS boot by the XTSServiceTestRunnerBean by setting system

Modified: labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BACrashDuringOnePhaseCommit.txt
===================================================================
--- labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BACrashDuringOnePhaseCommit.txt	2009-11-06 12:03:25 UTC (rev 30054)
+++ labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BACrashDuringOnePhaseCommit.txt	2009-11-06 12:05:02 UTC (rev 30055)
@@ -37,7 +37,7 @@
 # used for either of these cases, the choice of which participant is used being
 # determined by the test program.
 #
-# The scenario is as follows (** indicates intercession by a TOAST rule):
+# The scenario is as follows (** indicates intercession by a Byteman rule):
 #
 # AS1 boots
 # AS2 boots
@@ -119,7 +119,7 @@
 #
 # This script contians rules which respond to events triggered by either the
 # XTS coordinator services or the XTS participant services. It needs to be
-# passed to a TOAST agent in the JVM running these services both at first boot
+# passed to a Byteman agent in the JVM running these services both at first boot
 # and at reboot. Output will be written to file testlog in the working directory
 # of the coordinator/participant AS. If two separate ASes are employed for the
 # coordinator and participant then they need to employ different working

Modified: labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BASubordinateCrashDuringComplete.txt
===================================================================
--- labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BASubordinateCrashDuringComplete.txt	2009-11-06 12:03:25 UTC (rev 30054)
+++ labs/jbosstm/trunk/XTS/sar/tests/dd/scripts/BASubordinateCrashDuringComplete.txt	2009-11-06 12:05:02 UTC (rev 30055)
@@ -91,71 +91,56 @@
 # ** Rule system traces create
 # Recovery system recreates participant engine for P1
 # ** Rule system traces create
-# Recovery system recreates participant engine for PP1
-# ** Rule system traces create
 # Recovery system recreates participant engine for P2
 # ** Rule system traces create
 # Recovery system recreates participant engine for P3
 # ** Rule system traces create
-# Recovery system recreates coordinator engine for P1
-# ** Rule system traces create
-# Recovery system recreates coordinator engine for PP1
-# ** Rule system traces create
 # Recovery system recreates coordinator engine for P2
 # ** Rule system traces create
 # Recovery system recreates coordinator engine for P3
 # ** Rule system traces create
-# Recovery system calls replay of COMPLETED transaction
-# ** Rule system traces COMPLETED replay invocation
 #
-# Coordinator sends close to P1
-# ** Rule system traces dispatch of close
-# P1 replies with closed
-# ** Rule system traces dispatch of closed
+# (parallel optional)
+# getStatus sent for P2/P3 and ignored during recovery
+# ** Rule system traces dispatch of getStatus
+# (parallel)
+# Recovery system detects missing proxy P2 for transaction T2
+# Recovery system calls cancel for subordinate coordinator
+# ** Rule system traces call to cancel
 #
-# Coordinator sends close to PP
-# ** Rule system traces dispatch of close
+# Coordinator sends compensate to P2
+# ** Rule system traces dispatch of compensate
+# P2 replies with compensated
+# ** Rule system traces dispatch of compensated
+# ** Rule system detects removal of P2
 #
-# (optional depending upon recovery timing)
-# PP throws System Exception because subordinate coordinator is not avaiable
-# ** Rule system traces call to close
-# Coordinator resends close to PP
-# ** Rule system traces dispatch of close
-# (end optional section -- n.b. may be repeated)
+# Coordinator sends compensate to P3
+# ** Rule system traces dispatch of compensate
+# P3 replies with compensated
+# ** Rule system traces dispatch of compensated
+# ** Rule system detects removal of P3
+# Subordinate coordinator cancel call returns
+# ** Rule system traces return from cancel
 #
-# PP calls subordinate coordinator close
-# ** Rule system traces call to close
+# Recovery system removes transaction T2
+# ** Rule system traces removal of transaction
+# (parallel)
+# getStatus sent for P1
+# ** Rule system traces dispatch of getStatus
+# soap fault sent to P1
+# ** Rule system traces dispatch of soap fault
+# ** Rule system detects removal of P1
+# (end parallel)
 #
-# Subordinate coordinator sends close to P2
-# ** Rule system traces dispatch of close
-# P2 replies with closed
-# ** Rule system traces receipt of closed
+# ** Rule system detects 3 participant deletes and 1 tx delete and kills JVM
 #
-# Subordinate oordinator sends close to P3
-# ** Rule system traces dispatch of close
-# P3 replies with closed
-# ** Rule system traces receipt of closed
-#
-# Subordinate coordinator deletes T2 from log
-# ** Rule system traces delete of T2
-#
-# return from subordinate coordinator close
-# ** Rule system traces return from close
-#
-# PP1 replies with closed
-# ** Rule system traces receipt of closed
-#
-# Coordinator deletes T1 from log and completes close
-# ** Rule system traces delete of T1
-# ** Rule system detects 2nd completed close and kills JVM
-#
 # Use of this script
 #
 # The default way of exercising this test is to deploy the xtstest war
 # to a single AS and configure it to run the relevant XTS Service Test.
 # The web services and coordinator will be located with the client.
-# The number of participants and subordinate participants can actually be
-# 2, 3 or more. The  web service(s), client (i.e. the XTS Service Test which
+# The number of participants and subordinate participants must be
+# exactly 3. The  web service(s), client (i.e. the XTS Service Test which
 # drives the test) and coordinator and subordinate coordinator service must
 # be colocated for this scritp to work (it is possible to distribute all of
 # these agents if desired but that woud lrequire more complex script rules).
@@ -267,25 +252,17 @@
 #   created recovered CC coordinator engine XXXXXX
 #   reinstated prepared subordinate transaction XXXXXX
 #
-#   (optional depending upon timing)
+#   (parallel -- optional and may be repeated depending upon timing)
 #   getstatus sent for CC participant P1/P2/P3
 #   getstatus received for CC participant P1/P2/P3
 #   status(COMPLETED) sent for CC participant P2/P3
 #   status(COMPLETED) received for CC participant P3
-#   (end optional -- n.b. may be repeated depending upon timing)
-#
-#   (order trace may be interleaved with next block)
+#   (parallel)
 #   getstatus sent for CC/PC participant P1
 #   getstatus received for CC/PC participant P1
 #   soap fault sent for CC/PC participant P1
 #   soap fault received for CC/PC participant P1
-#   (end order)
-#
-#   (order trace may be interleaved with previous block)
-#   getstatus sent for CC participant PP
-#   getstatus received for CC participant PP
-#   fail sent for CC participant PP
-#   fail received for CC participant PP
+#   (parallel)
 #   compensate called for pseudo participant XXXXXX
 #   cancel called for subordinate transaction XXX
 #   compensate sent for PC/CC participant XXXXXX
@@ -299,7 +276,7 @@
 #   cancel returned for subordinate transaction XXX
 #   compensate completed for pseudo participant XXXXXX
 #   removed transaction XXXXXX
-#   (end order)
+#   (end parallel)
 #
 #   JVM exit
 #