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
    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.


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

The OverOps agent is already included within the java build pack. To get the latest agent, you should update the java build pack (requires Admin rights):

1.Update the java-buildpack
cf update-buildpack java-buildpack-offline

2.Create a User-provided service
Connecting to a remote collector we are providing the remote collector host and remote collector port (6060 is default).
cf cups takipi -p '{"collector_host":"<collector-host-domain-name-here>","collector_port":"6060"}'

3.Attach the Micro Agent to your JVM (The application you want to monitor)
Bind the application service to the OverOps agent:

cf bind-service APP_NAME takipi
cf restage APP_NAME

4.Update system parameters with application and deployment names

cf set-env my-application JAVA_OPTS '<version-name-here>'
cf set-env my-application JAVA_OPTS '<app-name-here>'

or combined

cf set-env my-application JAVA_OPTS '<app-name-here><version-name-here>'

5.Test your Installation