Chapter 17. Stopping the Camel Debugger
Overview
The way to stop the Camel debugger depends on the mode in which it is running:
Local debugging (olink:RiderUG/localDebug)
To stop the Camel debugger, click
on the menu bar once if the debugging session has ended. Otherwise, click
twice: once to terminate the currently running node thread and once to terminate the Camel Contextthread (both displayed in the Debug view).NoteTerminating the Camel debugger also terminates the console but does not clear its output. To clear the output, click
(Clear Console) on the Console view’s menu bar.
Remote debugging (olink:RiderUG/remoteDebug)
To stop the Camel debugger, select the
[Remote Camel Context]thread or the[Remote Camel Context and Java]thread in the Debug view, and then click
on the menu bar.
NoteTerminating the Camel debugger does not close the connection to the remote runtime server in the Servers view nor in the JMX Navigator view.
Closing the Camel debugger
After you have finished debugging your project, you may want to close the Debug perspective to make more space for your workbench.
To do so, right-click
on the right side of the JBoss Developer Studio toolbar, and then select Close.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.