I had been consistently facing the standard “An unexpected error has been detected by HotSpot Virtual Machine”. I spent some time trying to figure out the root cause of the problem. I was not able to make any headway for some days.
Yesterday google search provided me with the answer. Added the following JVM option
-Djava.net.preferIPv4Stack=true
And presto the JVM crashes ceased. The above mentioned thread mentions that the Inet4AddressImpl is not thread-safe. If you thought the Sun guys were GODS, you must be mistaken. They are just mere mortals like us.
5 responses so far ↓
James DeMichele // June 25, 2008 at 3:12 am |
Could you please add which version of Java that you were using when you made this fix? Thanks.
Mr. President // June 25, 2008 at 4:20 am |
I do not remember the exact version but I believe it was JDK 1.5.02.
Lyn // November 18, 2008 at 11:54 am |
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xaa6dff1d, pid=8021, tid=3073497856
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_18-b06 mixed mode)
# Problematic frame:
# C [libawt.so+0x225f1d] _XmAddHashEntry+0×15
Spoko // February 10, 2009 at 9:22 am |
Holla
After I have ran this command I get this error.
root@lenovo-desktop:/opt/sakai-release/sakai-src-2.5.3# mvn clean install sakai:deploy
[INFO] Scanning for projects…
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xb782dea6, pid=7005, tid=2990836624
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_14-b03 mixed mode, sharing)
# Problematic frame:
# V [libjvm.so+0x159ea6]
#
# An error report file with more information is saved as hs_err_pid7005.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#
Aborted
How can I fix this I have tried -Djava.net.preferIPv4Stack=true but it seem not to work.
Mr. President // February 12, 2009 at 2:38 pm |
Sorry Spoko for the delay in response. Unfortunately “an unexpected error” is the most common and the least explained error message. Only trail and error works in getting a solution. The closest is to lookup the troubleshooting guides and hope for success. Here are the links
http://java.sun.com/j2se/1.5/pdf/jdk50_ts_guide.pdf
http://java.sun.com/javase/6/webnotes/trouble/TSG-VM/TSG-VM.pdf
Hope this helps.