Communicator e3000 MPE/iX Release 6.5 Express 2 (Software Release C.65.02) (30216-90322)

Chapter 3 41
Technical Articles
Java Servlets for MPE/iX
or
shell/iX>cd /APACHE/PUB/logs
shell/iX>tail error_log
shell/iX>tail mod_jserv.log
shell/iX>tail jserv.log
Once the servlet engine is running, you can view servlet status by calling the servlet status
handler (the trailing slash is required),
http://your.host.com/jserv/
To run the example servlets,
http://your.host.com/servlets/Hello
http://your.host.com/servlets/IsItWorking
To access the Jserv documentation,
http://your.host.com/jservdocs
Shutdown
To stop WebWise Secure Web Server and the servlet engine,
:xeq sh.hpbin.sys "-c 'kill `cat /APACHE/SECURE/logs/httpd.pid`'"
:stream jsrvsoff.secure.apache
To stop standard Apache,
:xeq sh.hpbin.sys "-c 'kill `cat /APACHE/PUB/logs/httpd.pid`'"
:stream jsrvoff.pub.apache
Log Files
mod_jserv.log
Mod_jserv.log records messages and errors encountered by Apache's mod_jserv module.
This includes messages about communicating via AJP to JServ, the servlet engine. When
this log file is disabled, its messages are redirected to Apache's error_log. The number of
messages logged to this file can be adjusted by setting the log level. Directives for
disabling or changing the log file (ApJServLogFile) and for setting the logging level
(ApJServLogLevel) are found in conf/jserv.conf file. Mod_jserv.log is created at Apache
startup time, if it doesn't already exist, similar to Apache's other configuration files.
jserv.log
Jserv.log records messages and errors encountered by the servlet engine. Directives to
control this log file are found in the jserv.properties file. Jserv.log can be configured to also
log servlet exceptions and various internal debugging information. Due to the large
number of objects created and managed for logging, logging to jserv.log can cause
performance degradation. This effect of logging should be considered when deciding if or
how much to log.