Massive Java Crashes – Temp server in place

Guys, we had massive java crashes over the course of the day and I have no idea what is happening. I first rebooted the machine, undid some changes in the hope it would fix something, and it worked for 2 hours or so and then crashed again several times. I have upgraded a couple of things but I cannot trace the issue. I got a [Too many errors] on the console as well as the crash report from java at times:

# A fatal error has been detected by the Java Runtime Environment:
#  SIGSEGV (0xb) at pc=0x00000007f8327c00, pid=32641, tid=140230393620224
# JRE version: 6.0_22-b22
# Java VM: OpenJDK 64-Bit Server VM (20.0-b11 mixed mode linux-amd64 compressed oops)
# Derivative: IcedTea6 1.10.6
# Distribution: CentOS release 6.2 (Final), package rhel-
# Problematic frame:
# C  0x00000007f8327c00
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:

with different contents in “Problematic frame”. This is quite a serious issue that is why I have created a new, temp bukkit server and will now see how I can add plugins one by one and see if it works. So until then the normal server will be frozen. Unfortunately this comes at the worst of times since I will be leaving for a trip tonight for 2 weeks. I will see how much I can fix during the trip, but it looks like we will have to live with a not-fully operational server for some days. If you have any ideas how to debug something like this, please let me know. All help greatly appreciated.

5 thoughts on “Massive Java Crashes – Temp server in place

    • I don’t think that has anything to do with it, as it is an incompatibility with a video card driver and the lwjgl version of OpenGL. Since the Minecraft server doesn’t use OpenGL, that is highly unlikely to be causing the error.

  1. Just a suggestion, I have no idea if it could be bad in any way or if it has anything to do with the error.
    You appear to be using OpenJDK 6. Maybe a plugin has been updated and now requires Java 7. Maybe you can try if installing Java 7 fixes the error?

Comments are closed.