Resolving problems when debugging message flows

This topic contains advice for dealing with some of the common problems that can arise when debugging message flows.

A timeout occurs before the Rational Agent Controller service can connect

The debugger does not pause at the next breakpoint

The message does not stop executing at any breakpoint

Editing problems occur in the Message Flow editor

Editing the MQ message descriptor (MQMD) causes unexpected behavior in the debugger

You cannot see the message content when debugging your message flow

You cannot see the message flow names in the Debug view

You cannot see the deployed flow names in the Debug view

An exclamation mark appears above a node during debugging

The PutTime that is reported by WebSphere MQ on z/OS, and other times or timestamps are inconsistent

The message does not stop processing at breakpoints

Start of change

You cannot see where the debugger is in the message mapping editor

End of change
Start of change

When debugging a message map, the debugger does not move to the next field

End of change
Start of change

When debugging a message map, the debugger does not move out of the mapping node

End of change
Start of change

The message flow stops at a collector node

Related concepts
Flow debugger overview
End of change
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:23:29

au16612_