Mule

📘

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

Mule ESB 3.X or later uses the Tanuki configuration environment. To specify JVM arguments in your Mule ESB environment, you need to configure them as additional parameters to the Tanuki Java Service Wrapper configuration file, wrapper.conf, as described below.

1. Open the configuration file <MULE_HOME>/conf/wrapper.conf.
2. Find the location indicated for Java Additional Parameters:

# Java Additional Parameters 
wrapper.java.additional.1=

3. Add -agentlib:TakipiAgent or respectively -agentpath:<TAKIPI_HOME>/lib/libTakipiAgent.so argument using a wrapper.java.additional.n parameter.
4. Start the application you want OverOps to monitor.
5. Test your Installation