About Debug Sessions
A debug session starts when you use a launch configuration to debug a service. Designer requires a launch configuration for debugging a flow service. If a service does not have a launch configuration, Designer creates one automatically. Designer saves the launch configuration to your workspace.
Designer creates a debug session for each launch configuration that you use for debugging a service. You can use multiple launch configurations simultaneously and have multiple debug sessions for the same launch configuration. This translates to multiple debug sessions for the same service. Debug view displays all of the debug sessions. The name of the launch configuration used for a debug session appears as a top level node in the Debug view. The launch configuration can appear in the Debug view multiple times, once for each debug session.
Once started, debug sessions can suspend, resume, or terminate.
A debug session suspends for the following reasons:
The launch configuration specifies that the debug session should stop at the first flow step.
A step command finishes execution (
Step Over,
Step Into, or
Step Return).
Designer suspends the debug session immediately before executing the next step in the flow service when a breakpoint is encountered. In case of
Debug to Here, the execution continues till the specified step even if breakpoints are encountered.
A debug session resumes when you select Run > Resume or execute a step command.
A debug session terminates for the following reasons:
The flow service that you are debugging executes to completion (error or success).
You select the
Step Over command for the last step in the flow service.
You forcefully terminate the debug session by selecting
Run > Terminate.
You exit Eclipse.