If wrapper will programmaticaly restarted
(WrapperManager.restart();), JVM process crashes due
to an uncaught exception in native JVM code
EXCEPTION_ACCESS_VIOLATION (0xc0000005).
This couse Oracle OCI driver usage. But we don't need
popup message window (exceptions description staing in
log-file is enough). Some times the application will often
restarted and produce a lot of windows with error
message "java.exe crash with memory access violation
(0xc0000005)". Can you add the parameter to disable
this feature.
We use Wrapper 3.1.2 on Windows 2000 with JDK
1.4.2_05
Logged In: YES
user_id=228081
I'll go back and take another look at this. But I don't
think that there is anything that I can do about it. The
Java process is being launched by the Wrapper as a child
process. But I have not been able to find any way of
preventing a child process from showing a dialog like this.
Can you confirm that the Wrapper is correctly restarting the
Java application when this happens however?
Cheers,
Leif
Logged In: YES
user_id=1012060
Yes, Wrapper restarting the Java application correctly,
but User see ModalBox with error message.