doc.overops.com

Play Framework

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

Play 2.2+ - Production mode

To connect OverOps to Play 2.2+ in Production mode:

  1. Locate the run script of your Play application. By default is is in: {app_folder}/bin/{app_name}
  2. Locate the line:
    declare -a java_args
  3. Add the following immediately after it:
    java_args=( "${java_args[@]}" "-agentlib:TakipiAgent" )
  4. Restart the application.
  5. Test your Installation

Play 2.3 - Debug mode

To connect OverOps to Play 2.3 in Debug mode:

  1. Run Play in debug mode:
    activator run -J-agentlib:TakipiAgent
  2. Test your Installation

Play 2.2 - Debug mode (Linux/macOS)

To connect OverOps to Play 2.2 in Debug mode from Linux/macOS:

  1. Locate the build file under {play dir}/bin.
  2. Add the following line just before the java execution line:
    PLAY_OPTS="$PLAY_OPTS -agentlib:TakipiAgent"
  3. Run Play in debug mode:
  4. play run
  5. Test your Installation

Play 2.2 - Debug mode (Windows)

To connect OverOps to Play 2.2 in Debug mode from Windows:

  1. Locate the build.bat file under {play dir}\bin.
  2. Add the following line just before the java execution line:
    set PLAY_OPTS=%PLAY_OPTS% -agentlib:TakipiAgent
  3. Run play in debug mode:
  4. play run
  5. Test your Installation

Play 2.0 - Debug mode (Linux / macOS)

To connect OverOps to Play 2.0 in Debug mode from Linux/macOS:

  1. Locate build under {play dir}/bin.
  2. Add the following line just before the java execution line:
    JAVA_OPTS="$JAVA_OPTS -agentlib:TakipiAgent"
  3. Run play in debug mode
  4. play run
  5. Test your Installation

Play 2.0 - Debug mode (Windows)

To connect OverOps to Play 2.0 in Debug mode from Windows:

  1. Locate the build.bat file under {play dir}\bin.
  2. Add the following line just before the java execution line:
    set JAVA_OPTS=%JAVA_OPTS% -agentlib:TakipiAgent
  3. Run play in debug mode
  4. play run
  5. Test your Installation

Updated 9 months ago

Play Framework


Suggested Edits are limited on API Reference Pages

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