I have seen that a few other posts asking about JVM crashes with EXCEPTION_ACCESS_VIOLATION have got no response, but hope that this post will trigger one.....
We recently experienced two JVM crashes in quick succession on a production system running 32-bit server JVM 1.6.0_01 on Windows 2003 Server. The immediate cause for this seems to have been the attempt to upload a rather large PPT file (45 MB) through the application - in itself, this should not be a problem since it is a fairly common occurrence in the application (and has never caused a crash for over a year that this JVM has been used) and the same file seems to have been uploaded successfully a short while later.
I have seen a few bugs filed for this (5040096, 5062728) that talk about it being related to a mismatch in exception handling between the JVM and Windows 2003, but they were all supposedly fixed prior to 1.6, so I am a little puzzled - can anybody shed any light on the matter?
# An unexpected error has been detected by Java Runtime Environment:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x7c82be5e, pid=1340, tid=10468
# Java VM: Java HotSpot(TM) Server VM (1.6.0_01-b06 mixed mode)
# Problematic frame:
# C [ntdll.dll+0x2be5e]
# If you would like to submit a bug report, please visit:
--------------- T H R E A D ---------------
Current thread (0x4dbdf400): JavaThread "web-7503" [_thread_in_native, id=10468]
I am sure, I will be able to help you if you can provide me more details about the machine setup. Like what is the RAM, is it windows 2003 Standards or Windows 2003 Enterprise. In short details for the machine
Now coming to JVM. What is the JVM options you are using, is the JVM crash having a pattern or is it happening randomly. What is the load on the box when this happens. Is the app CPU intensive or RAM intensive.