When running tc Server as a service on Windows, JVM settings are specified in the conf/wrapper.conf file.
This table lists the various options that are commonly set in this location and the corresponding description.
Option |
Description |
set.JAVA_HOME | The location of Java to be used by Tomcat |
wrapper.java.library.X | The Java library path |
wrapper.java.classpath.X | The Java classpath |
wrapper.java.additional.X | System properties, which is -D |
wrapper.java.additional.X | JVM options, such as -Xmx, -Xms, and -Xss |
Note: Except for the set.JAVA_HOME option, other options require an incrementing number appended at the end, represented by X . You must replace X with a number. All numbers for a given property must be sequential and the numeric range should start with 1. For a sample, see the default conf/wrapper.conf file.
When running tc Server on a Linux or Unix system, the JVM settings can be modified by editing the bin/setenv.sh file. With tc Server, this file exists by default and is populated with some common settings and values.
This table lists the options that are set in the bin/setenv.sh file and the corresponding description.
Option | Description |
JAVA_HOME |
Defines the location of the installed JDK. |
AGENT_PATH | Used to configure an agent which requires custom JVM options. |
JAVA_AGENTS |
Used to configure Java agents that are required for a profiler. |
JAVA_LIBRARY_PATH |
Used to define options for the Java library path. This is set if you need to access the native code. |
JVM_OPTS | Used to specify JVM specific options, such as -Xmx or -Xms |
JAVA_OPTS |
This property aggregates the previously mentioned properties. It is not recommended to edit this property. |