We are running RedHat6.0, Blackdown JDK 1.1.7, JServ 1.1b3
We are using JServ as the application/communication layer for a large
project. The servlets we are running are doing a large amount of file
database IO. Currently during stress testing we are finding that at
point in our data processing the JServ seems to restart the JVM. (We see
watch this happen when running top in a window). We see the following
our mod_jserv.log at the time of the reset.
[10/11/1999 12:07:15:723] (EMERGENCY) ajp12: cannot scan servlet
[10/11/1999 12:07:15:794] (ERROR) an error returned handling request via
[10/11/1999 12:07:16:650] (EMERGENCY) ajp12: ping: no reply (-1)
Please make sure that
the wrapper.classpath is pointing to the correct version of
Does anyone out there know of any reason why the JVM might reset? At
we thought it might be running out of memory, so we placed a
-mx64m on in wrapper.bin.parameter line but we never notice the java
exceeding 20 or so megs.
Sent via Deja.com http://www.deja.com/
Before you buy.