Debug: running to completion

When message flow processing pauses at an active breakpoint, you can choose to let it continue to the end of the flow, ignoring other breakpoints.

Before you start:

Add one or more breakpoints to your message flow. See: Adding breakpoints in the flow debugger.

When message flow processing has paused at a breakpoint, you can restart processing so that the message flow runs to completion.

If you want the flow to continue processing, but you want to pause at the next enabled breakpoint instead of running to completion, see: Debug: resuming message flow processing.

  1. Switch to the Debug perspective.
  2. In the Debug view:
    • either, click Run to completion Run to completion on the toolbar.
    • or, right-click the flow stack frame, then click  Run to completion Run to completion.
The flow instance ignores all breakpoints and processing continues to the end. The flow instance is automatically removed from the Debug view.

Next:

If you have finished debugging, you can remove the breakpoints, or end the debugging session:
Related concepts
Flow debugger overview
Debug perspective
Related tasks
Debug: resuming message flow processing
Working with breakpoints in the flow debugger
Debug: ending a session
Related reference
Flow debugger shortcuts
Flow debugger icons and symbols
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:21:54

ag11280_