Then you could maybe define a free ratio on the metaspace so that always enough space for new classes is available and no resizing will be needed in critical situations. So what's the equivalent replacement for it The application has a heap of 8gb and creates a lot of short living objects I noticed that it often paused for some seconds to do garbage collection Unable to negotiate with xx.xx.xx.xx port 1234 Unfortunately (and in spite of the disclaimers in the documentation), many developers decide they know better than the jvm when to collect memory and introduce exactly this type of issue
Since we are getting java.lang.outofmemoryerror Since these parameters are not duplicated, why start with so many different prefix My guess is there are some kind of standards for this The segmented hprof dump format is required to correctly generate heap dumps containing more than 4 gb of data. This is the option that can be used for the case mentioned in the question
OPEN
