Macromedia live cycle 7.2 Manual

Installing and Configuring LiveCycle for JBoss

 Configuring required JBoss JVM options     82

You must configure the Java virtual machine (JVM) to support BAM Server.

➤

1. Navigate to the [jboss bam root]/bin directory and open the startup script in a text editor:

●

(Windows) 

run.bat

●

(Linux) 

run.sh

2. Change the 

JAVA_OPTS

 memory settings to 128M minimum and 768M maximum, and include -server 

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 -

Xmax1536m

 (1.5 GB).

3. Add a 

JAVA_OPTS

 setting to disable the duplicate logging of system output. This is a workaround to 

JBoss bug 877974:

●

Windows:

set JAVA_OPTS=%JAVA_OPTS
-Dorg.jboss.logging.Log4jService.catchSystemOut=false
-Dorg.jboss.logging.Log4jService.catchSystemErr=false

●

Linux:

JAVA_OPTS="$JAVA_OPTS
-Dorg.jboss.logging.Log4jService.catchSystemOut=false
-Dorg.jboss.logging.Log4jService.catchSystemErr=false"

4. Add a 

JAVA_OPTS

 setting to enable UTF-8 character support:

●

(Windows) set JAVA_OPTS=%JAVA_OPTS% -Dfile.encoding=utf8

●

(Linux) JAVA_OPTS="$JAVA_OPTS -Dfile.encoding=utf8”

5. Add a JAVA_OPTS setting to 

increase the thread stack size to 300:

●

(Windows) set JAVA_OPTS=%JAVA_OPTS% -XX:ThreadStackSize=300

●

(Linux) JAVA_OPTS="$JAVA_OPTS -XX:ThreadStackSize=300”

6. Add a JAVA_OPTS setting to 

set the JVM argument for workflow scheduler:

●

Windows:

set JAVA_OPTS=%JAVA_OPTS
-Dadobe.workflow.scheduler.java.naming.provider.url= 
jnp://[host name]:[port]

●

Linux:

JAVA_OPTS="$JAVA_OPTS
-Dadobe.workflow.scheduler.java.naming.provider.url= 
jnp://[host name]:[port]