We had our second freeze for today. Without warning, Wildfire 3.2.2 stops doing anything. When trying to create a stackdump with kill -3, we get a dump full of this:
Error occurred during stack walking: sun.jvm.hotspot.utilities.AssertionFailure: Only used on C2 x86 at sun.jvm.hotspot.utilities.Assert.that(Assert.java:15) at sun.jvm.hotspot.code.CodeBlob.getLinkOffset(CodeBlob.java:193) at sun.jvm.hotspot.runtime.amd64.AMD64Frame.senderForCompiledFrame(AMD64Frame.java:297) at sun.jvm.hotspot.runtime.amd64.AMD64Frame.sender(AMD64Frame.java:213) at sun.jvm.hotspot.runtime.Frame.sender(Frame.java:184) at sun.jvm.hotspot.runtime.Frame.realSender(Frame.java:191) at sun.jvm.hotspot.runtime.VFrame.sender(VFrame.java:102) at sun.jvm.hotspot.runtime.VFrame.javaSender(VFrame.java:129) at sun.jvm.hotspot.tools.StackTrace.run(StackTrace.java:50) at sun.jvm.hotspot.tools.JStack.run(JStack.java:41) at sun.jvm.hotspot.tools.Tool.start(Tool.java:204) at sun.jvm.hotspot.tools.JStack.main(JStack.java:58)
The entire dump is attached to this comment.
Killing Wildfire required a kill -9, as the -6 that I usually use didn’'t do anything.
Does anyone have any idea what might cause the JVM to freeze like this? We didn’'t change anything on the running configuration of the server in the last week. Why did it start freezing on us since this morning then?
Message was edited by: Guus (Stackdump removed, see next post)