If the JBoss run.bat or run.sh settings you currently have for LiveCycle ES2 is giving you problems, try the following settings. It is assumed that you are running 64-bit Windows, with a 64-bit Sun HotSpot JDK and the laptop/desktop/server has at least 4 GB of RAM: rem -----------------------------------------
rem Config for Adobe LiveCycle ES2
rem ---------------------------------------- rem Make 1.5 GB of RAM available to JBoss - big (+10 MB) docs might require higher values
set JAVA_OPTS=%JAVA_OPTS% -XX:PermSize=384m -XX:MaxPermSize=384m -Xms1536m -Xmx1536m rem Run in server mode
set JAVA_OPTS=%JAVA_OPTS% -server rem Set unique domain name for JBoss so that it does not automatically cluster
rem with other JBoss instances in your neighborhood. However this alone is not enough
rem to prevent this behavior
set JAVA_OPTS=%JAVA_OPTS% -Djboss.partition.name=partitionLIVECYCLE rem Control where the JBoss JVM puts its temporary junk
set JAVA_OPTS=%JAVA_OPTS% -Djava.io.tmpdir=C:\Programs\jboss_es2\server\lc_mysql\java_io_tmpdir rem Run the Parallel Garbage Collector for better performance
rem If you have 4 CPU cores, set ParallelGCThreads to 4
set JAVA_OPTS=%JAVA_OPTS% -XX:+UseParallelOldGC -XX:ParallelGCThreads=2 rem ----------------------------------------------------------------------
rem Enable Remote JMX Monitoring
rem security risk - not for production use
rem -----------------------------------------------------------------------
set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.port=50050
set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.authenticate=false
set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.ssl=false
| 
No comments:
Post a Comment