----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
On Wed 19th Jan Sean Hammon wrote:
> while we were running JServ 1.0. Every other day or every third day JServ
> would simply stop responding. If you accessed a servlet, the browser would
> just sit and spin. No reply would ever come back. Stopping jserv and
We had similar problems. The reason turned out to be a memory leak in the JDBC
drivers we are using. Java's garbage collector could not free some objects
allocated by the JDBC drivers and as a result, Java had to increase its heap
size until the upper limit was reached. Surprisingly, we did not usually get
any "Out of memory" errors or exceptions in the log files.
Maybe you should check for memory leaks too. Run Java with the -verbosegc
option by setting "wrapper.bin.parameters=-verbosegc" in jserv.properties.
TS.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
