JDK-6807420 : Regular java flow causes JVM to crash on SIGSEGV in Solaris 10
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 5.0u17
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_10
  • CPU: x86
  • Submitted: 2009-02-19
  • Updated: 2011-02-16
  • Resolved: 2009-08-31
Related Reports
Duplicate :  
Description
FULL PRODUCT VERSION :
java version "1.5.0_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_17-b04)
Java HotSpot(TM) Server VM (build 1.5.0_17-b04, mixed mode)

FULL OS VERSION :
SunOS SH-T2000-0UW 5.10 Generic_137137-09 sun4v sparc SUNW,Sun-Fire-T200

EXTRA RELEVANT SYSTEM CONFIGURATION :
The Java process is launched as following:
javabin -DSHVER=1.3,11 -Xdebug -Xrunjdwp:transport=dt_socket,address=60011,suspend=n,server=y -Xms4096m -Xmx4096m -server -d64 -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:ParallelGCThreads=12 -XX:
LargePageSizeInBytes=256m -XX:NewRatio=2 -XX:NewSize=1m -XX:MaxNewSize=10g -XX:SurvivorRatio=16 -XX:PermSize=256m -XX:MaxPermSize=256m -verbose:gc -XX:MaxPermSize=256m -Dos.phys.mem=31.9G -Dos.heap
.max=4096m -Dcmp.home=/export/home/ana41 -DREGISTRY_PATH=./registry -Djava.security.auth.login.config=/export/home/ana41/jboss/client/auth.conf -Djavax.net.ssl.trustStore=/export/home/ana41/Main/Tr
uststore/ejb3.truststore -Djavax.net.ssl.trustStorePassword=admin123 -DREGISTRY_DEBUG=false com.cisco.nm.cmp.system.os.AVM 11


A DESCRIPTION OF THE PROBLEM :
While running stress tests, one of the  java process crashes while handling alarms. The code in question creates lists, adds object ,converts lists to arrays and vice versa and executes queries against the DB (select, delete, insert)

We have been encountering java crashes on different JVMs in our system,
about 3-4 time a night, since we've upgraded to 1.5.0_17-b04. Each crash
is of type  SIGSEGV and occurs on one of the CompilerThreads.
The 'Current CompileTask' differs from JVM to JVM. 1. #
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGSEGV (0xb) at pc=0xfe8f6e40, pid=14015, tid=20
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0_17-b04 mixed mode)
# Problematic frame:
# V  [libjvm.so+0xf6e40]
#
Current thread (0x0022f220):  JavaThread "CompilerThread1" daemon
[_thread_in_native, id=20]
Current CompileTask:
opto: 19% !
com.cisco.nm.cmp.vne.vendor.cisco_sh.router.command.parser.iosxr.CiscoIO
SXRParsingTool.checkDeviceResponseError(Ljava/lang/String;Ljava/lang/Str
ing;)Z @ 173 (257 bytes)

========================================================================
=======================
2.
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGSEGV (0xb) at pc=0xffffffff7e30bd24, pid=20263, tid=23
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_17-b04 mixed mode)
# Problematic frame:
# V  [libjvm.so+0x30bd24]
#
Current thread (0x0000000100546cd0):  JavaThread "CompilerThread0"
daemon [_thread_in_native, id=23]
Current CompileTask:
opto:180% !
com.cisco.nm.cmp.gw.plugin.alarm.commands.ForceClear$ClearAlarmState.han
dle(Lcom/cisco/nm/cmp/system/transport/XMessage;)Lcom/cisco/nm/cmp/frame
work/commands/MultiStateCommand$StateHa
ndler; @ 657 (1066 bytes)

========================================================================
======================
3.
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGSEGV (0xb) at pc=0xfe8f6e40, pid=2530, tid=19
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0_17-b04 mixed mode)
# Problematic frame:
# V  [libjvm.so+0xf6e40]
#
Current thread (0x00222820):  JavaThread "CompilerThread0" daemon
[_thread_in_native, id=19]
Current CompileTask:
opto:413% !
com.cisco.nm.cmp.vne.framework.da.InvestigationProgressManager.logInvest
igationResult()V @ 470 (817 bytes)

========================================================================
======================


THE PROBLEM WAS REPRODUCIBLE WITH -Xint FLAG: Did not try

THE PROBLEM WAS REPRODUCIBLE WITH -server FLAG: Yes

ERROR MESSAGES/STACK TRACES THAT OCCUR :
Attached seperatly

REPRODUCIBILITY :
This bug can be reproduced often.

Release Regression From : 5.0u16
The above release value was the last known release where this 
bug was not reproducible. Since then there has been a regression.

Comments
EVALUATION This is a 1.5 issue so reassigning to sustaining. The crash log decodes to a crash in PhaseChaitin::Split so it's possible this is the same as 6754146 which is fixed in 6u18-rev and 6u19.
31-03-2009