A formatted log file, like the one in Formatting trace, contains a sequence of WebSphere Event Broker messages that records the activity in a specific part of the system (the part that you identify when you start the trace). You can use this sequence to understand what is happening, and to check that the behavior that is recorded is what you are expecting.
For example, if you have activated message flow trace, you can see entries that record the path that a message takes through the message flow, and why decisions result in this path (where a choice is available).
The messages contain identifiers for the resources that are being traced, for example the execution groups and message flows. The identifier that is given is usually the label (the name) that you gave to the resource when you defined it.
Timestamp Thread ID Trace type Message 2005-07-12 16:17:18.242605 5344 UserTrace BIP2537I: Node 'Reply.MapToRequestor': Executing statement ''SET I = I + 1;'' at ('.MapToRequestor.CopyMessageHeaders', '6.4'). 2005-07-12 16:17:18.242605 5344 UserTrace BIP2539I: Node 'Reply.MapToRequestor': Evaluating expression ''I'' at ('.MapToRequestor.CopyMessageHeaders', '6.12'). This resolved to ''I''. The result was ''1''. 2005-07-12 16:17:18.242605 5344 UserTrace BIP2539I: Node 'Reply.MapToRequestor': Evaluating expression ''I + 1'' at ('.MapToRequestor.CopyMessageHeaders', '6.14'). This resolved to ''1 + 1''. The result was ''2''. 2005-07-12 16:17:18.242605 5344 UserTrace BIP2566I: Node 'Reply.MapToRequestor': Assigning value ''2'' to field / variable ''I''.References such as '6.12' apply to the row and column number within a function that specify the location of the command that is being executed; in this case, row 6, column 12.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
au14320_ |