Java 5 crashes - the workaround

As announced I let the machine run till today - with no more crashes. The distributed GC interval was set to 4 hours. I believe we will be able to use this workaround in our production environments. Later this year we may upgrade to Java 6 which did not show the erratic behavior. Moreover, as we do not really know which combination of individual factors cause the bug to surface at all, we cannot even know for sure if there is a hardware configuration out in the field which would fail in the first place.

Nevertheless, thanks for all the input and suggestions. As a roundup I will just let the machine run memtest86 for some time to make sure this is not a memory problem. However I do not believe it will show any problems for reasons stated earlier.


Anonymous said…
Hi Daniel,
I am seeing the same crash on two servers entirely intermittent.

# An unexpected error has been detected by HotSpot Virtual Machine:
# SIGSEGV (0xb) at pc=0xb6c7542f, pid=26677, tid=1565014960
# Java VM: Java HotSpot(TM) Server VM (1.5.0_09-b01 mixed mode)
# Problematic frame:
# V []

and wondered what your resolution was?

unagicat at yahoo dot com

As I said, we do not really know what was the deciding factor. The distributed GC parameter change (see previous posts) seems to have been it.
However just to be sure we replaced the offending machine.


Popular posts from this blog

SAXParseException: -1:-1: Premature End Of File - Misleading error

Amiga 500 Restoration: A501 Memory Expansion

Amiga 500 Restoration: Mouse and Mainboard Maintenance