Starting manually

Sometimes, automatically starting JRebel Debugger Proxy (JDP) from the JRebel Agent is not possible. For example:

  • The application is running with the JRebel Java agent instead of the JRebel native agent.

  • There are network configuration issues that prevent launching or connecting to the JDP launched from the JRebel native agent.

  • You want greater control over JDP.

In this case, you can start JDP manually.

Important

Starting in JRebel 2025.4.1, jr-debugger-proxy.jar is distributed in the jrebel-<version>-nosetup.zip package in the jrebel/ subdirectory, in the package alongside jrebel.jar.


From the command line, run:

java -jar /some_path/jrebel/jr-debugger-proxy.jar <proxy port> <host> <JDWP port>

For example:

java -jar /home/myuser/jrebel/jr-debugger-proxy.jar 9199 localhost 8188

where:

  • <proxy port> is the port that the IDE debugger connects to.

  • <host> is the host name or IP address of the host where the target application runs. Usually, JDP runs on the same host as the target application; therefore, localhost is a reasonable value. A different value should be supplied if JDP runs on a different node than the target application, or if localhost is not resolvable.

  • <JDWP port> is the port specified in the -agentlib:jdwp=transport=dt_socket...address= argument.