Standalone JVM


Attaching the OverOps Agent to a JVM Running Java 10,11, 16 or 17

When attaching an OverOps Agent to a JVM that is running Java 10, 11, 16 or 17 or any IBM java versions, follow these guidelines:

  1. Turn off Class Sharing: This can be done using the following flags:
    for IBM Java
    for HotSpot
    -Xshare:off -XX:-UseTypeSpeculation

  2. Increase ReservedCodeCache to at least 512mb by adding the following flag

  3. The Agent should appear last in the VM arguments list before specifying the main class or jar.

  4. When adding/removing 3rd party packages, the Agent should be restarted.

Additionally, if you wish to upgrade your own compiler to target Java 10/11, then you'll have to upgrade your Collector (SaaS) or Collector + backend (On-Premises) to support it.

Connecting the OverOps Agent

To connect OverOps to your application, add the following argument to your JVM startup arguments:



Rootless Agent Installation Method (Linux only)

When Using the Rootless Agent Installation Method replace the
-agentlib:TakipiAgent JVM startup Argument
-agentpath:<TAKIPI_HOME>/lib/ JVM startup Argument


Important: -agentlib is a JVM argument and has to be written before -jar / -cp arguments. For example:
java -Xmx2G -agentlib:TakipiAgent -jar myapp.jar
or respectively
java -Xmx2G -agentpath:<TAKIPI_HOME>/lib/ -jar myappjar

Using Maven

In the terminal / command line, add -agentlib:TakipiAgent to the MAVEN_OPTS environment variable:

Linux / macOS:

export MAVEN_OPTS="$MAVEN_OPTS -agentlib:TakipiAgent"


set MAVEN_OPTS=%MAVEN_OPTS% -agentlib:TakipiAgent