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-6
Broadcast Error
Broadcast Error
A broadcast resulted in error. Some, but not all, of the server processes reported error
in their responses. As a result, those failed servers may be out of sync (in an
inconsistent state) from the rest of the servers. For example, if the broadcast is on
behalf of a deploy command, then these failed servers will not have the new
application. This causes an inconsistent service (i.e., requests served by these servers
will be returned with status 404 (resource not found). But, if the broadcast fails for a
status command, then the problem is not so severe (only the returned status does not
contain these failed servers' status). Therefore, the recovery procedures are totally
dependent on the commands that caused the broadcast failure. Listed below are some
guidelines to help you decide how to recover from a broadcast error:
1. For admin commands (commit changes):
Stop all inconsistent servers so that the entire NSJSP container maintains a
consistent service.
The admin application has a broadcast error page that reports the failed server
processes, and has a button for the operator to choose to stop the servers or to
ignore the broadcast failure.
2. For manager commands (status):
This may not constitute a real problem. Continue monitoring the servers by issuing
status commands. If the problem persists, these failed servers may have stalled
and require to be stopped.
3. For manager commands (other than status):
Stop all inconsistent servers so that the entire NSJSP container maintains a
consistent service. The manager has a broadcast error page that lists all the failed
servers and has a button for the operator to choose to stop the servers or ignore
the broadcast failure.
Broadcast Failure
This is a complete broadcast failure. All the server processes returned an error in their
response. This creates a situation where the nsjspadmin server and the configuration
files are out of sync with the currently running SERVLET ServerClass processes.
The recommended recovery procedures are:
•
Resolve any reported TS/MP or Guardian File System error.
•
Stop your iTP WebServer environment.
•
Manually roll back the changes you just committed.
•
Rollback the iTP_server.xml (if needed) using the backup copy in the
$NSJSP_HOME/conf/backup/ directory.