NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator's Guide

Configuring NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) 6.1 System Administrator’s Guide—596210-006
3-28
The Installation-Specific servlet.config File
The following are the configuration parameters defined by TS/MP for server classes.
For more information on these parameters, see the NonStop TS/MP System
Management Manual. The following descriptions are applicable to NSJSP only.
NUMSTATIC and MAXSERVERS
In the default configuration, both these parameters have the same value. This
means there are no dynamic servers are configured for NSJSP. HP recommends
that you do not configure dynamic servers. This is because, the long startup time
for NSJSP processes might lead to requests getting queued, which might also
result in application timeouts. For more information on NUMSTATIC &
MAXSERVERS parameters, see the NonStop Servlets for JavaServer Pages
(NSJSP) Configuration White Paper.
Stdout and Stderr
Specifies the standard out and standard error files respectively. The JNI library of
NSJSP writes messages to these files. Although most of the messages are written
during startup, errors encountered on operations on with $RECEIVE are written to
the standard error file during run time. Based on the message type, log entries
created by NSJ are also written to either the Stdout file or the Stderr file.
MAXLINKS and LINKDEPTH
The MAXLINKS and LINKDEPTH parameters are each set to 50 by default. These
values may require tuning, depending upon the NSJSP request load and the
number of CPUs in the HP NonStop system. For improved load balancing and
better response times, smaller values for both parameters may provide better
results.For information on MAXLINKS and LINKDEPTH parameters, see the
NonStop Servlets for JavaServer Pages (NSJSP) Configuration White Paper.
Miscellaneous
The Region Directive
The Region directive is used to prevent access to the Servlets and JSPs through the
Invoker Servlet. The Invoker Servlet allows applications to dynamically
register new servlets and to invoke a servlet using the fully qualified servlet class
name. Allowing such servlet invocations might lead to security problems. For more
information on the Invoker Servlet, see http://tomcat.apache.org/tomcat-6.0-
doc/funcspecs/fs-invoker.html.