WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Standard system logs

The broker writes information, warning, and error messages to standard output (STDOUT) and standard error (STDERR). The broker records this information for the execution group and for the broker admin agent (bipbroker process).

On some operating systems, the two standard logs are written to separate files, but the system might provide an option for the data to be recorded to a single merged file. On other systems, the two targets are defined to a single, and you might have the option to separate them. Check the documentation that is provided with your operating system for more details about STDOUT and STDERR.

Brokers write records to both STDOUT and STDERR. Always check the contents of the file or files when an error occurs.

Because the records are written whenever components are active, check occasionally that the location of the file or files has sufficient space, or trim the file contents on a regular basis.

The default location of STDOUT and STDERR depends on the operating system:
Operating system Location of STDOUT and STDERR for broker admin agent Location of STDOUT and STDERR for execution group

Linux platformUNIX platformLinux and UNIX systems

/var/mqsi/components/broker_name /var/mqsi/components/broker_name/execution_group_uuid

Windows platformWindows systems

A single file, workpath\components\broker_name\console.txt, contains both STDOUT and STDERR data, generated by the admin agent, where workpath is the working directory defined for the broker. A single file, workpath\components\broker_name\execution_group_uuid\console.txt, contains both STDOUT and STDERR data, where workpath is the working directory defined for the broker.

z/OS platformz/OS® systems

The job log for the broker control address space. The job log for the execution group address spaces.

Clearing logs

If you run your integration node with errors, or if you are leaving trace on, you need to clean the logs periodically. To clear the logs, complete the following steps.
  1. Stop the source that is generating the log, such as the broker or integration server.
  2. Back up the contents of the log file.
  3. Restart the source.
You can remove files without stopping the source, but this action might generate an error if the log is being actively updated. If you remove the log file, it is regenerated by the source when the source restarts.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:36


Concept topicConcept topic | Version 8.0.0.7 | au14165_