GuidesAPI
DocumentationAPICommunitySupportLog In

📘

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

Once you install OverOps, you’ll have to connect it. If you’re using NetBeans, please choose the debug configuration you’re using to launch your application:

Java/Scala Application

  1. Open the File | Project Properties dialog.
  2. Select Run in the tree pane on the left.
  3. Add to VM Options: -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 OK.
  2. Start the application you want OverOps to monitor.
  3. Test your Installation

NetBeans-Glassfish Plugin

  1. Open the Glassfish console (http://localhost:4848).
  2. Under Common Tasks, expand Configurations > server-config > JVM settings.
  3. Switch to the JVM Options tab.
  4. Add a new JVM option: -agentlib:TakipiAgent or respectively -agentpath:<TAKIPI_HOME>/lib/libTakipiAgent.so
  1. Click Save.
  2. Restart Glassfish.
  3. Test your Installation

NetBeans-JBoss Plugin

  1. Enter the Services window (Window | Services).
  2. Expand Servers.
  3. Right-click Wildfly Application Server.
  4. Select Properties.
  5. Select the Platform tab.
  6. Add to VM Options: -agentlib:TakipiAgent
  1. Click Close.
  2. Start JBoss.
  3. Test your Installation

NetBeans-Tomcat Plugin

  1. Enter the Services window (Window | Services).
  2. Expand Servers.
  3. Right click on the Apache Tomcat server.
  4. Select Properties.
  5. Select the Platform tab.
  6. In the VM Options box, add: -agentlib:TakipiAgent
  1. Click Close.
  2. Start Tomcat.
  3. Test your Installation