Watching Application Server Logs

The log files used by the platform are as follows:

• {install-dir}/profiles/IS_default/logs/relationals.log
• {install-dir}/profiles/IS_default/logs/sag-osgi.log
• {install-dir}/profiles/IS_default/logs/wrapper.log
• {install-dir}/profiles/IS_default/logs/platform.log

They contain informational messages as well as exceptions that help to troubleshoot specific problems. All messages are timestamped, with a prefix that indicates the module that recorded the message.)

Examples

• A report scheduled to run at 2:00 is not created until much later. Examining the relationals.log for entries timestamped around that time can help to diagnose the problem. (The same applies to other scheduled events.)
• A java.lang.OutOfMemoryError exception in sag-osgi.log or wrapper.log indicates that tomcat has run out of memory.

Note: In general, the Heartbeat Check is the best way to monitor the availability of the application server.