Resolving problems that occur when starting and stopping the
debugger
Use the advice given here to help
you to resolve common problems that can arise when you debug message
flows.
An endless "waiting for communication" progress bar is displayed
when you start the debugger
The debugger seems to stop
- Scenario: You are debugging a message flow and continue
after encountering a breakpoint. However, nothing seems to happen
and after about a minute, a progress bar appears, indicating that
the debugger is waiting for communication.
- Explanation: This situation can occur for the following
reasons:
- The message flow might have encountered a time-intensive operation,
such as a huge database query, and you must wait for the flow to complete
the action.
- The broker ended, or some other extraordinary condition occurred,
and communication was lost. In this case, click Cancel to
stop the debug session.
The session ends abnormally while debugging
- Scenario: After debugging a message flow, the session
ends abnormally and you still have the debug instance of the message
flow (mf_debug_) deployed to the broker's execution group. You are
concerned that this is going to affect the operation of the flow,
and want to put the execution group back to its original state.
- Explanation: The orphaned message flow should behave
as the flow would have done normally, and the Debug nodes have no
effect on message processing. If you have a small number
of nodes in the message flow, corrective action makes no noticeable
difference to the flow, apart from its name. However, if you have
a large message flow (that is, more than 15 nodes or several subflows),
take the corrective action described later in this section, because
the performance of message processing might be affected.
- Solution: Redeploy the broker.
A
full redeploy of the broker should replace the orphaned flow with
the original message flow. If this action has no effect, remove the
orphaned flow from the execution group, deploy, then add the flow
and deploy to restore the original state of the broker as it was before
the debugging session.
An error message is displayed indicating that the debug session
cannot be launched
- Scenario: You try to relaunch or invoke a new debug
session but when you click the green Debug icon
,
an error message is displayed stating: Cannot launch this debug
session.
- Explanation: When you click Debug ,
it relaunches the last debug session. It fails if you have not created
a debug session previously. It also fails if the broker and execution
group that were attached previously in a debug session are no longer
running, or have been restarted; the session cannot be reattached
without re-selection of the broker and execution group process instance.
- Solution:
- Close the error message and click the arrow immediately
to the right of the Debug icon.
- Re-select or modify the broker and execution group information
from the previous debug launch configuration by clicking Debug in
the menu and selecting the previous debug launch configuration. See Attaching the flow debugger to an execution group for debugging for more information.
Errors are generated when you copy a message
map into an application, library, or Message Broker
project
- Scenario: You are copying a message
map into an application, library, or Message Broker
project and
errors have appeared in the task list.
- Explanation: The application, library,
or Message Broker
project did
not have the correct references set before you copied the message
mapping.
- Solution: These errors remain in
the task list, even if you reset the project references immediately
after copying. Therefore, you must perform a clean build of the application,
library, or Message Broker
project.