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

delivered through file system calls from httpd, not through TS/MP. Hence, the 25 links are free
to process new web dialogs. Therefore, a single instance of NSJSP can serve all the 100 requests.
At this point, one instance of NSJSP could be processing requests from all the possible 100
connections to the httpd processes. This means that there could be a scenario where all the 100
requests time out. Therefore, there must be enough space in the $RECEIVE file to handle (100+100)
messages. That would mean TANDEM_RECEIVE_DEPTH should have a value of 200. The reason
for setting TANDEM_RECEIVE_DEPTH to a value of 200 can be explained as:
To handle 100 requests, you need 100 threads. In an extreme case of all the 100 requests timing
out, you need another 100 threads to process the new incoming 100 requests because the threads
processing the timeout requests could still be busy. Therefore, the number of threads that need to
be configured is (100+100 = 200).
Configuring Java Runtime Arguments
The configurations for Java runtime arguments can be written in the <iTP WebServer
Deployment Directory>/conf/servlet.config
file on OSS. The sscaux object is
configured under the Server directive. Java runtime arguments are populated in the Arglist.
Some of the important Java runtime arguments that you must consider during the deployment of
your applications are:
•
“-Xmx” (page 329)
•
“-Xss” (page 329)
•
“-Xnoclassgc” (page 329)
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:
-Xss 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
NonStop Platform Configurations 329