JRebel 7.0.0 agent command line startup

With the release of JRebel 7, we have revised the agent file locations and startup configuration. You will need to edit your startup scripts!

Running the new JRebel Agent

The new JRebel Agent no longer works using -javaagent. This change affects users previously running with the Legacy Agent from a command line (as well as on a remote machine or container).

Here is how you should start the new JRebel Agent:


You need to replace the jrebel64.dll based on your operating system and JVM bitness:

  • jrebel64.dll — Using a 64-bit JVM on Windows.
  • jrebel32.dll — Using a 32-bit JVM on Windows.
  • libjrebel64.dylib — Using a 64-bit JVM on macOS.
  • libjrebel32.dylib — Using a 32-bit JVM on macOS.
  • libjrebel64.so — Using a 64-bit JVM on Linux.
  • libjrebel32.so — Using a 32-bit JVM on Linux.

Other operating systems and architectures

When using a non-x86 or non-x86-64 architecture, or different operating systems, follow the instructions here.

Using Java 4 or Java 5

The new JRebel Agent requires Java 6 or newer. When using Java 4 or Java 5, you can still use the Legacy Agent. You can find it in the legacy folder within the standalone ZIP archive.

The Legacy Agent is still started using the -javaagent parameter:


Using Java 4 still requires bootstrapping. Read more here.

The new JRebel standalone ZIP structure

Here are the locations of the important files in the standalone zip archive. Keep these in mind when extracting files for use in standalone or remote scenarios:

/jrebel.jar - This is the new JRebel Agent.
/legacy/jrebel.jar - This is the Legacy Agent. 
/lib/jrebel64.dll - JRebel Agent Windows 64-bit library.
/lib/jrebel32.dll - JRebel Agent Windows 32-bit library.
/lib/libjrebel64.dylib - JRebel Agent macOS 64-bit library.
/lib/libjrebel32.dylib - JRebel Agent macOS 32-bit library.
/lib/libjrebel64.so - JRebel Agent Linux 64-bit library.
/lib/libjrebel32.so - JRebel Agent Linux 32-bit library.