See information about the latest product version
WebSphere Message Broker logs
WebSphere® Message Broker writes information to a number of product-specific logs to report the results of actions that you take.
Eclipse error log
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 .metadata directory of the workspace. The default location for the workspace directory depends on your operating system:
Linux on x86: user_home_dir/IBM/wmbt80/workspace/
Windows XP and Windows Server 2003: C:\Documents and Settings\user_ID\IBM\wmbt80\workspace\
Windows 7, Windows Vista and Windows Server 2008: C:\Users\user_ID\IBM\wmbt80\workspace\
The Eclipse error log shows errors that are generated only by the user ID that is working with that particular WebSphere Message Broker Toolkit session.
Broker Administration log or Deployment log
Broker Administration log information is written to the Administration log. This log is stored and managed by the broker. The Administration log displays messages about events that occur within the broker, such as the results of a deployment, or a change to broker properties. The messages can be information, errors, or warnings. You view the messages in the Administration Log view in the WebSphere Message Broker Explorer, and the Deployment log in the WebSphere Message Broker Toolkit.
Activity Log
Activity log information is displayed in the Activity Log view in the WebSphere Message Broker Explorer, and displays messages about recent activities in your message flows and associated external resources. The messages can provide early information about errors that have occurred in your message flow, such as a connection to an external resource being broken. See Using Activity logs.
The Problems or Alerts view
- In the Broker Application Development perspective the Problems view shows information messages, warnings, and errors for message flow applications and associated resources, such as message flows, message sets, ESQL, Java™, and mapping.
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 WebSphere Message Broker Toolkit. 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 Message Sets: TDS message model integrity.