iTP Secure WebServer System Administrator's Guide (iTPWebSvr 6.0+)

Using NonStop Servlets for JavaServer Pages
(NSJSP)
iTP Secure WebServer System Administrator’s Guide—523346-002
9-42
Error Messages
Event #7013 Servlet Server Class Object code call to %FUNC%
failed. Terminating Server
where %FUNC% is the native function that caused the failure. Currently it is either
processhandle_getmine_() or getProcessInfo(). You must restart the
NSJSP process.
Error Messages
The following logs are available for tracking error conditions:
/usr/tandem/webserver/logs/servlet.log
This is the servlet output file (STDOUT of the NSJSP Process).
/usr/tandem/webserver/logs/servlet_error.log
This is the servlet error output file (STDERR of the NSJSP Process).
/usr/tandem/webserver/servlet_jsp/logs/tomcat.log
This is the internal tomcat or NSJSP engine log.
/usr/tandem/webserver/servlet_jsp/logs/jasper.log
This is the NSJSP log file.
/usr/tandem/webserver/servlet_jsp/logs/servlet.log
This is the servlet log file.
Note that /usr/tandem/webserver/ is the default location for iTP Secure
WebServer installation. The rest of the path is also configurable. The
iTP_server.xml file sets the location of the files that contain logs of low-level
events. This part of the configuration file is reproduced below:
<!-- Debug low-level events in XmlMapper startup -->
<xmlmapper:debug level="0" />
<!-- This is quite flexible; we can either have a log file per
module in Tomcat (example: ContextManager) or we can have
one for Servlets and one for Jasper, or we can just have
one tomcat.log for both Servlet and Jasper.
If you omit "path" there, then stderr should be used.
verbosityLevel values can be:
FATAL
ERROR
WARNING
INFORMATION
DEBUG
-->
<Logger name="tc_log"
path="logs/tomcat.log"
customOutput="yes" />