[Wrapper-user] JVM exited unexpectedly

[Paul C. <cas...@au...>]

Hi all,

This problem is not caused by the Java Service Wrapper - I just need some
help to extract some diagnostics please!

I have a problem where my JVM exits about once a week (not at a consistent
time) on Windows 2000 Advanced Server, JDK 1.3.1_09.

This is a new box - dual P4 2.4GHz with hyperthreading, 6.3GB of RAM, and 2
of the Java processes happily consume 1600MB of RAM each under the watchful
eye of the Java Service Wrapper.  Thankfully the Java Service Wrapper kicks
things off again when the JVM exits.

Before utilising the Java Service Wrapper, srvany (MS - yuck!) was used to
control the application.  It did die every now and then, and normally we
could explain it with a Dr Watson dialog saying that Java had caused an
access violation etc.  We don't seem to be getting the Dr Watson errors,
which is strange.  Peak RAM usage was around 4.25GB, which indicates that
the Java processes had been hitting the ceiling of 1600MB, but they should
garbage collect and get on their way.

Currently the wrapper log file level is set to WARN, syslog is set to FATAL
and console is set to FATAL.  As it may be another week before I see this
happen again, I'm not keen on trial and error of logging levels to dump out
more info next time the JVM decides to die - debug could result in huge
files without need.

What can I do to get some info about what happened when the JVM exited?

Thanks in advance,

Paul Casanova