DXI agent is not connecting to the EM
Article ID: 132187
Updated On:
Products
CA Application Performance Management Agent (APM / Wily / Introscope)
INTROSCOPE
Issue/Introduction
CA DXI Agent is not able to connect to EM;
[WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at ext-ca-apm-svc.default.svc.cluster.local:5001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (java/net/ManagedSocketOutputStreamAPSIHighPerformanceNew)
It doesn't seem to be able to connect to the APM infrastructure..
Running on-premise 10.7 APM
[WARN] [IntroscopeAgent.ConnectionThread] Failed to connect to the Introscope Enterprise Manager at ext-ca-apm-svc.default.svc.cluster.local:5001,com.wily.isengard.postofficehub.link.net.DefaultSocketFactory (java/net/ManagedSocketOutputStreamAPSIHighPerformanceNew)
It doesn't seem to be able to connect to the APM infrastructure..
Running on-premise 10.7 APM
Cause
1. Incorrectly configured JVM Argument on the Application Startup Script.
2. Incorrect path for the Wily Agent jar files.
2. Incorrect path for the Wily Agent jar files.
Environment
DX APM On-Premise APM
DX DXI SaaS Agent
DX DXI SaaS Agent
Resolution
1. Make sure that the Java options are added before the running jar file.
Example: -patch-module java.base=/opt/apm/wily/common/AgentSocket.jar -jar /deployments/SNAPSHOT.jar
2. Make sure that the path for the all the Agent jar files are correct and located on the same path.
Agent.jar
AgentSocket.jar
SNAPSHOT.jar
Example: -patch-module java.base=/opt/apm/wily/common/AgentSocket.jar -jar /deployments/SNAPSHOT.jar
2. Make sure that the path for the all the Agent jar files are correct and located on the same path.
Agent.jar
AgentSocket.jar
SNAPSHOT.jar
Additional Information
NA
Feedback
Yes
No
Powered by
