Re: [Wrapper-user] EXCEPTION _ACCESS_VIOLATION

[Leif M. <le...@ta...>]

Mark,
Let me confirm, the message from the wrapper.log is showing that the
JVM process is crashing.  Does the Wrapper restart the JVM correctly?

The DrWatson output is confusing.  Is it saying that the Wrapper
process crashed as well?

The JVM crash itself could be caused by anything.  In all cases I have
encountered, the crashes would also happen without the Wrapper
in the equation.  When native libraries are being used, especially
custom ones, they tend to be related to the cause.  Java developers
are not used to the memory management issues that have to be
handled in the JNI world of C.  Then on top of that, there are lots of
strange releases that are required when using Java objects that C
developers are not used to dealing with.

Is this the product you are using?
http://www.intrinsyc.com/products/jintegra.asp
Try asking their support about the crash.  It may be something
they are aware of.

Cheers,
Leif

no spam wrote:
> I'm using JavaWrapper 3.2.3 and the JRE 1.6.0_01.  I have an 
> application that is using JIntegra to talk to COM objects on the local 
> machine that is controlling video encoding hardware.  If the system is 
> not loaded things seem to run great and I never see crashes.  If 
> I load the software so that it's hovering around 100% cpu I eventually (after 7 hours & not always exactly at this time) get crashes. 
>
>
> In the wrapper logs I see this:
>
> The JVM process terminated due to an uncaught exception: 
> EXCEPTION_ACCESS_VIOLATION (0xc0000005)
> JVM exited unexpectedly.
>
>
> Dr Watson shows this:
>
> Application exception occurred:
> App: c:\ipe\mvcp\javawrapper\bin\wrapper.exe (pid=2952)
> When: 5/1/2007 @ 17:28:49.263
> Exception number: c0000005 (access violation)
<snip>