Splunk AppDynamics

JAVA Agent failed: Connection refused (Connection refused)

Mandar_Kadam2
New Member

Hi All,

JAVA App Agent is not showing in Tier and Node also in app agent logs I can see following message.

[AD Thread Pool-Global1] 02 May 2024 21:21:31,149 INFO DynamicRulesManager - The config directory /apps/dynamics/ver23.2.0.34668/conf/outbound--2 is not initialized, not writing /apps/dynamics/ver23.2.0.34668/conf/outbound--2/bcirules.xml
[AD Thread Pool-Global0] 02 May 2024 21:21:55,817 ERROR NetVizAgentRequest - Fatal transport error while connecting to URL [http://127.0.0.1:3892/api/agentinfo?timestamp=0&agentType=APP_AGENT&agentVersion=3.2.0]: org.apache.http.conn.HttpHostConnectException: Connect to 127.0.0.1:3892 [/127.0.0.1] failed: Connection refused (Connection refused)
[AD Thread Pool-Global1] 02 May 2024 21:21:55,832 WARN NetVizConfigurationChannel - NetViz: Number of communication failures with netviz agent exceeded maximum allowed [3]. Disabling config requests.
[AD Thread Pool-Global1] 02 May 2024 21:22:55,833 ERROR NetVizAgentRequest - Fatal transport error while connecting to URL [http://127.0.0.1:3892/api/agentinfo?timestamp=0&agentType=APP_AGENT&agentVersion=3.2.0]: org.apache.http.conn.HttpHostConnectException: Connect to 127.0.0.1:3892 [/127.0.0.1] failed: Connection refused (Connection refused)
[AD Thread Pool-Global0] 02 May 2024 21:22:55,848 WARN NetVizConfigurationChannel - NetViz: Number of communication failures with netviz agent exceeded maximum allowed [3]. Disabling config requests.
[AD Thread Pool-Global1] 02 May 2024 21:23:55,849 ERROR NetVizAgentRequest - Fatal transport error while connecting to URL [http://127.0.0.1:3892/api/agentinfo?timestamp=0&agentType=APP_AGENT&agentVersion=3.2.0]: org.apache.http.conn.HttpHostConnectException: Connect to 127.0.0.1:3892 [/127.0.0.1] failed: Connection refused (Connection refused)
[AD Thread Pool-Global0] 02 May 2024 21:23:55,866 WARN NetVizConfigurationChannel - NetViz: Number of communication failures with netviz agent exceeded maximum allowed [3]. Disabling config requests.
[AD Thread Pool-Global1] 02 May 2024 21:25:53,942 INFO DynamicRulesManager - The config directory /apps/dynamics/ver23.2.0.34668/conf/outbound--2 is not initialized, not writing /apps/dynamics/ver23.2.0.34668/conf/outbound--2/bcirules.xml
[AD Thread Pool-Global1] 02 May 2024 21:25:58,948 INFO DynamicRulesManager - The config directory /apps/dynamics/ver23.2.0.34668/conf/outbound--2 is not initialized, not writing /apps/dynamics/ver23.2.0.34668/conf/outbound--2/bcirules.xml
[AD Thread Pool-Global1] 02 May 2024 21:30:53,887 INFO DynamicRulesManager - The config directory /apps/dynamics/ver23.2.0.34668/conf/outbound--2 is not initialized, not writing /apps/dynamics/ver23.2.0.34668/conf/outbound--2/bcirules.xml
[AD Thread Pool-Global0] 02 May 2024 21:35:53,895 INFO DynamicRulesManager - The config directory /apps/dynamics/ver23.2.0.34668/conf/outbound--2 is not initialized, not writing /apps/dynamics/ver23.2.0.34668/conf/outbound--2/bcirules.xml
[AD Thread Pool-Global0] 02 May 2024 21:40:53,906 INFO DynamicRulesManager - The config directory /apps/dynamics/ver23.2.0.34668/conf/outbound--2 is not initialized, not writing /apps/dynamics/ver23.2.0.34668/conf/outbound--2/bcirules.xml
[AD Thread Pool-Global1] 02 May 2024 21:45:53,910 INFO DynamicRulesManager - The config directory /apps/dynamics/ver23.2.0.34668/conf/outbound--2 is not initialized, not writing /apps/dynamics/ver23.2.0.34668/conf/outbound--2/bcirules.xml
[AD Thread Pool-Global0] 02 May 2024 21:49:56,265 ERROR NetVizAgentRequest - Fatal transport error while connecting to URL [http://127.0.0.1:3892/api/agentinfo?timestamp=0&agentType=APP_AGENT&agentVersion=3.2.0]: org.apache.http.conn.HttpHostConnectException: Connect to 127.0.0.1:3892 [/127.0.0.1] failed: Connection refused (Connection refused)
[AD Thread Pool-Global1] 02 May 2024 21:49:56,279 WARN NetVizConfigurationChannel - NetViz: Number of communication failures with netviz agent exceeded maximum allowed [3]. Disabling config requests.
[AD Thread Pool-Global0] 02 May 2024 21:50:53,910 INFO DynamicRulesManager - The config directory /apps/dynamics/ver23.2.0.34668/conf/outbound--2 is not initialized, not writing /apps/dynamics/ver23.2.0.34668/conf/outbound--2/bcirules.xml
[AD Thread Pool-Global1] 02 May 2024 21:50:56,280 ERROR NetVizAgentRequest - Fatal transport error while connecting to URL [http://127.0.0.1:3892/api/agentinfo?timestamp=0&agentType=APP_AGENT&agentVersion=3.2.0]: org.apache.http.conn.HttpHostConnectException: Connect to 127.0.0.1:3892 [/127.0.0.1] failed: Connection refused (Connection refused)
[AD Thread Pool-Global0] 02 May 2024 21:50:56,295 WARN NetVizConfigurationChannel - NetViz: Number of communication failures with netviz agent exceeded maximum allowed [3]. Disabling config requests.
[AD Thread Pool-Global0] 02 May 2024 21:51:56,296 ERROR NetVizAgentRequest - Fatal transport error while connecting to URL [http://127.0.0.1:3892/api/agentinfo?timestamp=0&agentType=APP_AGENT&agentVersion=3.2.0]: org.apache.http.conn.HttpHostConnectException: Connect to 127.0.0.1:3892 [/127.0.0.1] failed: Connection refused (Connection refused)
[AD Thread Pool-Global1] 02 May 2024 21:51:56,309 WARN NetVizConfigurationChannel - NetViz: Number of communication failures with netviz agent exceeded maximum allowed [3]. Disabling config requests.
[AD Thread Pool-Global0] 02 May 2024 21:52:56,310 ERROR NetVizAgentRequest - Fatal transport error while connecting to URL [http://127.0.0.1:3892/api/agentinfo?timestamp=0&agentType=APP_AGENT&agentVersion=3.2.0]: org.apache.http.conn.HttpHostConnectException: Connect to 127.0.0.1:3892 [/127.0.0.1] failed: Connection refused (Connection refused)

Regards,

Mandar Kadam

Labels (1)
0 Karma

iamryan
Community Manager
Community Manager

Hi @Mandar.Kadam,

I see you also created a Support ticket. Can you share the solution from Support here as a reply? This will help others with the same problem in the future 🙂 

0 Karma

Amit_Bisht
Explorer

Hello @Mandar.Kadam ,

Can you share the solution you got from the support?

Regards,

Amit Singh Bisht

0 Karma
Get Updates on the Splunk Community!

Splunk Observability Synthetic Monitoring - Resolved Incident on Detector Alerts

We’ve discovered a bug that affected the auto-clear of Synthetic Detectors in the Splunk Synthetic Monitoring ...

Video | Tom’s Smartness Journey Continues

Remember Splunk Community member Tom Kopchak? If you caught the first episode of our Smartness interview ...

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud?

3-2-1 Go! How Fast Can You Debug Microservices with Observability Cloud? Learn how unique features like ...