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.

Starting and stopping the debugger:
During debugging:
After debugging:

Java class error messages are displayed when you start the debugger

An endless "waiting for communication" message is displayed when you start the debugger

The debugger seems to stop

The session ends abnormally while debugging

An error message is displayed indicating that the Rational Agent Controller is not installed

Message flow engines are not available for selection

You cannot see the list of execution groups

You see the wrong execution group names in the Agent page

Shared Memory Allocation Error on AIX

An error message is displayed indicating that the debug session cannot be launched

A timeout occurs while waiting for the Rational Agent Controller service to 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

There is an exclamation mark above a node during debugging

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

You cannot change a message flow after debugging

You redeployed a debugged message flow but deployment hangs

The message does not stop executing at any breakpoint

Errors are generated when you copy a message map into a message flow project

Related concepts
Flow debugger overview