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

Java runtime arguments that you must consider during the deployment of your MyFaces application
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
This 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.
Determining the Maximum Capacity of NSJSP Instance
To determine the maximum load for a single instance of NSJSP, it is important to configure the
relevant TS/MP and server parameters of NSJSP (of the single instance) to their maximum limit in
the following way:
1. Set the value of Numstatic to 1. This limits the number of static instances of NSJSP to 1.
2. Set the value of Maxservers to 1. This limits the number of NSJSP instances that can be
started to 1. This implies that TS/MP cannot start more than one instance of NSJSP.
3. Set the value of Maxlinks to 250. This is the maximum number of links to the server process
(NSJSP process). This means that the server process must be capable of processing 250
requests simultaneously.
250 Configuring MyFaces Applications on NonStop Systems