The following reply was made to PR mod_jserv/5172; it has been noted by GNATS.
From: Thomas Fleischmann <[EMAIL PROTECTED]>
To: 'Ed Korthof' <[EMAIL PROTECTED]>
Cc: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: RE: mod_jserv/5172: Out of Memory exception at org.apache.jserv.J
ServConnection.processRequest
Date: Wed, 20 Oct 1999 09:25:41 -0700
The thing that I don't understand is that there is still a lot of memory
available in the UNIX system. And I configured the JVM to use the max.
available
memory.
I traced the memory usage of the servlet by calling
System.Runtime.getRuntime).freeMemory(), and found that the garbage
collection
seems to work fine (memory is growing and shrinking)...in 99% of the cases,
but sometimes, I don't know why, when the memory is low, the exception is
thrown
before freeing the memory! Anf then, just after the exception, the memory is
freed
and everything is fine!!
-----Original Message-----
From: Ed Korthof [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 19, 1999 6:08 PM
To: Thomas Fleischmann
Cc: '[EMAIL PROTECTED]'; [EMAIL PROTECTED]
Subject: RE: mod_jserv/5172: Out of Memory exception at
org.apache.jserv.J ServConnection.processRequest
Most likely servletrunner throttles the number of requests to some number
which is small enough that you never use all the available memory. That
is at least consistent with the observed behavior (as described so far).
The traditional organization of unix servers often means that more
configuration is required; but it also offers more flexibility.
Ed
