topic Java agent not reporting in appd controller after the finished patching. in Splunk AppDynamics

Java agent not reporting in appd controller after the finished patching.

Neha_Dev1 — Tue, 23 Feb 2021 17:07:12 GMT

The java agent was installed and it was reporting fine, but last week the server was down , and after the patching work was done, it was not reporting in AppD. AppD did not come back up when the server came back up.

Please suggest.

Re: Java agent not reporting in appd controller after the finished patching.

iamryan — Tue, 23 Feb 2021 23:04:58 GMT

Hi @Neha.Dev,

Thanks for asking your question in the community. There is an existing post on Community that could be related.

Please check it out here:

If you learn anything from that post, please share what you learned as a reply to this post.

Re: Java agent not reporting in appd controller after the finished patching.

Morelz — Thu, 25 Feb 2021 05:59:11 GMT

Hi Neha

Would you be able to provide more information?

The Java Agent is added to the startup of the Application it's instrumenting, so a server restart would not affect the agent, as when the application starts , the agent will start with it.

Can you validate that the Appdynamics Java Agent is still part of the Application Java Process, you can check using any command e.g ps aux | grep "javaagent".

It might be possible that the following occurred

1. Java Agent directory itself was removed, or permissions changed with patching

2. Server firewall turned on, blocking the Java Agent from communicating to the Controller

3. Application was patched, which removed the Java Agent startup parameters.

Ciao