Resolving problems that occur when debugging message flows
Advice on dealing with some of the common problems that you see when debugging message flows.
About this task
- Resolving problems that occur when starting and stopping 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 debug session cannot be launched
- Errors are generated when you copy a message map into an application, library, or integration project
- Resolving problems when debugging message flows
- 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
- An exclamation mark appears above a node during debugging
- The message does not stop processing at breakpoints
- Resolving problems that occur after debugging: