Default Java Agent is not starting
Article ID: 130334
Updated On:
Products
CA Application Performance Management Agent (APM / Wily / Introscope)
INTROSCOPE
Issue/Introduction
Installed Default JAVA Agent on Open Text Custom java application.
Using following parameters but the default agent is not starting.
set JAVA_OPTIONS=%JAVA_OPTIONS% -javaagent:/opt/CA/APM/wily/Agent.jar -Dcom.wily.introscope.agentProfile=/opt/CA/APM/wily/core/config/IntroscopeAgent.monitor.profile export JAVA_OPTIONS
Using following parameters but the default agent is not starting.
set JAVA_OPTIONS=%JAVA_OPTIONS% -javaagent:/opt/CA/APM/wily/Agent.jar -Dcom.wily.introscope.agentProfile=/opt/CA/APM/wily/core/config/IntroscopeAgent.monitor.profile export JAVA_OPTIONS
Environment
APM 10.5.2 SP2
Solaris Enterprise Server 12 SP2
Custom Java Application
Oracle JDK 1.6.045 32 bit
Solaris Enterprise Server 12 SP2
Custom Java Application
Oracle JDK 1.6.045 32 bit
Cause
Unsupported JVM Version
Resolution
Upgrade the JVM
If the Application strictly uses Oracle 1.6 JDK, we won't be able to help as Java 1.6 is no longer supported.
As per CA APM 10.5.2 Release Notes:
https://docops.ca.com/ca-apm/10-5/en/ca-apm-release-notes
Java 1.6 No Longer Supported
We no longer support the Java agent on JVM 1.6 run time. If you have applications on Java 6, you can use the older version of the agent. Our agents are always compatible and fully supported on higher versions of the Enterprise Managers.
If the Application strictly uses Oracle 1.6 JDK, we won't be able to help as Java 1.6 is no longer supported.
As per CA APM 10.5.2 Release Notes:
https://docops.ca.com/ca-apm/10-5/en/ca-apm-release-notes
Java 1.6 No Longer Supported
We no longer support the Java agent on JVM 1.6 run time. If you have applications on Java 6, you can use the older version of the agent. Our agents are always compatible and fully supported on higher versions of the Enterprise Managers.
Additional Information
Feedback
Yes
No
Powered by
