User Manual

important Java runtime arguments that you must consider during the deployment of your Axis2/Java
applications are:
• -Xmx
• -Xss
• -Xnoclassgc
There are other Java runtime arguments supported by NSJSP. For more information, see the NonStop
Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator's Guide.
-Xmx
Sets the maximum size of the memory allocation pool, which is the garbage collected heap.
Syntax:
-Xmx maximum-heap-size [ k | m ]
where,
maximum-heap-size
is the maximum size of the memory allocated for the garbage collected. It must be greater than or
equal to 1000 bytes.
k
sets the value of maximum-heap-size to be read in kilobytes.
m
sets the value of maximum-heap-size to be read in megabytes.
-Xss
Sets the maximum stack size that can be used by a Java thread.
Syntax:
-Xmx maximum-stack-size
where,
maximum-stack-size
is the maximum size of the stack trace in kilobytes.
-Xnoclassgc
Is an optional argument to stop the Java class garbage collection.
Syntax:
-Xnoclassgc
By default, the Java runtime reclaims space for unused Java classes. Including this optional argument
might prevent any memory-leak problems.
Axis2/Java Framework Configurations for NonStop Systems
This section discusses the NonStop specific Axis2/Java configurations for the following:
• “Global Configuration” (page 317)
• “Service Configuration” (page 318)
• “Module Configuration” (page 318)
Global Configuration
Global configurations are used to configure the whole system, wherein the axis2.xml file provided
with the Axis2/Java distribution is configured.
Axis2/Java Framework Configurations for NonStop Systems 317