cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

Hi Team

sangeetha_mitta
Organizer

Could you please help on the below issue?

We have got Application out of memory incident. From the description, we could see the issue is heap size. Please suggest us how to find out the root cause for heap size and associated transactions?

Customer is more interested in knowing the transactions that are causing increase in heap size.

Thanks&Regards

@sangeetha


3 REPLIES 3

Babar_Qayyum
DynaMight Leader
DynaMight Leader

Hello @Sangeetha M.

If the incident triggered due to heap size then you should have have Leak Analysis Memory Snapshot in the Session Browser Dashboard where you can see hotspots and other information caused the memory leak.

Regards,

Babar


JamesKitson
Dynatrace Leader
Dynatrace Leader

I'd recommend following the diagnostic worfkflow described here:

https://www.dynatrace.com/support/doc/appmon/appli...

James


Hi Sangeetha,

You have to do memory analysis by following the below tutorial, this will help you in finding the issue

https://www.dynatrace.com/support/doc/appmon/short...

Note: While doing Memory Leak Analysis make sure confirming with the application team, as it suspends the application while you are performing this. I mean application will not be accessible, also you should need the Analysis server component running and connected to the AppMon server for post processing the captured data through this analysis.

Also, please go through this Online Perf Clinic - Memory Diagnostics for Java & .NET https://youtu.be/SWy83EW_xhk tutorial by @Andreas G. which is a good one to start and gives you a overview on the memory.

HTH,

Ravi