doc.overops.com

JBoss/Wildfly

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

When OverOps is installed on your machine, connect it to your JBoss server.
Follow the instructions of the relevant JBoss launch configuration:

Standalone JBoss/Wildfly

To connect to JBoss/Wildfly running on Linux/macOS:

  1. Locate the standalone.conf file under {jboss dir}/bin.
  2. Add the following line near the end of the file:
    JAVA_OPTS="$JAVA_OPTS -agentlib:TakipiAgent"
  3. Restart JBoss.
  4. Test your Installation

To connect to JBoss running on Windows:

  1. Locate the standalone.conf.bat file under {jboss dir}\bin.
  2. Add the following line near the end of the file:
    set JAVA_OPTS=%JAVA_OPTS% -agentlib:TakipiAgent
  3. Restart JBoss.
  4. Test your Installation

Eclipse Plugin

see JBoss-Eclipse Plugin

IntelliJ Plugin

see JBoss-IntelliJ Plugin

NetBeans Plugin

see JBoss-NetBeans Plugin

Updated 7 months ago

JBoss/Wildfly


Suggested Edits are limited on API Reference Pages

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