I'd say probably before going too deep, I would just use the verbose:gc option piped into a log file so it can be further analyzed.
It should show a memory increase to confirm. Also when it gets slow, probably a jstack could also help to see where the threads are. As for the head dump, I also use jvisualvm. JMC is now available for free in OpenJDK (I believe) and might be helpful. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Wed, Dec 26, 2018 at 11:23 AM Bruno Baptista <bruno...@gmail.com> wrote: > Thant's interesting Matthew. > > Usually I open those in jvisualvm. I go to classes and activate the > retained column. > > That column will calculate the retained (effective) memory usage by class. > > Usually it takes a while to calculate, that's why it's not on by default. > > Cheers > > Bruno Baptista > https://twitter.com/brunobat_ > > > On 26/12/18 09:28, Matthew Broadhead wrote: > > TomEE 7.0.5 plus > > > > i had a recent memory leak which was stalling the server every couple > > of days. so i did a heap dump and solved that problem. > > > > then i decided to do another heap dump because the server is running > > pretty slowly. each page is taking a few seconds to load on a 32GB > > system. (i did clear out work directory) > > > > it turns out that more than half of the memory is consumed with > > org.apache.bval.cdi.BValExtension. is this fairly normal? using > > Eclipse Memory Analyser i have dug into shortest routes to GC root but > > i don't find any of my objects listed there. mostly BVal stuff. are > > there any tips for debugging heap dumps? >
