Chapter 16. Stopping the Camel Debugger

download PDF


The way to stop the Camel debugger depends on the mode in which it is running:

  • Local debugging (Section 15.1, “Debugging a locally running routing context”)

    To stop the Camel debugger, click Terminate button on the menu bar once if the debugging session has ended. Otherwise, click Terminate button twice: once to terminate the currently running node thread and once to terminate the Camel Context thread (both displayed in the Debug view).


    Terminating the Camel debugger also terminates the console but does not clear its output. To clear the output, click clear co (Clear Console) on the Console view’s menu bar.

  • Remote debugging (Section 15.2, “Debugging a remotely running routing context”)

    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 Terminate button on the menu bar.


    Terminating 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 Debug perspective icon on the right side of the CodeReady Studio toolbar, and then select Close.

Red Hat logoGithubRedditYoutubeTwitter


Try, buy, & sell


About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.