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

Logs and Error Conditions
NonStop Servlets for JavaServer Pages (NSJSP) System Administrator’s Guide—525644-002
6-7
Causes of Broadcast Error/Failure
•
Additionally, you will need to rollback any Context configuration files
(<context>.xml) that have been modified. You can use the backup copies
from the $NSJSP_HOME/conf/NSJSP/<host-name>/backup/ directory.
•
Restart your iTP WebServer environment.
Causes of Broadcast Error/Failure
A broadcast error could be the result of the following:
1. TS/MP or Guardian File System error:
If a CPU has just failed, the Path Down file system error will likely be received by
the nsjspadmin server. In such a case, no recovery is necessary since the server
process is no longer running. Refer to TS/MP Manual or Guardian System Error
Manual for any other reported errors and their recommended recovery procedures.
2. A temporary stall on the server process. This would cause the broadcast operation
to timeout with Guardian File System error 40.The nsjspadmin server has a default
timeout of 20 seconds for each message sent as part of a broadcast operation. For
example, if an application is running a CPU-bound operation such as prime
number search, the server process is pre-occupied and may not be able to handle
the broadcast message in time. The other potential cause of timeout is a blocking
SQL operation (such as all of the SQL/MP queries). Therefore, the timeout may not
constitute a real problem. The timer is configurable using an environment variable
named TANDEM_BROADCAST_SEND_TIMEOUT in the nsjspadmin server
configuration file (iTPWS_INSTALL_DIR/conf/nsjspadmin.config)
Env TANDEM_BROADCAST_SEND_TIMEOUT=<timeout-in-milliseconds>
Default: 20000 or 20 seconds
3. Processing exception reported by the server process. This reports that the server
is in an inconsistent state and could not handle the broadcast command. It is
recommended that you stop all such server processes.