Appserver Crashed With HotSpot Virtual Machine Error : 11 # Error ID : 4F530E43505002

Technote (FAQ)
Problem
Sun Solaris 2.8
hs_err_pid29166.log
Unexpected Signal : 11 occurred at PC=0xfb9ccb24
Function name=readStringOrIndirection (compiled Java code)
Library=(N/A)

AND

#
# HotSpot Virtual Machine Error : 11
# Error ID : 4F530E43505002BD 01
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Server VM (1.3.1_05-b02 mixed mode)
Refer PMR:45143,227,000 for more details
Cause
Jit failure within the method readStringOrIndirection it's cause was with the Server JIT of 131_05.
Solution
The situation was not resolved by the signal handler. The problem has arisen through a JIT failure as the location of the problem is JITted code and an hs_err file has been thrown. Note, this file
correctly attributes the event as a signal 11.

The problem has exercised a JIT fault. Unfortunately, the pstack has little more information to
provide in context of this failure, although it does identify the fault occurred within the method readStringOrIndirection() - so no need for obtaining PrintCompilation either.

There were a number of JIT issues being experienced with the Server JIT through 131_05 until 131_08 although I believe we have gained a fair degree of stability with 131_09 and 131_10 which are technically almost identical. I understand the customer has experienced this failure only once so far: its cause was with the Server JIT of 131_05.

Given the expressed reluctance by the customer to consider use of Client JIT or set further diagnostic options, I am unclear whether the customer wishes to pursue this issue currently. A brief review of
their patches suggests they are reasonably current. Should this problem prove deterministic and cause trouble for their environment the remedy would be to adopt a more current JDK in the first instance, and nothing less than 131_09 is my recommendation.

If this is a new JIT fault (and I have little information to determine that currently) then we would have to pursue this with the current JDK 131_10.

Options:
  1. Upgrade to latest JDK
  2. Consider use of Client JIT or set further diagnostic options.











Document Information

Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Crash
Operating system(s): Solaris
Software version: 3.5, 4.0, 5.0, 5.1, 6.0
Software edition: Edition Independent
Reference #: 1178786
IBM Group: Software Group
Modified date: 2004-09-06