environment :
Apache Tomcat/6.0.18
Solaris 9 64 bit
jdk1.6.0_13

On one of the servers we are today getting constantly errors:
An unexpected error has been detected by Java Runtime Environment.
Here are some of those:

---------------------------------------------------------------------------------------
#
# An unexpected error has been detected by Java Runtime Environment:
#
#  SIGBUS (0xa) at pc=0xffffffff7f4008b8, pid=2380, tid=121
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (11.3-b02 mixed mode
solaris-sparc)
# Problematic frame:
# C  [libc_psr.so.1+0x8b8]
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid2380.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#

---------------------------------------------------------------------------------------
#
# An unexpected error has been detected by Java Runtime Environment:
#
#  SIGBUS (0xa) at pc=0xffffffff78c0bf44, pid=11205, tid=615
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (11.3-b02 mixed mode
solaris-sparc)
# Problematic frame:
# j
java.net.URLStreamHandler.parseURL(Ljava/net/URL;Ljava/lang/String;II)V+0
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid11205.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
---------------------------------------------------------------------------------------
#
# An unexpected error has been detected by Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0xffffffff7e34c17c, pid=23223, tid=5
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (11.3-b02 mixed mode
solaris-sparc)
# Problematic frame:
# V  [libjvm.so+0x74c17c]
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid23223.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
---------------------------------------------------------------------------------------
The file which should contain the logs/dump (i.e. /tmp/hs_err_pid23223.log)
are empty.
Did anybody get experienced with such a thing?
Thanks
Evgeny

Reply via email to