Difference between revisions of "Watching Application Server Logs"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| (One intermediate revision by the same user not shown) | |||
| Line 1: | Line 1: | ||
<includeonly>=== Watching Application Server Logs ===</includeonly> | <includeonly>=== Watching Application Server Logs ===</includeonly> | ||
The log files used by the platform are <tt> | The log files used by the platform are as follows: | ||
:*<tt>{install-dir}/profiles/IS_default/logs/relationals.log</tt> | |||
:*<tt>{install-dir}/profiles/IS_default/logs/sag-osgi.log</tt> | |||
:*<tt>{install-dir}/profiles/IS_default/logs/wrapper.log</tt> | |||
:*<tt>{install-dir}/profiles/IS_default/logs/platform.log</tt> | |||
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.) | 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.) | ||
| Line 6: | Line 10: | ||
;Examples: | ;Examples: | ||
:* A report scheduled to run at 2:00 is not created until much later. Examining the <tt>relationals.log</tt> for entries timestamped around that time can help to diagnose the problem. (The same applies to other scheduled events.) | :* A report scheduled to run at 2:00 is not created until much later. Examining the <tt>relationals.log</tt> 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 <tt> | :* A java.lang.OutOfMemoryError exception in <tt>sag-osgi.log</tt> or <tt>wrapper.log</tt> 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. | ''Note:'' In general, the [[Heartbeat Check]] is the best way to monitor the availability of the application server. | ||
[[Category: | [[Category:Installable Version]] | ||
Latest revision as of 12:00, 17 October 2019
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.