WebSphere® Message Broker writes information to a number of product-specific logs to report the results of actions that you take.
The Eclipse error log captures internal errors from Eclipse and the code associated with your user-defined extensions. Check this log at run time for exceptions that you might have caused during development. When errors are triggered, they are added to the Error Log view of the Plug-in Development perspective, and you can double-click each one to examine details. Entries are sorted in reverse chronological order; that is, most recent first. You can open the Properties view to see entry details. You can also clear the view when you have fixed all the errors, although you cannot clear individual errors.
Some errors might be hierarchical; that is, a general entry for a complex problem might be followed by a number of child entries that list the individual problems in detail.
The same information
that is shown in the Error Log view is stored in the .log file
in the workspace directory. The default location for the workspace
directory depends on your environment:
The Eclipse error log shows errors that are generated only by the user ID that is working with that particular workbench session.
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 configurations. 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.
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.