WebSphere Message Brokers
File: au16700_
Writer: Jane Brockbank

Reference topic

This build: July 31, 2007 21:39:48

WebSphere Message Broker logs

This section describes the logs that are specific to WebSphere Message Broker:

Eclipse error log

The Eclipse error log captures internal errors from Eclipse or your code. This is useful at run time, in case you cause exceptions during development. As errors are triggered, they are added to the Error Log view of the Plug-in Development perspective, and you can examine details by double-clicking them. You can also clear the view when you have fixed all the errors, although you cannot clear individual errors. Entries are sorted in reverse chronological order; that is, most recent first. You can open the Properties view to see entry details.

Some errors might be hierarchical; that is, there might be a general entry for a complex problem and a number of child entries listing the individual problems in detail.

The same information that is shown in the Error Log view is stored in the .log file in the C:\Documents and Settings\user\IBM\wmbt6.0\workspace\.metadata directory.

The Eclipse error log shows errors that are generated by the person using that particular workbench.

The broker domain Event Log

Broker domain log information is written to the broker domain Event Log. This log is stored and managed by the Configuration Manager. The Event Log displays messages about events that occur within the broker domain, such as deploying topology or topics hierarchy configuration. The messages can be information, errors, or warnings. You view the messages in the editor area of the Broker Administration perspective.

The broker domain Event Log shows errors that are generated by all workbench users in that particular domain.

The Problems or Alerts view

Either the Problems or the Alerts view is displayed, depending on the perspective being used at the time.
  • In the Broker Application Development perspective, the Problems view shows information messages, warnings and errors for message flow applications (such as message flows, message sets, ESQL, Java, and mapping).
  • In the Broker Administration perspective, the Alerts view shows information about stopped resources (such as message flows, execution groups, and brokers).

TDS log

When you use the Tagged/Delimited String (TDS) physical format messages, you must conform to a number of rules that apply to the setting of values of properties. These rules are checked at deploy time, and, if an inconsistency is found, error message BIP1836 is displayed in the workbench. Details of the error are written to the TDS.log file in the install_dir/log directory.

For more information about the rules for TDS physical format properties, see TDS message model integrity.

Related concepts
Logs
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:39:48

au16700_ This topic's URL is: