Show TOC

Monitoring Java Error MessagesLocate this document in the navigation structure

Use

Use the Java Critical Messages monitor to obtain information about the most important error messages of your monitored Java systems. You can see alerts in the Java log files that you particularly need to monitor in your daily administration at a glance in the subtrees of this monitor (see also Logging Quick Guide).

Execution

Check the Java Critical Messages monitor for alerts. To open the monitor, proceed as described in Tasks.

Affected MTE

Meaning

<SysID>

The monitored log files are initially grouped by the system ID of the monitored Java systems. All systems that belong to the J2EE_Systems system group are displayed.

<context name>

The log files are grouped by different contexts (such as dispatcher, server, startup framework) within a system.

<monitored log file>

A monitoring object with the name of the file is displayed for each monitored log file. The most important files are monitored in this monitor.

The following developer traces are written in a separate directory by the startup framework; if, for example, the J2EE Engine does not start or crashes due to Virtual Machine errors, you can find relevant information at the end of these files,

  • dev_dispatcher*

  • dev_server*

  • dev_jcontrol*

    The following files are written by the J2EE Engine to the directory ./log:

  • database*.log: Messages related to the database

  • security*.log: Messages about security

  • network*.log: Messages about network connections and traffic

  • server*.log: Messages about problems that are not covered by the above categories, such as EJB, Web Container, Deploy service, and so on.

Complete Name Monitored Patterns Lines Found for Pattern Data Collection Check

Information about the relevant log file, the monitored search pattern, and the lines that contain the search pattern with alert values (see also Logfile Monitoring Monitor)