This log can be used to help diagnose both the cause of servlet failures
and failures of the servlet service. This log will record any exceptions
thrown by WebSphere in trying to load or configure servlets; so, it is a
good place to start diagnosing these sorts of problems. It will also contain
information relevant to determining the causes of servlet service start
The servlet service event log allows you to see when servlets are loaded,
when they are called, and with what parameters they are called. This is
useful in trying to diagnose why a particular servlet is failing under certain
conditions but not others since it shows you how it is being called. You
may want to add some debug writes to your servlet that include a
timestamp so that you can match the debug output that your servlet is
producing in standard output or standard error to the messages in the
event log that already have a timestamp.
The WebSphere engine tracing log shows detailed information about the
activity on the server. This log is stored in the directory that you specified
when activating the tracing function from the WebSphere administration.
Each action that the server takes is recorded. The format of this log is:
This log is good for diagnosing CLASSPATH problems since it provides
detailed information on which directories and JAR files have been found
and verified in the classpath.
4.4.2 DB2 diagnostic log file
DB2 keeps a diagnostics log file, called db2diag.log. This file is located in the
instance home directory under subdirectory sqllib/db2dump directory. In our
scenario, on our backend server bdtest3, it would be located in
/home/db2inst1/sqllib/db2dump. This file is appended to, or created and
appended to if it does not already exist, with diagnostic information.
The amount of diagnostic information is determined by the DIAGLEVEL
parameter found in the DB2 database manager configuration. Log in as the
DB2 instance owner and access the database manager configuration using
db2 get dbm cfg
Figure 103 on page 137 shows the result of running this command on our
backend server, bdtest3, while logged in as the DB2 instance owner,
db2inst1. The DIAGLEVEL information line has been highlighted in bold.
Linux Web Hosting with WebSphere, DB2, and Domino