Resolving problems that occur when starting and stopping the debugger:

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

Java class error messages are displayed when you start the debugger

An endless "waiting for communication" progress bar 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

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

  • Scenario: You copied a message map into a message flow project and errors appeared in the task list.
  • Explanation: The message flow project did not have the correct references set before you copied the message mapping.
  • Solution: These errors will remain in the task list, even if you reset the project references immediately after copying; you must perform a clean build of the message flow project.
Related concepts
Flow debugger overview
Notices | Trademarks | Downloads | Library | Support | Feedback

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

au16611_