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
See information about the latest product version
Resolving trace problems when developing message flows
Follow this advice to deal with some common trace problems that can arise when you develop message flows.
You cannot determine which node is being referenced in your trace file
You cannot see any alerts when you change user trace
- Scenario: You cannot see any alerts for an execution group or message flow in the Alerts viewer when you use the mqsichangetrace command to change the user trace setting.
- Explanation: No alert is generated when an execution group runs user trace at normal or debug level. Alerts are generated only for message flow trace. For message flow trace, the WebSphere® Message Broker Toolkit is not notified of trace changes that are initiated by the mqsichangetrace command.
- Solution: To see the alert, refresh the message flow, or disconnect, then reconnect to the domain.
Data that the Trace node sends to the syslog on UNIX is truncated
- Scenario: You are using a Trace node on UNIX and have set the Destination property to Local Error Log. You send a message to the Trace node that consists of multiple lines, but the message that appears in the syslog is truncated at the end of the first line.
- Explanation: On UNIX, syslog entries are restricted in length and messages that are sent to the syslog are truncated by the new line character.
- Solution: To record a large amount of data in a log on UNIX, set the Destination property on the Trace node to File or User Trace instead of Local Error Log.