How to do problem determination when heap analysis shows 88% of heap used
One answer
Hi Kevin,
I'd suggest also capturing some javacore samples over a period of time while this problem is happening. Application logs will sometimes clue you in as well. I'd suggest capturing ISALite output along with the javacores and heap dump and creating a PMR so support can investigate further.
I'd suggest also capturing some javacore samples over a period of time while this problem is happening. Application logs will sometimes clue you in as well. I'd suggest capturing ISALite output along with the javacores and heap dump and creating a PMR so support can investigate further.
Comments
My 107th favorite thing to do.. This particular RTC has been so given to dumping that it is often started with dumps disabled. (https://jazz.net/forum/questions/108730/how-to-troubleshoot-birt-reports-that-consume-excessive-timecpu for example). Right after we upgraded to 4.0.5 I put a hard limit on report execution time.
For those I could definitely find a pattern; or at least find the object that owned the biggest heap segment. The last two have totally different patterns than those caused by BIRT reports and each other.