HP Integrity NonStop J-Series - Manual (Page 62)

Some of the important Java runtime arguments that you must consider during the deployment of
your Spring applications are:
•
“-Xmx” (page 62)
•
“-Xss” (page 62)
•
“-Xnoclassgc” (page 62)
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
may prevent any memory-leak problems.
Spring Framework Configurations
This section discusses the following configurations for your Spring applications:
•
“Configuring JDBC Driver for SQL/MX Database” (page 63)
•
“Configuring Database Transaction Management” (page 66)
•
“Connection Pooling” (page 72)
JDBC configurations are carried out in applicationContext.xml and jdbc.properties
files. All the configurations for Transaction Management and Connection Pooling are configured
in applicationContext.xml.
62 Configuring Spring Applications on NonStop Systems