Collector Heap Memory Usage and Class Cache
One of our collectors' memory usage always trigger the diable new agents instrument alert. From dynatrace selef-monitoring, we can find the memory heap utilization is between 80% to 90%. We have 860MB class cache and 2GB memory heap. The question is what else are using collecotor memory beside class cache?
Thanks
YC
What version of DT? There's a fix for a similar pattern in 6.2.2
Hi Richard,
Thank you for promoted reply. We are using 6.1.0.8305. Do you mean that's a known issue?
Thanks
YC
Hm, I think the issue happened only in 6.2 so that may not be your issue. Depending on number of agents you may want/need to increase the heap size if you can. Consider opening a support ticket
Best Answer
This is a known issue at least in 6.2 and fixed in 6.2.2 update. From the release notes:
- JLT-133458: High Collector memory usage due to incorrect cache sizing
- Impact: Collector uses too much memory, which might cause Agents to be declined
- Cause: Wrong debug flag constant was used for cache sizing
- Solution: Using correct debug flag now
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 
