Splunk AppDynamics

Database Agent keep on stopping

CommunityUser
Splunk Employee
Splunk Employee

hi,

my db agent works fine for a few days then suddenly stopped. no server reboot or whatsover.

 these situation has been going about two weeks. whenever i started the agent, it will keep on running and collectors are collecting data as it should be..but after few days or so.. suddenly on the ui it shows agent stopped reporting. but when i check into the db-agent running process its still running.

the only clue that i have from the db-agent was

[AD Thread-Metric Reporter1] 23 Oct 2017 13:40:25,378 ERROR ManagedMonitorDelegate - Error reporting metrics
java.lang.OutOfMemoryError: GC overhead limit exceeded

but i have already provisioned 4gb as max heap to the agent...i dont know if that is the case..some1 help please

Labels (1)
0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Razzi,

It looks as if your GC (Garbage Collection) is the issue. I recommend looking over this doc to see if it might help you remediate the problem: https://docs.appdynamics.com/display/PRO43/Garbage+Collection

Newer version of the above Appd Docs page: https://docs.appdynamics.com/display/PRO45/Garbage+Collection#space-menu-link-content

This is also a good resource: http://www.baeldung.com/java-gc-overhead-limit-exceeded

Cody

^ Post edited by @Ryan.Paredez to add updated Docs link

0 Karma
Get Updates on the Splunk Community!

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

Splunk Enterprise Security 8.x: The Essential Upgrade for Threat Detection, ...

Watch On Demand the Tech Talk on November 6 at 11AM PT, and empower your SOC to reach new heights! Duration: ...

Splunk Observability as Code: From Zero to Dashboard

For the details on what Self-Service Observability and Observability as Code is, we have some awesome content ...