cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

Memory Leak Analysis quetion

John_Kelly2
Organizer

All,

We attempted to run a memory leak analysis on an agent of an application running under websphere and the IBM JVM.   As we understand it this would stall the application but not shutdown or restart the jvm?  This happened twice the afternoon but we are just wondering if it could be a coincidence or not?

  

2 REPLIES 2

florent_duchate
Dynatrace Pro
Dynatrace Pro

Hi John

Deep memory analysis is very disruptive indeed. The bigger the heap the longer it will take. It is quite likely that by pausing the jvm during the acquisition of the dump, websphere thought that it had become unresponsive and decided to restart the process. I'm not familiar with websphere but weblogic which is quite similar has a process (node manager) which will monitor the jvm and restart automatically if the jvm doesn't respond.

Please note that a deep memory analysis will be triggered automatically in the case of an out of memory error anyway. The view is that at that point the VM is dead anyway so slowing it down further wouldn't make it worse...

Regards

 

Flo

kevin_jackson2
Inactive

John-

I would also suggest looking at the WebSphere log files to see if there is any indication as to why the JVM shutdown.  Also, depending on the IBM JDK version being used, there are some known issues regarding memory dumps.  Take a look at the link below to check for the JDK version your customer is using.  If all else fails, I would open a support ticket.

KB-327 Issues with JVM versions, options and parametersT

Thanks,

Kevin