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

Java runtime arguments that you must consider during the deployment of your Hibernate applications
are:
•
“-Xmx” (page 180)
•
“-Xss” (page 180)
•
“-Xnoclassgc” (page 180)
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.
Hibernate Framework Configurations for NonStop Systems
This section discusses the NonStop specific Hibernate configurations for the following:
•
“JDBC Driver for SQL/MX Database” (page 181)
•
“Database Transaction Management” (page 188)
•
“Connection Pooling” (page 189)
All the configurations for JDBC, Transaction Management, and Connection Pooling are configured
in either the hibernate.properties or the hibernate.cfg.xml file.
180 Configuring Hibernate Applications on NonStop Systems