JDK-6517886 : Core file for analysis
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 5.0u8
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_8
  • CPU: sparc
  • Submitted: 2007-01-26
  • Updated: 2010-08-18
  • Resolved: 2007-02-01
Related Reports
Duplicate :  
Description
This is regarding an urgent issue from customer.
They have a production issue which they have reported to us and have given the core file and stdout file for analysis.
Here are files :
1) /net/cores.central/cores/dir33/CBOE/cboe_core.29381.Z
2) /net/cores.central/cores/dir33/CBOE/PID_29831.EquityTradeServer1.out.01-25-07.100230.gz

Customer needs analysis from memory perspective to provide the memory histogram.
This core was produced by a process running JDK 1.5.0_08 on Solaris 8.
The file which is the stdout for the application has also been obtained from them.
Filename : PID_29831.EquityTradeServer1.out.01-25-07.100230.gz, as mentioned above.

Customer tried to run JMAP themselves, but could not succeed and got the below exception :

Exception in thread "main" java.lang.OutOfMemoryError: requested 4096 bytes for jbyte in /BUILD_AREA/jdk1.5.0_08/hotspot/src/share/vm/prims/jni.cpp. Out of swap space?

Hence customer needs our assistance to provide them memory histogram analysis out of core file.

Comments
EVALUATION Core file in question is from an i86pc, not sparc. I think the problem reported here is that jmap, on a heap of this size (2675MB CMS generation), will fail due to memory exhaustion. This is already documented in CR 6494472 (jmap -heap and jmap -permstat both require a large amount of memory). e.g. ----------------------------------------------------------------- . . concurrent mark-sweep generation: capacity = 2804940800 (2675.0MB) used = 2511204392 (2394.8711318969727MB) Exception in thread "main" java.lang.OutOfMemoryError: requested 4096 bytes for jbyte in /BUILD_AREA/jdk1.5.0_08/hotspot/src/share/vm/prims/jni.cpp. Out of swap space? ----------------------------------------------------------------- Our internal SA tool jhistoproc.sh fails in the same way. (jmap -dump and using HAT to analyse is suggested in 6494472, although that will require JDK6) EDIT: correction: jmap -heap:format=b java corefile ...would dump the Java heap in 5.0. However, this also has a large memory overhead for such 2.6GB heap corefiles and fails. In the error above, native C heap is the problem: but trying lower and LOWER Java heap sizes with jmap -J-Xmx look likely to work in some cases, but do not solve the problem here.
31-01-2007