EXCEPTION_ACCESS_VIOLATION

[praveen vempati]

Hi Ranchers,
We are getting the following exception when we run our multi Threaded Application. We could not the reason why this error comes. The following is the error dump. My question is what might be the reason for this error?
*****************************Dump Start******************************
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d707ba1, pid=1056, tid=428
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_05-b05 mixed mode, sharing)
# Problematic frame:
# V [jvm.dll+0xc7ba1]
#

--------------- T H R E A D ---------------

Current thread (0x00987c98): VMThread [id=428]

siginfo: ExceptionCode=0xc0000005, reading address 0x00000660

Registers:
EAX=0x00020000, EBX=0x00000000, ECX=0x00000660, EDX=0x00020000
ESP=0x02d3fbe4, EBP=0x02d3fc20, ESI=0x2b2b0280, EDI=0x6d7adcd0
EIP=0x6d707ba1, EFLAGS=0x00010216

Top of Stack: (sp=0x02d3fbe4)
0x02d3fbe4: 00020000 6d707b6a 6d7adcd0 6d707dc5
0x02d3fbf4: 6d7b20a8 6d74b372 6d7b20a8 6d7adcd0
0x02d3fc04: 0098ecf0 6d6ad7b5 6d7adcd0 00000000
0x02d3fc14: 00000001 0098ecf0 00000000 02d3fc88
0x02d3fc24: 6d6aea00 00000001 00000000 00000001
0x02d3fc34: 00000002 6d7adcd0 6d7adcd0 00000001
0x02d3fc44: 0098ecf0 00000000 00000000 00000001
0x02d3fc54: 00000001 00000001 00000000 00000000

Instructions: (pc=0x6d707ba1)
0x6d707b91: 08 8b 08 8b 40 08 8b 04 88 50 8b 48 04 83 c1 08
0x6d707ba1: 8b 11 ff 52 58 eb de c3 e9 00 00 00 00 c7 05 cc


Stack: [0x02d00000,0x02d40000), sp=0x02d3fbe4, free space=254k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [jvm.dll+0xc7ba1]
V [jvm.dll+0x6ea00]
V [jvm.dll+0x6e7da]
V [jvm.dll+0x71dba]
V [jvm.dll+0x102b38]
V [jvm.dll+0x6d5a9]
V [jvm.dll+0x50741]
V [jvm.dll+0x6d754]
V [jvm.dll+0x11d5b3]
V [jvm.dll+0x11d08a]
V [jvm.dll+0x11d22a]
V [jvm.dll+0x11cfbf]
C [MSVCRT.dll+0x85bc]
C [KERNEL32.DLL+0x438b]

VM_Operation (0x4326fa68): generation collection for allocation, mode: safepoint, requested by thread 0x03020788


--------------- P R O C E S S ---------------

Java Threads: ( => current thread )
0x03020788 JavaThread "SuspiciousFundTransferAgent 168934SUSPICIOUSTRNS" [_thread_blocked, id=1340]
0x02fb1578 JavaThread "SuspiciousFundTransferAgent for 168934" [_thread_blocked, id=556]
0x02fe09c8 JavaThread "TranFrauCheckFrame 168934" [_thread_blocked, id=976]
0x00236300 JavaThread "DestroyJavaVM" [_thread_blocked, id=1068]
0x02ee7920 JavaThread "Transaction Queue Listener" [_thread_blocked, id=1548]
0x009c01c0 JavaThread "AWT-Windows" daemon [_thread_in_native, id=728]
0x009a6838 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=1200]
0x009afa08 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=716]
0x009ae510 JavaThread "CompilerThread0" daemon [_thread_blocked, id=544]
0x009ad7d0 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=548]
0x0023ea48 JavaThread "Finalizer" daemon [_thread_blocked, id=1416]
0x00988da8 JavaThread "Reference Handler" daemon [_thread_blocked, id=1392]

Other Threads:
=>0x00987c98 VMThread [id=428]
0x009b0e08 WatcherThread [id=1328]

VM state:at safepoint (normal execution)

VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
[0x002358d0/0x00000318] Threads_lock - owner thread: 0x00987c98
[0x00235a98/0x000002dc] Heap_lock - owner thread: 0x03020788

Heap
def new generation total 18240K, used 1984K [0x06ab0000, 0x07e70000, 0x09210000)
eden space 16256K, 0% used [0x06ab0000, 0x06ab0000, 0x07a90000)
from space 1984K, 100% used [0x07c80000, 0x07e70000, 0x07e70000)
to space 1984K, 0% used [0x07a90000, 0x07a90000, 0x07c80000)
tenured generation total 244160K, used 244105K [0x09210000, 0x18080000, 0x26ab0000)
the space 244160K, 99% used [0x09210000, 0x18072708, 0x18072800, 0x18080000)
compacting perm gen total 8192K, used 4312K [0x26ab0000, 0x272b0000, 0x2aab0000)
the space 8192K, 52% used [0x26ab0000, 0x26ee6250, 0x26ee6400, 0x272b0000)
ro space 8192K, 62% used [0x2aab0000, 0x2afba3a0, 0x2afba400, 0x2b2b0000)
rw space 12288K, 46% used [0x2b2b0000, 0x2b8403d8, 0x2b840400, 0x2beb0000)
*****************************Dump End******************************

regards

[Peter Chase]

If your application contains your own, or third-party, native code that didn't come with the Java runtime, then that native code may have a bug. If it's your own code, you'd need to debug it. If it's third-party, you'd need to take up the issue with the third-party vendor.

If that's not the case, then you are the victim of a JVM bug. Pure Java code has no way to cause an OS-level access violation.

If the crash persists, try to find out as much as possible about what provokes it, then search Sun's Java bug database. You may find a bug report for what you've experienced. You'll certainly find reports of other access violations, but they could be for different bugs.

If you rewrite the affected Java code somehow, you may make the problem go away. That might only be temporary, of course.

Ultimately, you may need to get a newer version of the JVM, and hope Sun have fixed the problem.