[jboss-cvs] JBossAS SVN: r95187 - trunk/testsuite/imports.

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

Author: bstansberry at jboss.com
Date: 2009-10-20 11:46:33 -0400 (Tue, 20 Oct 2009)
New Revision: 95187

Modified:
   trunk/testsuite/imports/server-config.xml
Log:
[JBAS-7248] Add simple hook to add JBoss Profiler via command line

Modified: trunk/testsuite/imports/server-config.xml
===================================================================
--- trunk/testsuite/imports/server-config.xml	2009-10-20 15:42:08 UTC (rev 95186)
+++ trunk/testsuite/imports/server-config.xml	2009-10-20 15:46:33 UTC (rev 95187)
@@ -30,6 +30,17 @@
    -->
    <property name="jpda.cmdline" value="" />
 
+   <!-- Override with the settings for running JBoss Profiler. A minimal
+        example would be:
+        
+   -agentlib:jbossAgent
+   
+        For a 64 bit JVM this might be:
+        
+   -agentlib:jbossAgent -d64
+   -->        
+   <property name="jboss.profiler.cmdline" value="" />
+
    <path id="jboss.client.classpath">
       <fileset dir="${jboss.dist}/client"/>
    </path>
@@ -770,12 +781,10 @@
       	<jvmarg value="-XX:MaxPermSize=256m" />
          <jvmarg value="-XX:-UseGCOverheadLimit" />
       	<jvmarg value="-XX:+HeapDumpOnOutOfMemoryError" />
-         <!-- Uncomment to use JBoss Profiler to analyze heap. The
-              -d64 argument may not be needed and definitely shouldn't
-              be used if a non-64 bit JVM is used
-         <jvmarg value="-agentlib:jbossAgent"/>
-         <jvmarg value="-d64"/>
-         -->
+         <!-- Use -D to set ${jboss.jvm.agentlib} to "-agentlib:jbossAgent" or
+              "-agentlib:jbossAgent -d64" to use JBoss Profiler to analyze heap 
+              The default value is "" turning the following into a no-op -->
+         <jvmarg value="${jboss.profiler.cmdline}"/>
          <sysproperty key="java.net.preferIPv4Stack" value="true" />
       	<sysproperty key="java.endorsed.dirs" value="${jboss.dist}/lib/endorsed" />
         <sysproperty key="jgroups.udp.ip_ttl" value="${jbosstest.udp.ip_ttl}" />
@@ -786,12 +795,10 @@
          <jvmarg value="-XX:MaxPermSize=256m" />  
          <jvmarg value="-XX:-UseGCOverheadLimit" />      
          <jvmarg value="-XX:+HeapDumpOnOutOfMemoryError" />
-         <!-- Uncomment to use JBoss Profiler to analyze heap. The
-              -d64 argument may not be needed and definitely shouldn't
-              be used if a non-64 bit JVM is used
-         <jvmarg value="-agentlib:jbossAgent"/>
-         <jvmarg value="-d64"/>
-         -->
+         <!-- Use -D to set ${jboss.jvm.agentlib} to "-agentlib:jbossAgent" or
+              "-agentlib:jbossAgent -d64" to use JBoss Profiler to analyze heap 
+              The default value is "" turning the following into a no-op -->
+         <jvmarg value="${jboss.profiler.cmdline}"/>
          <sysproperty key="java.net.preferIPv4Stack" value="true" />
          <sysproperty key="java.endorsed.dirs" value="${jboss.dist}/lib/endorsed" />
          <sysproperty key="resolve.dns" value="false" />
@@ -801,7 +808,8 @@
          <sysproperty key="jboss.partition.name" value="${partitionName}"/>
          <sysproperty key="jgroups.bind_addr" value="${node0.jgroups.bind_addr}" />
       </server>
-      <server name="cluster-classloader-leak-1" host="${node1}">
+    	<!-- Note that on this node we don't run JBoss Profiler -->
+    	<server name="cluster-classloader-leak-1" host="${node1}">
          <jvmarg value="-Xms128m" />
          <jvmarg value="-Xmx512m" />
          <jvmarg value="-XX:MaxPermSize=256m" />