doc.overops.com

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.

Naming Your Application and Deployment

Naming your applications and deployment allows us to aggregate your data and to sort, view, and compare them from version over version. The data then feeds into our dashboards (without using a naming convention your data loses value):

  • Give the application a name you'll be able to easily track
  • Give your deployment a distinct name so that whenever you deploy new code to your application, you'll be able to distinguish between different deployments that will show up in the OverOps Dashboard

Use the following arguments:
-Dtakipi.application.name=<APPLICATION_NAME>
-Dtakipi.deployment.name=<DEPLOYMENT_NAME>

To learn more, see Naming the Application, Server, Deployment.

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

After you install OverOps, you will need to connect it. Please choose the debug configuration you’re using to launch your application:

Java/Scala Application
Glassfish Plugin
JBoss Plugin
Tomcat Plugin

Java/Scala Application

  1. Open “Run | Edit Configurations“.
  2. Locate your project’s application configuration.
  3. In the VM options box, add: -agentlib:TakipiAgent or respectively -agentpath:<TAKIPI_HOME>/lib/libTakipiAgent.so.
    Note that for macOS, Linux and Windows, you'll use a takipi agent file with different extensions.
  1. Click Apply.
  2. Test your Installation

Glassfish-IntelliJ Plugin

  1. Edit Glassfish Run/Debug configurations.
  1. From Run/Debug Configuration, In the VM options field, add: -agentlib:TakipiAgent or respectively -agentpath:<TAKIPI_HOME>/lib/libTakipiAgent.so
  1. Click OK.
  2. Start Glassfish.
  3. Test your Installation

JBoss-IntelliJ Plugin

  1. Edit Wildfly Run/Debug configurations.
  1. In the VM options field, add: -agentlib:TakipiAgent or respectively -agentpath:<TAKIPI_HOME>/lib/libTakipiAgent.so
  1. Click OK.
  2. Start JBoss.
  3. Test your Installation

Tomcat-IntelliJ Plugin

  1. Edit Tomcat Run/Debug configurations.
  1. In the VM options field, add: -agentlib:TakipiAgent or respectively -agentpath:<TAKIPI_HOME>/lib/libTakipiAgent.so

3.Click OK.

  1. Start Tomcat.
  2. Test your Installation

Updated 9 months ago

IntelliJ


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.