This is a cache of https://docs.openshift.com/container-platform/4.5/cli_reference/developer_cli_odo/debugging-applications-in-odo.html. It is a snapshot of the page at 2024-11-23T00:35:01.628+0000.
Debugging applications in odo - Developer <strong>cli</strong> (odo) | <strong>cli</strong> tools | OpenShift Container Platform 4.5
    OpenShift docs are moving and will soon only be available at docs.redhat.com, the home of all Red Hat product documentation. Explore the new docs experience today.
  1. Documentation
    2. history
×

Debugging applications in odo

With odo, you can attach a debugger to remotely debug your application. This feature is only supported for NodeJS and Java components.

Components created with odo run in the debug mode by default. A debugger agent runs on the component, on a specific port. To start debugging your application, you must start port forwarding and attach the local debugger bundled in your Integrated development environment (IDE).

Debugging an application

You can debug your application on in odo with the odo debug command.

Procedure

  1. After an application is deployed, start the port forwarding for your component to debug the application:

    $ odo debug port-forward

  2. Attach the debugger bundled in your IDE to the component. Instructions vary depending on your IDE.

Configuring debugging parameters

You can specify a remote port with odo config command and a local port with the odo debug command.

Procedure

  • To set a remote port on which the debugging agent should run, run:

    $ odo config set DebugPort 9292

    You must redeploy your component for this value to be reflected on the component.

  • To set a local port to port forward, run:

    $ odo debug port-forward --local-port 9292

    The local port value does not persist. You must provide it every time you need to change the port.