topic Re: Java Agent issue in Splunk AppDynamics

Java Agent issue

Vikant_Bhati1 — Thu, 06 Jul 2023 18:04:28 GMT

When i run the agent, it always shows me this message "Started AppDynamics Java Agent Successfully."

But in logs is logs/argentoDynamicService_07-06-2023-10.47.50 file, it is showing the below error,

ErrorOccurred==> Unable to complete registration on policy file argentoPolicy.json from the Management Server https://cas********.saas.appdynamics.com/argento-agent/v1/management,
Error: java.lang.Exception: ERROR from Controller Response: Invalid tenant.

Note:-
this error is inconsistant, sometime it got connected to the controller with the same configuration.

Re: Java Agent issue

iamryan — Fri, 07 Jul 2023 17:39:14 GMT

Hi @Vikant.Bhati,

I was able to do some digging around and found this info.

The issue might be related to the Security Agent. If you are not using Security Agent.
Please remove the argentoDynamicService folder from <java-agent-home>/<version>/external-services

You can refer to the below document on Argento related.
https://docs.appdynamics.com/appd/22.x/latest/en/application-security-monitoring/cisco-secure-application-requirements

Re: Java Agent issue

Vikant_Bhati1 — Sat, 08 Jul 2023 11:15:06 GMT

Still facing the same issue

Re: Java Agent issue

Vikant_Bhati1 — Sat, 08 Jul 2023 11:52:37 GMT

Container id: 7b46ba684c04ecdfced7c1c51c948b8f41e98257893d90c9ff500ff0be3e13e3
[AD Thread Pool-Global1] 08 Jul 2023 11:37:21,945 INFO ConfigurationChannel - Agent node meta-info thus far: ProcessID;1;appdynamics.ip.addresses;172.17.0.2;appdynamicsContainerId;7b46ba684c04ecdfced7c1c51c948b8f41e98257893d90c9ff500ff0be3e13e3;appdynamicsHostName;7b46ba684c04
[AD Thread Pool-Global1] 08 Jul 2023 11:37:21,945 INFO ConfigurationChannel - Detected node meta info: [Name:ProcessID, Value:1, Name:appdynamics.ip.addresses, Value:172.17.0.2, Name:appdynamicsContainerId, Value:7b46ba684c04ecdfced7c1c51c948b8f41e98257893d90c9ff500ff0be3e13e3, Name:appdynamicsHostName, Value:7b46ba684c04, Name:supportsDevMode, Value:true]
[AD Thread Pool-Global1] 08 Jul 2023 11:37:21,945 INFO ConfigurationChannel - Sending Registration request with: Application Name [my-app], Tier Name [tier1], Node Name [docker-node], Host Name [7b46ba684c04] Node Unique Local ID [docker-node], Version [Server Agent #23.6.0.34839 v23.6.0 GA compatible with 4.4.1.0 r8e3a55588eed933a4f6bb44c4dec9edc8c25073f release/23.6.0]
[AD Thread Pool-Global1] 08 Jul 2023 11:37:22,311 WARN ConfigurationChannel - ResponseReadException creating Response Wrapper [AppAgentConfigurationBinaryRequest], : com.singularity.ee.rest.ResponseReadException: Error in controller in processing binary request AppAgent Config Data - Limit reached for: APPLICATION; Scope: Controller; Limit: 20000
[AD Thread Pool-Global1] 08 Jul 2023 11:37:22,311 WARN ConfigurationChannel - Unable to get AppAgentConfigurationResponse from controller

Currently I am using the free-trial.

Re: Java Agent issue

iamryan — Mon, 10 Jul 2023 18:21:02 GMT

Hi @Vikant.Bhati,

I'll see if I can find any other info. Let's see if the community can jump in and help too.
If you happen to do more digging and find out what went wrong, please share that here too.