Configuring Required Jboss Jvm Options - Adobe LIVE CYCLE 7.2 - INSTALLING AND CONFIGURING LIVECYCLE FOR JBOSS Manual

Adobe LiveCycle
Installing and Configuring LiveCycle for JBoss

Configuring required JBoss JVM options

You must configure the Java virtual machine (JVM) to support BAM Server.
➤
To configure the JBoss JVM options:
1. Navigate to the [jboss bam root]/bin directory and open the startup script in a text editor:
(Windows)
●
(Linux)
●
2. Change the
to improve the performance:
(Windows) set JAVA_OPTS=%JAVA_OPTS% -server -Xms128m -Xmx768m
●
(Linux) JAVA_OPTS="$JAVA_OPTS -server -Xms128m -Xmx768m"
●
For large data loads, consider increasing the maximum memory to -
3. Add a
JBoss bug 877974:
Windows:
●
Linux:
●
4. Add a
(Windows) set JAVA_OPTS=%JAVA_OPTS% -Dfile.encoding=utf8
●
(Linux) JAVA_OPTS="$JAVA_OPTS -Dfile.encoding=utf8"
●
5. Add a JAVA_OPTS setting to
(Windows) set JAVA_OPTS=%JAVA_OPTS% -XX:ThreadStackSize=300
●
(Linux) JAVA_OPTS="$JAVA_OPTS -XX:ThreadStackSize=300"
●
6. Add a JAVA_OPTS setting to
Windows:
●
Linux:
●
run.bat
run.sh
memory settings to 128M minimum and 768M maximum, and include -server
JAVA_OPTS
setting to disable the duplicate logging of system output. This is a workaround to
JAVA_OPTS
set JAVA_OPTS=%JAVA_OPTS
-Dorg.jboss.logging.Log4jService.catchSystemOut=false
-Dorg.jboss.logging.Log4jService.catchSystemErr=false
JAVA_OPTS="$JAVA_OPTS
-Dorg.jboss.logging.Log4jService.catchSystemOut=false
-Dorg.jboss.logging.Log4jService.catchSystemErr=false"
setting to enable UTF-8 character support:
JAVA_OPTS
increase the thread stack size to 300:
set the JVM argument for workflow scheduler:
set JAVA_OPTS=%JAVA_OPTS
-Dadobe.workflow.scheduler.java.naming.provider.url=
jnp://[host name]:[port]
JAVA_OPTS="$JAVA_OPTS
-Dadobe.workflow.scheduler.java.naming.provider.url=
jnp://[host name]:[port]
Manually Configuring JBoss for BAM Server
Configuring required JBoss JVM options
(1.5 GB).
Xmax1536m
82