Difference between revisions of "Watching Application Server Logs"
From AgileApps Support Wiki
imported>Aeric m (moved Watching LongJump Logs to Watching Application Server Logs) |
imported>Aeric |
||
| Line 1: | Line 1: | ||
=== Watching Application Server Logs === | <includeonly>=== Watching Application Server Logs ===</includeonly> | ||
The log files used by the platform are <tt>tomcat/logs/relationals.log</tt> and <tt>tomcat/logs/catalina.out</tt> | The log files used by the platform are <tt>tomcat/logs/relationals.log</tt> and <tt>tomcat/logs/catalina.out</tt> | ||
Revision as of 21:32, 2 October 2013
The log files used by the platform are tomcat/logs/relationals.log and tomcat/logs/catalina.out
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 catalina.out 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.