[jboss-cvs] JBossAS SVN: r105540 - projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US.

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

Author: misty at redhat.com
Date: 2010-06-01 23:41:35 -0400 (Tue, 01 Jun 2010)
New Revision: 105540

Modified:
   projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml
Log:
JBPAPP-4387

Modified: projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml
===================================================================
--- projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml	2010-06-02 03:40:24 UTC (rev 105539)
+++ projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Getting_Started_With_JBoss_Tools.xml	2010-06-02 03:41:35 UTC (rev 105540)
@@ -204,14 +204,14 @@
 			JBoss includes sophisticated support for hot redeployment of WARs and EARs. Unfortunately, due to bugs in JVM, repeat redeployment (common during development) uses all of the JVM's perm gen space. Therefore, we recommend running JBoss in a JVM with a large perm gen space during development. If you are running JBoss from JBoss IDE, you can configure this in the server launch configuration, under "VM arguments". We suggest the following values:
 		</para>
 		 
-<programlisting> -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512
-</programlisting>
+<screen> -Xms512m -Xmx1024m -XX:PermSize=256m -XX:MaxPermSize=512
+</screen>
 		 <para>
 			If your available memory is limited, the following is our minimum recommendation:
 		</para>
 		 
-<programlisting> -Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256
-</programlisting>
+<screen> -Xms256m -Xmx512m -XX:PermSize=128m -XX:MaxPermSize=256
+</screen>
 		 <para>
 			Right-click on the server in the <emphasis>JBoss Server View</emphasis> and select <guimenu>Edit Launch Configuration</guimenu>:
 		</para>