7.18 Checking the troubleshooting information

This section describes the troubleshooting information to be used for errors when Cosminexus JMS Provider is used.

With Cosminexus JMS Provider, the following three components output the log:

These components output the message log and exception log. The message log and exception log are output to the log files for each component.

The log format is the Hitachi Trace Common Library format.

Message log
The statuses occurring due to the operations executed from J2EE applications are output to the message log.
The output message type is set based on the log level.
The following table describes the meaning of the log levels in Cosminexus JMS Provider.

Table 7-14 Meaning of the log levels in Cosminexus JMS Provider

Log levelMeaning
ERRORA message log level that indicates the occurrence of a serious problem leading to a system error.
This log level outputs minimum information, containing only the error and exception information.
If this log level is specified, only the ERROR level messages are output to the log.
WARNINGA message log level that indicates a status in which precautions need to be taken, but not leading to a system error.
This log level is output when the processing terminates normally and there is a problem in the status.
If this log level is specified, the ERROR level and WARNING level messages are output to the log.
INFOThis log level outputs the metrics and other messages.
This log level outputs information that indicates the flow of processing and the type of operations performed during normal processing.
If this log level is specified, the ERROR level, WARNING level, and INFO level messages are output to the log.
Note
The important messages are output to the console or the log file regardless of the log level settings.

Exception log
The information about the occurrence of errors or exceptions (exception messages) during the execution of J2EE applications is output to the exception log.

For details on the messages output to the log files, see 4. KDAN (Messages Output by Cosminexus JMS Provider) in the manual uCosminexus Application Server Messages. Also, for details on the Hitachi Trace Common Library format, see 5.2.1 Log output format and output items in the Hitachi Trace Common Library format in the uCosminexus Application Server Maintenance and Migration Guide.

Reference note
  • With Cosminexus JMS Provider, you can also obtain the PRF trace. For the PRF trace collection points when Cosminexus JMS Provider is used, see 8. Trace Collection Points and PRF Trace Collection Levels of the Trace Based Performance Analysis in the uCosminexus Application Server Maintenance and Migration Guide.
  • If CJMSP Broker stops with a JavaVM error, the thread dump or core file is output to the following directory:
    In Windows
    Cosminexus-installation-directory\CC\cjmsp\var\instances
    In UNIX
    /opt/Cosminexus/CC/cjmsp/var/instances