Java Solaris Communities Sun Store Join SDN My Profile Why Join?
 
Bug Database
Bug Detail
Quick Lists
Top 25 Bugs
Top 25 RFE's
Recently Closed Bugs
Printable Page Printable Page


Bug Database
Bug ID: 4736391
Votes 0
Synopsis irrecoverable stack overflow using 1.3.1)4
Category hotspot:runtime_system
Reported Against 1.3.1_04
Release Fixed
State 11-Closed, Not a Defect, bug
Priority: 2-High
Related Bugs 4298656 , 4402735 , 4736567
Submit Date 23-AUG-2002
Description
BEA has a test case they can send.  It will need weblogic server to run.

1.3.1_04  using -XX:+ShowMessageBoxOnError and heap sizes of -Xms32m -Xmx200m
Crashes with both -server and -client compilers.
other stack traces are in /net/cores.east/cores/63117078

gets the following error and then attaching dbx to the process gets the following stack trace

An irrecoverable stack overflow has occurred.
Unexpected Signal: 11
An error has just occurred, do you want to debug the problem?


from my server log, then I run dbx from another shell like following:

$ /opt/SUNWspro/bin/dbx 
/home/ytian/jdk/j2sdk1_3_1_04/bin/sparc/native_threads/java 6614
changes (topic)
The major new features of this release relative to 6.1 are:

o The dbx environment variable "rtc_use_traps" has been removed.
   Traps are used automatically as long as the hardware is UltraSparc.
o There is now some basic support for looking at core files from
   different versions of Solaris. See `help core mismatch' for details.
o Stepping to a specific function support. See `help step to' for details.
o Fortran intrinsics support on  customer  has been removed.
o Dbx automatically translates some old dbxenv variables to their new
   names. See `help dbxenv' for details.
o The default command-line editing mode is now emacs. See "How do I enable
   command-line editing?" in FAQ for details (`help FAQ').
o Two new collector commands have been implemented: `pause' and `resume'.
   See `help collector' for details.
o The collector enable_once command has been removed.
o The collector store command has been extended to include experiment groups.

See also `help changes61'


To suppress this message, add the following line to your .dbxrc file:

         dbxenv suppress_startup_message 6.2
Reading java
Reading ld.so.1
Reading libthread.so.1
Reading libdl.so.1
Reading libc.so.1
Reading libc_psr.so.1
Reading libjvm.so
Reading libCrun.so.1
Reading libsocket.so.1
Reading libnsl.so.1
Reading libm.so.1
Reading libw.so.1
Reading libmp.so.2
Reading librt.so.1
Reading libaio.so.1
Reading libhpi.so
Reading libverify.so
Reading libjava.so
Reading libzip.so
Reading libnet.so
Reading libioser12.so
Reading nss_nis.so.1
Reading libmuxer.so
detected a multithreaded program
Attached to process 6614 with 79 LWPs
  xxxxx@xxxxx   (  xxxxx@xxxxx  ) stopped in __lwp_park at 0xff374a74
0xff374a74: __lwp_park+0x0010:  ta      0x8
(/opt/SUNWspro/bin/../WS6U2/bin/sparcv9/dbx) where
current thread:   xxxxx@xxxxx  
=>[1] __lwp_park(0x0, 0x0, 0x0, 0x1, 0xfe98ccc0, 0x298d0), at 0xff374a74
   [2] cond_wait_queue(0x1, 0x298b8, 0x0, 0xfe98ccc0, 0x0, 0xff386000), at 
0xff372448
   [3] cond_wait(0x298d0, 0x298b8, 0x298d0, 0x0, 0xe92c0, 0x0), at 0xff372bcc
   [4] ObjectMonitor::wait(0xff132dbc, 0x298d0, 0x298b8, 0xff146be8, 
0xff0ce000, 0xe92c0), at 0xfedf9dd4
   [5] ObjectSynchronizer::wait(0xffbee8dc, 0x0, 0xff0ce000, 0x28e98, 0x0, 
0xffbee53c), at 0xfedf9804
   [6] JVM_MonitorWait(0xff0e4960, 0x0, 0x0, 0xeccca070, 0x28e98, 
0xffbee9d4), at 0xfedfa32c
   [7] 0x8f244(0xffbee9d4, 0x0, 0xffbeea54, 0x0, 0x0, 0x109a0), at 0x8f243
   [8] 0x8c3ac(0xffbeea54, 0xffbeec70, 0x28e98, 0x97e54, 0xc, 0xffbee970), 
at 0x8c3ab
   [9] 0x8c3ac(0xffbeeaec, 0xffbeec70, 0x28e98, 0x95a80, 0x4, 0xffbee9f0), 
at 0x8c3ab
   [10] 0x8c3ac(0xffbeeb84, 0xffbeec70, 0x28e98, 0x95a80, 0x4, 0xffbeea80), 
at 0x8c3ab
   [11] 0x8c3d0(0xffbeec04, 0x1, 0xff0dca68, 0x95c30, 0x4, 0xffbeeb20), at 
0x8c3cf
   [12] 0xff138048(0xffbeec90, 0xffbeee90, 0xa, 0xf74d6e00, 0x4, 
0xffbeeba8), at 0xff138047
   [13] JavaCalls::call_helper(0xffbeee88, 0xff0ce000, 0xffbeedbc, 0x28e98, 
0x8e1fc, 0xffbeee90), at 0xfeccd0c8
   [14] JavaCalls::call(0xffbeee88, 0xffbeed9c, 0xffbeedbc, 0x28e98, 
0x28e98, 0xffbeed34), at 0xfed75aec
   [15] jni_invoke(0x1, 0x28e98, 0x0, 0x0, 0x27f18, 0xffbeee6c), at 0xfedd6820
   [16] jni_CallStaticVoidMethod(0xff0ce000, 0x28e98, 0x27f18, 0x28f24, 
0xffbeeef0, 0x28e98), at 0xfee3f02c
   [17] main(0x28f24, 0x0, 0x28f24, 0xffbefbe6, 0x0, 0x254c4), at 0x1212c
Work Around
To find out the java stack try:
java_g -Xint -verbose:class -XX:-UseStackBanging -XX:+UseBoundThreads  
-XX:+OverrideDefaultLibthread -XX:AltStackSize=64k

  xxxxx@xxxxx   2002-08-29
Evaluation
Could be related to 4736567, This is a JPSE issue, will continue to track this one.
  xxxxx@xxxxx   2002-08-26


  xxxxx@xxxxx   2002-09-18
Esc. were closed as user error, closing bug as well.
Comments
  
  Include a link with my name & email   


PLEASE NOTE: JDK6 is formerly known as Project Mustang