JVM Options for Application Servers

If the application server is setup for RIP mode, the JVM options for the application server's own JVM must also be verified. Finding the command line information that created the JVM varies among the application servers.

Related Topics
JVM Options
JVM Options for ENOVIA Live Collaboration Servers
JVM Options for ENOVIA Live Collaboration Servers on Windows

The following table contains a list of default file names and command lines that start the application server JVM:

Application Server Default files to find JVM options

WebSphere (all versions)

 INSTALL-DIR\AppServer\config\cells\HOST\nodes\HOST\servers\server1\server.xml

These can be set via the WebSphere Administrative Console. Refer to WebSphere JVM Options.

WebLogic version 7.x

 INSTALL-DIR/user_projects/yourDomain/startWeblogic.sh

Tomcat 4.1x

 INSTALL-DIR/bin/Catalina.sh

Sun Java System Application Server version 7.x

 INSTALL-DIR/domains/yourDomain/yourServer/config/server.xml

With the exception of the Sun Java System Application Server and WebSphere servers, all other files are startup scripts or batch files. For all servers (except for Sun Java System Application Server) edit the startup file and locate the Java command line.

Following is an example from the tomcat.sh file:

$JAVACMD $TOMCAT_OPTS -Djava.security.manager 
-Djava.security.policy==${TOMCAT_HOME}/conf/tomcat.policy 
-Dtomcat.home=${TOMCAT_HOME}  org.apache.tomcat.startup.Tomcat
"$@" &

Note: The TOMCAT_OPTS environment variable can be used to pass in JVM options. It is necessary to check both the command line itself and the TOMCAT_OPTS environment variable to verify the JVM options in use.

Below is an example from the WebLogic 7 default startWeblogic.bat file:

%JAVA_HOME%\bin\java %JAVA_VM% %JAVA_OPTIONS% %DB_JVMARGS%
-Xmx256m -classpath %WLISERVERCP% 
-Dweblogic.servlet.ClasspathServlet.disableStrictCheck=true 
-Dwli.bpm.server.evaluator.supportsNull=false 
-Dweblogic.management.username= -Dweblogic.management.password= 
-Dweblogic.Name=codonnell -Dweblogic.RootDirectory=%WLI_DOMAIN_HOME% 
-Djava.security.policy=%WL_HOME%\lib\weblogic.policy 
-Dweblogic.management.discover=false 
-Dweblogic.ProductionModeEnabled=%STARTMODE%  weblogic.Server

Note: The JAVA_VM variable allows JVM options to be specified from the environment. Additionally, WebLogic sets a default heap size of 256M (the -Xmx256m in the command line). Because it is in the command line after the JAVA_VM environment variable, it will probably override any value set by JAVA_VM.

If you are using the Sun Java System Application Server, the administrative console must be used, as shown below. Using the console, you can add, delete, or modify JVM options for each configured server.

Check all options in the "JVM Settings for Application Server" table in Server Startup Configuration Checker. If any of the options do not exist or are wrong, you can change them using the JVM Settings panel shown above.

For all Application Servers or ENOVIA Live Collaboration Servers using the Sun JVM

Note that IBM JVMs are derived from Sun's JVM, so the following tip may also work for those JVMs. Below is a quick way to check the parameters used to load the JVM:

SET _JAVA_LAUNCHER_DEBUG=1

On Unix, enter the following before running the server:

export _JAVA_LAUNCHER_DEBUG

The JVM sends each option it parses to stdout, usually the console of the window running the JVM. This will show the complete list of options passed to the JVM and directly allow verification of the options. Remember to switch this off after verifying the values, even though it is only a startup diagnostic and will not affect server operation other than having the server load a little slower.

WebSphere JVM Options

JVM options in WebSphere can be found using the WebSphere Administrative Console, as shown below.

To see the JVM settings panel shown above, select Nodes > YOUR DOMAIN > Application Servers > YOUR SERVER NAME > Process Definition > JVM Settings.

Verify that the Initial Heap Size field does not have a value less than the minimum value for the -Xms parameter listed in the "JVM Settings for Application Server" table in Server Startup Configuration Checker.

Then verify the Maximum Heap Size value, which corresponds to the -Xmx option. The Generic Command Line Arguments field should contain all other options found in the table in the Server Startup Configuration Checker topic. For example, for a maximum heap size of 256M running in RIP mode, the generic command line arguments might contain:

<jvmEntries xmi:id='JavaVirtualMachine_1' verboseModeClass='false' verboseModeGarbageCollection='false' verboseModeJNI='false' initialHeapSize='0' 
maximumHeapSize='256' runHProf='false' hprofArguments='' debugMode='false' 
debugArgs='-Djava.compiler=NONE -Xdebug -Xnoagent 
-Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=7777' genericJvmArguments=''>
        <classpath></classpath>
        <bootClasspath></bootClasspath>
      </jvmEntries>

For more information, refer to http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp.