![]() to 1GB, to wait for the issue to reproduce. ![]() ![]() Hence sometimes we recommend temporally decreasing the max heap size, e.g. just to exchange and to open in various analysis tools. We could check this by comparing a couple of thread dump files also found in LogGrabber.īTW, please be noted that practically speaking, it is not very easy to handle dump file around the size of 8GB, i.e. This scenario could also consume the heap memory in the longer run, especially if there are any slow/stuck/blocked/dead-lock threads.Į.g. In addition, it may be worth checking if we see any increase in the number of thread or not, as thread also consumes JVM heap memory.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |