customer is running an intel server farm running Solaris 8 X86.
They started experiencing this in May.  It's progressively gotten worse.  Upto 80 outagages a month at one point.

Initially every crash ended with a truncated core file of only about 10% of what it should have been.

It was not until the use of -XX:+ShowMessageBoxOnError that we were able to collect a pstack, pmap and gcore of the failing process
A> What I see in the log file :
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Server VM (1.4.2_01-b06 mixed mode)
#
# Error ID: 53484152454432554E54494D450E435050018D
#
# Problematic Thread: prio=5 tid=0x08396a80 nid=0x25 runnable
#
Internal Error
Fatal: null exception in compiled code

Do you want to debug the problem?

All data collected is in /net/cores.ebay/cores/63833818
the cores are in the 24nov and 25nov sub directories.

interesting in the pstacks(this one is from the 25nov crash
there are several threads signitures

-----------------  lwp# 29 / thread# 28  --------------------
 dfac892c nanosleep (95a6e9d0, 95a6e9c8)
 dfb87f90 __nanosleep (64) + 58
 debced77 __1cCosOinfinite_sleep6F_v_ () + 17
 dead5697 __1cMreport_error6Fipkci11E_v_ (1, dec90008, 18d, dec647fc, dec647f0, 
95a6f35c) + 423
 dead4fc9 __1cMreport_fatal6Fpkci1E_v_ (dec90008, 18d, dec8ffe8) + 49
 de8fa3af __1cNSharedRuntimebGcompute_exception_return_address6Fi_pC_ (1) + 22d
 da034111 ???????? ()
-----------------  lwp# 30 / thread# 29  --------------------

-----------------  lwp# 45 / thread# 44  --------------------
 dfac892c nanosleep (9574e494, 9574e48c)
 dfb87f90 __nanosleep (64) + 58
 debcf817 __1cCosLmessage_box6Fpkc2_i_ (dec647fc, 9574ea00) + 56
 dead5638 __1cMreport_error6Fipkci11E_v_ (1, dec90008, 18d, dec647fc, dec647f0, 
9574f22c) + 3c4
 dead4fc9 __1cMreport_fatal6Fpkci1E_v_ (dec90008, 18d, dec8ffe8) + 49
 de8fa3af __1cNSharedRuntimebGcompute_exception_return_address6Fi_pC_ (1) + 22d
 da034111 ???????? ()
-----------------  lwp# 47 / thread# 46  --------------------


-----------------  lwp# 56 / thread# 55  --------------------
 dfac892c nanosleep (9501e890, 9501e888)
 dfb87f90 __nanosleep (64) + 58
 debced77 __1cCosOinfinite_sleep6F_v_ () + 17
 dead52af __1cMreport_error6Fipkci11E_v_ (1, dec90008, 18d, dec647fc, dec647f0, 
9501f21c) + 3b
 dead4fc9 __1cMreport_fatal6Fpkci1E_v_ (dec90008, 18d, dec8ffe8) + 49
 de8fa3af __1cNSharedRuntimebGcompute_exception_return_address6Fi_pC_ (1) + 22d
 da034111 ???????? ()
-----------------  lwp# 59 / thread# 58  --------------------

N/A

For the code generated, it appears that C2 has moved a LoadKlassNode for a dynamic object above the object's null check. The program fails since there is no exception handling for such a null exception.

 xxxxx@xxxxx  2004-03-11

The test program also fails on x86 and sparc under 1.5.0, but with a different symptom. It is not yet clear whether the base problem is the same.

 xxxxx@xxxxx  2004-03-11

With the test program, the problem also appears on 1.5.0.

The problem is a result of combination of the inlined function returning an interface type which is covered by a null check test.  

A CastPPNode is created during the parse of the ifnull bytecode.  A child CheckCastPPNode is then created by return_current() with no control edge. Finally, a LoadKlassNode is created using the CheckCastPPNode as input.

When the CastPP nodes are eliminated after the CCP pass, memory nodes (such as the LoadKlassNode) may need to inherit a control edge from their parent CastPP or CheckCastPP node.  In the bug's case, the LoadKlassNode inherited a null control edge input.  This is wrong. Under the current scheme, we need to fix MemNode::Ideal_DU_postCCP to look further up the parent chain if CheckCastPP node's control edge is null.

 xxxxx@xxxxx  2004-03-12

I have also seen this recently under Win2K Server and am 
unable to consistantly reproduce it, but it makes me a little 
nervous.

Can confirm that we are seeing this problem with 1.4.2_01
under Windows 2000 (and we just went into production with
this VM!!)

I have expreienced the same as GavinEverson under Win2K

Have Recieved the same error on Weblogic 8.1 SP2 
using 1.4.2_02-b03 on win2000 with only the following 
output:

#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Server VM (1.4.2_02-b03 
mixed mode)
#
# Error ID: 
53484152454432554E54494D450E435050018D
#
# Problematic Thread: prio=5 tid=0x5d38fd28 
nid=0xcbc runnable 
#

Heap at VM Abort:
Heap
 def new generation   total 104832K, used 21440K 
[0x10010000, 0x171d0000, 0x171d0000)
  eden space 93184K,  16% used [0x10010000, 
0x10f2a028, 0x15b10000)
  from space 11648K,  51% used [0x15b10000, 
0x160e67a8, 0x16670000)
  to   space 11648K,   0% used [0x16670000, 
0x16670000, 0x171d0000)
 tenured generation   total 932096K, used 243400K 
[0x171d0000, 0x50010000, 0x50010000)
   the space 932096K,  26% used [0x171d0000, 
0x25f82068, 0x25f82200, 0x50010000)
 compacting perm gen  total 51200K, used 51075K 
[0x50010000, 0x53210000, 0x58010000)
   the space 51200K,  99% used [0x50010000, 
0x531f0e58, 0x531f1000, 0x53210000)

We are experiencing the same problem on RedHat 
Linux Enterpise running the JBoss EJB Container. The 
error does not show itself under same load on RedHat 
Fedora Core 1.


 #
 # HotSpot Virtual Machine Error, Internal Error
 # Please report this error at
 # http://java.sun.com/cgi-bin/bugreport.cgi
 #
 # Java VM: Java HotSpot(TM) Server VM (1.4.2_03-b02 
mixed mode)
 #
 # Error ID: 
53484152454432554E54494D450E435050018D
 #
 # Problematic Thread: prio=1 tid=0x08ecd520 
nid=0x8c0 runnable
 #

 Heap at VM Abort:
 Heap
  def new generation   total 3008K, used 2429K 
[0xa6ce0000, 0xa7020000, 0xa7b10000)
   eden space 2688K,  84% used [0xa6ce0000, 
0xa6f1a930, 0xa6f80000)
   from space 320K,  45% used [0xa6fd0000, 
0xa6ff4be8, 0xa7020000)
   to   space 320K,   0% used [0xa6f80000, 0xa6f80000, 
0xa6fd0000)
  tenured generation   total 26140K, used 15770K 
[0xa7b10000, 0xa9497000, 0xaece0000)
    the space 26140K,  60% used [0xa7b10000, 
0xa8a76a00, 0xa8a76a00, 0xa9497000)
  compacting perm gen  total 16384K, used 15082K 
[0xaece0000, 0xafce0000, 0xb2ce0000)
    the space 16384K,  92% used [0xaece0000, 
0xafb9a8a0, 0xafb9aa00, 0xafce0000)

I got this one with Intel/Linux (Fedora Core 3) 1.4.2_06-b03. The fix should be in _05 according to above, I wonder if it is? Cannot reproduce yet, can try to for producing a core file.

#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Server VM (1.4.2_06-b03 mixed mode)
#
# Error ID: 53484152454432554E54494D450E435050018D
#
# Problematic Thread: prio=1 tid=0x0840df48 nid=0x21a4 runnable
#

Heap at VM Abort:
Heap
 def new generation   total 13120K, used 12151K [0xae860000, 0xaf690000, 0xb5a20000)
  eden space 11712K,  95% used [0xae860000, 0xaf347168, 0xaf3d0000)
  from space 1408K,  70% used [0xaf530000, 0xaf626b28, 0xaf690000)
  to   space 1408K,   0% used [0xaf3d0000, 0xaf3d0000, 0xaf530000)
 tenured generation   total 116544K, used 86733K [0xb5a20000, 0xbcbf0000, 0xee860000)
   the space 116544K,  74% used [0xb5a20000, 0xbaed35d8, 0xbaed3600, 0xbcbf0000) compacting perm gen  total 16384K, used 11990K [0xee860000, 0xef860000, 0xf2860000)
   the space 16384K,  73% used [0xee860000, 0xef4159e8, 0xef415a00, 0xef860000)

OK, managed to reproduce (not too difficult, it seems) and I've got a core dump. Please email me to get it...

The same error happened with j2sdk 1.4.2_07 on RH7.3.
Should I submit this as a new bug report?
This bus occurs still now with 1.4.2_07.

#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Server VM (1.4.2_07-b05 mixed mode)
#
# Error ID: 53484152454432554E54494D450E435050018D
#
# Problematic Thread: prio=1 tid=0x08f247c8 nid=0x7720 runnable
#

Heap at VM Abort:
Heap
 def new generation   total 52416K, used 30026K [0x45ae0000, 0x493c0000, 0x493c0000)
  eden space 46592K,  60% used [0x45ae0000, 0x476401e8, 0x48860000)
  from space 5824K,  34% used [0x48e10000, 0x490026f0, 0x493c0000)
  to   space 5824K,   0% used [0x48860000, 0x48860000, 0x48e10000)
 tenured generation   total 466048K, used 44182K [0x493c0000, 0x65ae0000, 0x65ae0000)
   the space 466048K,   9% used [0x493c0000, 0x4bee5828, 0x4bee5a00, 0x65ae0000) compacting perm gen  total 524288K, used 22594K [0x65ae0000, 0x85ae0000, 0x85ae0000)
   the space 524288K,   4% used [0x65ae0000, 0x670f09b0, 0x670f0a00, 0x85ae0000)

Crashes with the same  Error ID could have many different root causes. To be sure,  we would recommend that you file a new bug report at http://bugs.sun.com/services/bugreport/index.jsp  with the following information.

-SourceCode to reproduce the problem.
-Exact steps to generate the crash

If a follow up bug has been raised, can someone post the new id? I get the same issue on RH 3.0 with 1.4.2_07

What is the fix for this bug.  Please let me know where can I get the fix or solution.  

Can you please tell me if this bug is fixed in 1.4.2_09 release 
Thanks

This bug, fixed in 5.0, was backported to update releases  1.3.1_12 and 1.4.2_05.

JDK118_V3 on RHEL4 for oracle 10g
Should I submit this as a new bug report?
This bus occurs still now with 118_V3

#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Server VM 118_V3) mixed mode)
#
# Error ID: 53484152454432554E54494D450E435050018D
#
# Problematic Thread: prio=1 tid=0x08f247c8 nid=0x7720 runnable
#

Heap at VM Abort:
Heap
 def new generation   total 52416K, used 30026K [0x45ae0000, 0x493c0000, 0x493c0000)
  eden space 46592K,  60% used [0x45ae0000, 0x476401e8, 0x48860000)
  from space 5824K,  34% used [0x48e10000, 0x490026f0, 0x493c0000)
  to   space 5824K,   0% used [0x48860000, 0x48860000, 0x48e10000)
 tenured generation   total 466048K, used 44182K [0x493c0000, 0x65ae0000, 0x65ae0000)
   the space 466048K,   9% used [0x493c0000, 0x4bee5828, 0x4bee5a00, 0x65ae0000) compacting perm gen  total 524288K, used 22594K [0x65ae0000, 0x85ae0000, 0x85ae0000)
   the space 524288K,   4% used [0x65ae00


My is is satsun@stivant.com
sathish

It looks like your crash is on a 1.1.8.  Sun no longer supports that JDK. The oldest JDK supported is 1.3.1.

I see the same problem on HPUX RISC 11.11
JRE 1.4.1.07. I have all the latest patches.

Stack_Trace: error while unwinding stack
( 0)  0xc430dc68   report_error__FbPCciN22e + 0x60  [/opt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl]
( 1)  0xc430d914   report_fatal__FPCciT1e + 0x6c [/opt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl]
( 2)  0xc4622c64   compute_exception_return_address__13SharedRuntimeSFl+ 0x19c
 [/opt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl]
#
# Java version:
# Java HotSpot(TM) Server VM (mixed mode)
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error to HP customer support.
#
# Java VM: Java HotSpot(TM) Server VM (1.4.1 1.4.1.07-040312-15:24-PA_RISC2.0 PA2.0 (aCC_AP) mixed mode)
#
# Fatal: null exception in compiled code
#
# Error ID: /CLO/Components/JAVA_HOTSPOT/Src/src/share/vm/runtime/sharedRuntime.cpp, 405
#
# Problematic Thread: prio=7 tid=0x0297d710 nid=6282 lwp_id=1246927 runnable
#

This bug was not fixed in 1.4.1.  To get a 1.4 VM with this bug fixed, you should use the latest 1.4.2 release.

Since your bug is on an HP platform which is not supported by Sun, please contact HP customer support.