ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Agent not picking up the agent name automatically from application server


Article ID: 129747


Updated On:


CA Application Performance Management Agent (APM / Wily / Introscope) INTROSCOPE


We have deployed a Weblogic agent and is not picking up the agent name automatically from the Weblogic application server.
The agent package was created through APM Command Center:
more apmccsrv-10.7.0.ver APM Command Center Configuration Server Technologies 20180829-0529

In the agent profile we have configured the agent name as follows:

Seems the Agent couldn't get the name from the web server in time, so it falls back to the name defined in the profile:
[INFO] [IntroscopeAgent.Agent] Unable to automatically determine the Agent name before the connection delay timeout.

We also tried increasing the timeout but the problem persists.


This is happening for the fact that we are missing the IntroscopeWLStartupTracer tracer in the agent which is the tracer to pass the agent name from the Weblogic server, and it's in wl100x.pbd.



Agent 10.x, ACC 10.x


We would suggest to try the following:

a) Make sure Weblogic is selected as the application server when building this package in APM Command Center. This should address this issue.
b) Try including all Weblogic pbds to directive files property in the agent profile and restart the application.

NOTE: this particular case is related to Weblogic but the same suggestions are applicable for any other application server.


Additional Information

How does APM agent determine its name before it decides to use the default Agent name "UnknownAgent"?

Customize Java Agent naming based on Application.