Java Virtual Machine (JVM) - HotSpot Virtual Machine crash

[atouloupis]

Hello all,

We have an HP-UX meprod1 B.11.23 U 9000/800 64 bit O.S. with 1.5.0.02 Java version.

Today our production application crushed and the JVM produced a log saying the following:

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (11) at pc=c0184770, pid=7141, tid=144
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0.02 jinteg:10.14.05-17:07 PA2.0 (aCC_AP) mixed mode)
# Problematic frame:
# C [libc.2+0x84770]

Some extra system info:

meprod1 97: uname -r
B.11.23

meprod1 109: /opt/mediation/java/jre1.5.0_02/bin/java -version
java version "1.5.0.02"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0.02-_14_oct_2005_17_51)
Java HotSpot(TM) Server VM (build 1.5.0.02 jinteg:10.14.05-17:07 PA2.0 (aCC_AP), mixed mode)

meprod1 99: /usr/sbin/swlist | grep -e QPK -e GOLD -e BUNDLE11i
BUNDLE11i B.11.23.0409.3 Required Patch Bundle for HP-UX 11i v2 (B.11.23), September 2004
QPKAPPS B.11.23.0609.053a Applications Quality Pack Bundle for HP-UX 11i v2, September 2006
QPKBASE B.11.23.0706.064 Base Quality Pack Bundle for HP-UX 11i v2, June 2007



How would you suggest to handle this? Is it a JVM bug or could it be an O.S. problem?

thank you in advance,
Alex

[Steven E. Protter · Accepted solution]

Shalom Alex,

Java is quite out of date.

http://www.hp.com/go/java

Get and install a supported, current release.

SEP

[atouloupis]

Thank you Steven for the quick reply.
I would like if possible to verify that it is a known bug that is fixed in a newer version.

Can you advice me a page with changelogs between the java version we have currently installed and the latest one?

Although i suspect our problem has to do with a missing system patch as it is mentioned in here http://docs.hp.com/en/HPUXJAVAPATCHES/index.html

Thank you

[Pete Randall]

It would be nearly impossible to say for sure that it was the O.S. or JVM, but the fact that your O.S. is relatively current while your JVM is some 4 years old would lead most to the conclusion that Java was the problem. The fact that it was a SIGSEGV fault would also lead me to suspect Java rather than the O.S.


Pete