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

Installing NSJSP
NonStop Servlets for JavaServer Pages (NSJSP) System Administrator’s Guide—525644-002
2-7
Stopping NSJSP
Stopping NSJSP
You can stop NSJSP in two ways by using the stop script, as described in the iTP
Secure WebServer System Administrator’s Guide, or by using the nsjsp_stop script,
described as follows.
The 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.
To save persistent session data and allow your applications to shut down gracefully,
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.
Note. This script is slower than the 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,
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 must
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 when an nsjsp_stop script
has been issued against the web container.