NonStop Servlets for JSP System Administrator's Guide

Installing NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) System Administrator’s Guide—525644-001
2-6
Possible Error Conditions
NSJSP can also be started with a security manager. For information on this, refer to
Starting NSJSP With a Security Manager on page 3-17.
To restart NSJSP, use the restart script or the stop/nsjsp_stop and start scripts in
sequence, as described in the iTP Secure WebServer System Administrator’s Guide,
or use the PATHCOM utility to freeze, stop, thaw, and start NSJSP. The restart
script is shown below:
OSS: cd /usr/tandem/webserver/conf
OSS: ./restart
Possible Error Conditions
The NSJSP class file (ServletJSPConnector.jar) and servlets JNI (libT1222.a)
must be the same version; otherwise, startup of the NSJSP environment fails and a
message reporting the error appears in the servlet_error.log file.
Stopping NSJSP
You can stop NSJSP in two ways: using the stop script, as described in the iTP
Secure WebServer System Administrator’s Guide, or using the nsjsp_stop script,
described as follows.
The new NSJSP script called nsjsp_stop is located in the
iTPWS_INSTALL_DIR/conf directory. This script, shown in Example 2-1, enables the
NSJSP container to be stopped gracefully by invoking the servlet/jsp destroy()
methods for cleanups and flushing the persistent session data into a pre-configured
persistent data store.
Use the nsjsp_stop script instead of the iTPWS_INSTALL_DIR/conf/stop script
(described in the iTP Secure WebServer System Administrator’s Guide) to shut down
the NSJSP and iTP WebServer environments if you wish to save the persistent
session data and allow your applications to shut down gracefully.
Note. This script will be slower than the old ITPWS_INSTALL_DIR/conf/stop script. So if
you do not use persistent sessions and do not care about gracefully allowing your applications
to exit, then using the ITPWS_INSTALL_DIR/conf/stop script might be more appropriate
for your environment.
Caution. If you use the nsjsp_stop script when servlet requests are still pending, you will need
to restart the WebServer environment. Stopping the web container immediately stops all
execution threads that are running within the web container. There are no runtime checks that
allow the web container to stay up and wait for all threads to finish executing when an
nsjsp_stop script has been issued against the web container.