« November 2009
SunMonTueWedThuFriSat
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
     
       
Today
XML

Blog::Navigation

GetJava Download Button
Get the Source
Personal Blog

Blog::Referers

Today's Page Hits: 599

Powered by Roller Weblogger.
« Permanent generation... | Main | jhat throws OOM! »
20051006 Thursday October 06, 2005

Does jhat work for heap dumps produced from earlier JDKs?

Short answer: Yes. Mustang's jhat works against heap dumps produced from earlier JDKs as well. It just works -- because it uses the same HPROF binary file format as used by hprof profiler and jmap tool. jmap tool can dump from live Java processes and Java core dumps. This feature has been backported to 1.4.2_09 (solaris only) and 5.0 update 5 (solaris and linux only) releases. hprof produces heap dump with allocation site trace information in the same format -- you need to use format=b option with hprof. As you'd probably know, hprof prodifier has been existing in JDK for quite some time.

And yes, HPROF binary file format is platform independent. Therefore jhat on any platform can parse and view heap dumps produced from any platform



( Oct 06 2005, 07:44:42 PM IST ) Permalink Comments [2] del.icio.us | furl | simpy | slashdot | technorati | digg

Comments:

jhat can be extremely useful for diagnosing OutOfMemoryError issues in application servers. I've used it with weblogic 8.1 to confirm an OOM bug on a 1Gb heap. Having Solaris 10 running on a 24Gb AMD64 v40z with jhat in 64-bit helps to deal with large heap dumps.

Posted by Philippe Lantin on October 14, 2005 at 10:11 PM IST #

I can't seem to get JHat (Windows, Mustang 70) to read the heap.bin files generated by jmap (Linux, 1.5.0_05). It complains about the dreaded magic number.

Posted by 208.51.58.30 on February 09, 2006 at 03:19 AM IST #

Post a Comment:

Comments are closed for this entry.
Copyright (C) 2005, A. Sundararajan's Weblog