JDK-6307972 : VolanoTest server died after running for 37 hours.
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 6
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_8,solaris_10
  • CPU: sparc
  • Submitted: 2005-08-08
  • Updated: 2010-08-06
  • Resolved: 2005-09-27
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6Resolved
Related Reports
Duplicate :  
Description
In Mustang b46, the vtest server died after running for 37 hours with client VM. 
The hs_err_pid file left behind in the system is incomplete since there is no
dynamic section in the file.

# uname -a
SunOS jtg-e250-5 5.10 Generic sun4u sparc SUNW,Ultra-250

# /usr/j2se/bin/java -client -version
java version "1.6.0-ea"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-ea-b46)
Java HotSpot(TM) Client VM (build 1.6.0-ea-b46, mixed mode, sharing)

flag used: 
/usr/j2se/bin/java -client  -XX:+UseSerialGC

log file location:
/bt/VolanoTestrun.2301.-client

# /usr/j2se/bin/java ErrorID 53484152454432554E54494D450E435050024E
sharedRuntime.cpp, 590

Below is the retrace from the core

Stack trace:
current thread: t@1393972
  [1] OopMapStream::OopMapStream(0xe59fe9e4, 0xfc, 0x8, 0xfc2, 0x198,
0x18), at 0xfefc211c
  [2] OopMapSet::update_register_map(0xe59fead0, 0xfc914308, 0xe59feae0,
0x2c28b8, 0xff120000, 0x7e18e4), at 0xfedad540
  [3] frame::sender(0xe59feac0, 0xe59fead0, 0xe59feae0, 0xfc914308,
0xe59ff698, 0xff135f54), at 0xfecd96c8
  [4] VMError::report(0xe59feeac, 0x82, 0xe59fedd8, 0x0, 0xff10b6ef,
0xff1464e8), at 0xff061960
  [5] VMError::report_and_die(0xe59feeac, 0xe59feeac, 0x0, 0xfefca968,
0x4800, 0xff147498), at 0xff062508
  [6] report_fatal(0xff0e4936, 0x24e, 0xff0e4978, 0x443550, 0x0,
0xff120000), at 0xfee66d34
  [7] SharedRuntime::continuation_for_implicit_exception(0x3800,
0xff328a94, 0x0, 0x127884, 0x0, 0x0), at 0xfeff8960
  [8] JVM_handle_solaris_signal(0xb, 0xe59ff420, 0xe59ff168, 0x1,
0xca000, 0xff328a94), at 0xfedb572c
  [9] __sighndlr(0xb, 0xe59ff420, 0xe59ff168, 0xfedb51ac, 0x0, 0x1), at
0xff33c52c
  [10] call_user_handler(0xb, 0xffbffeff, 0xc, 0x0, 0xfc2e4c00,
0xe59ff168), at 0xff331998
  [11] 0x0(0x9d5, 0x13c41b8, 0xff33d9c0, 0x6638, 0xf95ff578,
0xff000001), at 0xffffffffffffffff
  [12] ObjectMonitor::exit(0x1c9f90, 0x6800, 0x686c, 0xff139bac, 0x4,
0xf95ff578), at 0xfecdf2b8
  [13] Runtime1::monitorexit(0xca000, 0xe59ff688, 0x0, 0x0, 0x0, 0x0),
at 0xfedabdb4
  [14] 0xfc855358(0xc648af18, 0xe59ff688, 0x0, 0x42, 0x28, 0xe59ff628),
at 0xfc855357
  [15] 0xfc9145e4(0xcc658050, 0xcc5f2308, 0x40, 0x390f8, 0x10,
0xffffffff), at 0xfc9145e3
  [16] 0xfc912560(0xc5ed0aa8, 0xc59d8be0, 0x0, 0x0, 0x0, 0xc5ed0be0), at
0xfc91255f
  [17] 0xfc98d87c(0xc5ed0be0, 0xc59d8978, 0xc5ed0be0, 0xc59d8be0, 0x5,
0xc5ed0be0), at 0xfc98d87b
  [18] 0xfc9cfd68(0xc5ed0b78, 0x1ffc, 0xd9015898, 0xc52ac8b0, 0x0,
0xe59ff818),at 0xfc9cfd67
  [19] 0xfc80021c(0xe59ff900, 0xe59ffb10, 0xa, 0xd9015898, 0xfc856580,
0xe59ffa58), at 0xfc80021b
  [20] JavaCalls::call_helper(0xe59ffb08, 0x475ed8, 0xe59ffa50, 0xca000,
0xd9015898, 0xe59ff8e0), at 0xfeccdea0
  [21] JavaCalls::call_virtual(0xe59ffb08, 0x6038, 0x475ee8, 0x6000,
0xe59ffa50, 0xca000), at 0xfeeab66c
  [22] JavaCalls::call_virtual(0xe59ffb08, 0xe59ffb04, 0xe59ffb00,
0xe59ffafc, 0xe59ffaf8, 0xca000), at 0xfecde764
  [23] thread_entry(0xc52ac8b0, 0xca000, 0xff1485f8, 0x441a14,
0xd9016a20, 0xff1480a8), at 0xfecde6ec
  [24] JavaThread::run(0xca000, 0x559c, 0x0, 0x5c00, 0x0, 0xff120000),
at 0xfecde598
  [25] _start(0xca000, 0x3568, 0x6400, 0x0, 0xff0d7e04, 0xff120000), at
0xfefc4df4

Comments
EVALUATION Has this bug been observed since b51? I think these volano issues with crashes with an invalid thread were all caused by bug 6317226 and should be closed as a dup of that fixed bug. If I could get another core file (I lost that last one), I would be able to check this out, but if there's another core file with this symptom then it's not fixed, is it? ----- Didn't see Volano issues after the fixes for 6317226 integrated in b51. Closed as a duplicate of that fixed bug.
27-09-2005