How can we address the slowness issue in Tomcat when using the Java Agent?
RCA : The slowness during application startup can be attributed to the scanning of the agent JAR performed by Tomcat. The slowness is primarily a result of Tomcat's encryption verification and decompression processes applied to each class within the signed agent JAR during scanning. It's noteworthy that this performance issue is particularly noticeable in Java 8. In contrast, Java 9 and later versions exhibit a minimal startup delay, typically ranging from 100 to 200 milliseconds.
To resolve this issue, kindly add the apminsight-javaagent.jar to the jarsToSkip property in the catalina.properties file.
New to ADSelfService Plus?
Related Articles
Adding APM Insight Java agent in a Kubernetes environment
There are three methods for installing the APM Insight Java agent in a Kubernetes environment: Using Dockerfile Using InitContainers Using Persistent Volumes Prerequisites Download the latest APM Insight Java agent ZIP file. Extract the ZIP file and ...How to rename an existing APM - Java agent application's monitor?
In Applications Manager's APM(Application Performance Monitoring) doesn't support renaming applications/monitors from the web client. However, the application name of an existing application instance can be renamed in the `apminsight.conf` file and ...Self monitor Applications Manager using APM Insight Java Agent
Applications Manager is built with Java, hence we can monitor it using APM Insight Java Agent to measure it's performance continuously, which can be very much useful. Setting up APM Insight Java Agent Follow the below steps to download and set up the ...How to add an APM Insight Java agent in Kubernetes via InitContainers?
Step 1. Create a secret to access the APM Insight license key in your application namespace: kubectl create secret generic app-secret --from-literal=s247licensekey='your_APMInsight_license_key' -n petclinic The license key can be obtained from the ...Applications Manager default tomcat is down
If your Tomcat Monitor is down, it could probably be due to changes in Hostname/IP address of the machine in which Applications Manager is installed. You can verify the same using the steps given below: Navigate to ...