stack trace is missing in JIFA reports

[nikhildongre]

Hi Team,

In MAT report under leak suspect we can see strack trace but same we cannot see under JIFA leak suspect. And we can see JIFA has only 2 Problems suspects but MAT has generated 4 problems suspects.

JIFA report :------------ Problem Suspect 1 Description 1,051,665 instances of glog.business.shipment.TShipment, loaded by weblogic.utils.classloaders.GenericClassLoader @ 0x1c831fee8 occupy 7,047,994,256 (33.10%) bytes. Keywords

glog.business.shipment.TShipment weblogic.utils.classloaders.GenericClassLoader @ 0x1c831fee8 Problem Suspect 2 Description 2,103,246 instances of glog.business.shipment.TShipmentStop, loaded by weblogic.utils.classloaders.GenericClassLoader @ 0x1c831fee8 occupy 4,180,086,864 (19.63%) bytes. Keywords

glog.business.shipment.TShipmentStop weblogic.utils.classloaders.GenericClassLoader @ 0x1c831fee8

MAT REPORT :-------------------

Problem Suspect 1 The thread weblogic.work.ExecuteThread @ 0x1cb167bd8 [STUCK] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)' keeps local variables with total size 4,998,565,640 (23.57%) bytes.

The memory is accumulated in one instance of "weblogic.work.ExecuteThread" loaded by "com.oracle.classloader.weblogic.LaunchClassLoader @ 0x1c000df80". PSR Summary Request Details

The stacktrace of this Thread is available. See stacktrace.

Keywords com.oracle.classloader.weblogic.LaunchClassLoader @ 0x1c000df80 weblogic.work.ExecuteThread PSR Thread Details Available

PSR Section - Leak Suspects PSR Suspect resolveByClass weblogic.work.ExecuteThread for "weblogic.work.ExecuteThread" PSR Suspect resolveByClassLoader weblogic.utils.classloaders.GenericClassLoader @ 0x1c00151f0 for "weblogic.utils.classloaders.GenericClassLoader @ 0x1c00151f0" Details » Problem Suspect 2 The thread weblogic.work.ExecuteThread @ 0x1c16c37c0 [STUCK] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)' keeps local variables with total size 3,982,750,480 (18.78%) bytes.

The memory is accumulated in one instance of "weblogic.work.ExecuteThread" loaded by "com.oracle.classloader.weblogic.LaunchClassLoader @ 0x1c000df80". PSR Summary Request Details

The stacktrace of this Thread is available. See stacktrace.

Keywords com.oracle.classloader.weblogic.LaunchClassLoader @ 0x1c000df80 weblogic.work.ExecuteThread PSR Thread Details Available

PSR Section - Leak Suspects PSR Suspect resolveByClass weblogic.work.ExecuteThread for "weblogic.work.ExecuteThread" PSR Suspect resolveByClassLoader weblogic.utils.classloaders.GenericClassLoader @ 0x1c00151f0 for "weblogic.utils.classloaders.GenericClassLoader @ 0x1c00151f0" Details » Problem Suspect 3 The thread weblogic.work.ExecuteThread @ 0x1cb1671d8 [STUCK] ExecuteThread: '15' for queue: 'weblogic.kernel.Default (self-tuning)' keeps local variables with total size 3,604,046,896 (16.99%) bytes.

The memory is accumulated in one instance of "weblogic.work.ExecuteThread" loaded by "com.oracle.classloader.weblogic.LaunchClassLoader @ 0x1c000df80". PSR Summary Request Details

The stacktrace of this Thread is available. See stacktrace.

Keywords com.oracle.classloader.weblogic.LaunchClassLoader @ 0x1c000df80 weblogic.work.ExecuteThread PSR Thread Details Available

PSR Section - Leak Suspects PSR Suspect resolveByClass weblogic.work.ExecuteThread for "weblogic.work.ExecuteThread" PSR Suspect resolveByClassLoader weblogic.utils.classloaders.GenericClassLoader @ 0x1c00151f0 for "weblogic.utils.classloaders.GenericClassLoader @ 0x1c00151f0"

And