21 Mar 2023 04:18 AM
Hi,
We're currently troubleshooting memory leak (gradually increased over days) everytime OneAgent is installed in our Java server.
We have narrowed down the issue by updating to the latest OneAgent version, downloading support archive dump files, disabling full stack monitoring, deep monitoring, checking for bugs in certain Java version, NMT output from when the problem occurs, and came into conclusion that the leak occuring in the native memory.
Then we were using oneagentdumpproc command to dump the native process however still couldn't find the issue.
Developer suggested to disable the feature allocation profiling, as we still have it enabled from the log.
2023-02-08 01:40:15.595 UTC [000032c6] info [native] AllocationProfiling: enabled=Y
I'm not familiar with Java, could anyone give insight/resources on how this can be done? Checking on the command and Dynatrace no such options.
In addition they also suggested to replace the garbage collector from Shenandoah to G1, not sure how this is related. If anyone has suggestion on how to troubleshoot would be helpful.
Thank you.
Solved! Go to Solution.
21 Mar 2023 06:01 AM
Hello @Ardhi
You can disable continuous memory profiling from the OneAgent features globally or can override on the particular process level.
Regards,
Babar
22 Mar 2023 09:03 AM
thank you. It's too bad we can turn it off on host level