📘

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

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

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

2. Increase ReservedCodeCache to at least 512mb by adding the following flag
   -XX:ReservedCodeCacheSize=512m

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.

❗️

Rootless Agent Installation Method (Linux only)

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

The OverOps Agent runs on the JVM. You can launch the JVM with OverOps, using various launchers. When launching the JVM with Glassfish, follow the instructions of the relevant debug configuration:

Standalone Glassfish

To launch JVM with Glassfish:

1. From the {glassfish dir}/domains/{domain}/config/ directory, locate the domain.xml file.
2. Locate the xml node.
3. Under , add the following node:

<jvm-options>-agentlib:TakipiAgent</jvm-options>

or respectively

<jvm-options>-agentpath:<TAKIPI_HOME>/lib/libTakipiAgent.so</jvm-options>

4. Restart Glassfish.
5. Test your Installation

Admin Console/Netbeans Plugin

Glassfish-Netbeans Plugin

Eclipse Plugin

Glassfish-Eclipse Plugin

IntelliJ Plugin

Glassfish-IntelliJ Plugin