JRebel 7.0.0 Agent upgrade

New agent, fewer redeploys.

What I need to know before I upgrade

To upgrade JRebel in your IDE, follow the standard plugin update procedures for your IDE. When using a standalone JRebel distribution, simply download the new binaries.

JRebel Agent is the new default

Upgrading to JRebel 7.0.0 will switch some of the users to the JRebel Agent automatically, while others need need to do a simple reconfiguration.

Running servers via IDE?

Users who run their servers or applications via the IDE will automatically be migrated to the new agent.

You can always check which agent you are using. The agent details are displayed in the JRebel console banner at startup. When using an IDE plugin, you can check your active agent via Help > JRebel > Configuration > Advanced.

Running servers on command line or remotely?

When running application servers or standalone applications from the command line, some configuration changes are required.

To start the new JRebel Agent from a command line, we now use the -agentpath parameter (instead of -javaagent). We also no longer reference the JAR file directly — instead we refer to the dynamic libraries bundled for each operating system and JVM bitness. Here is an example of a JVM argument for starting the JRebel Agent from a command line on Windows with a 64-bit JVM:

-agentpath:C:/JRebel/lib/jrebel64.dll

We have updated our documentation to reference these changes. When using an IDE plugin, open Help > JRebel > Configuration > Startup and select either Run locally from command line or Run on a remote server or VM. From there, pick the desired application server to see startup instructions. You can also find all new command line startup instructions in the reference manual.

Legacy Agent is still available

The Legacy Agent is still part of the release. Need to revert to the Legacy Agent? Get help here.