on 1/24/00 1:36 PM, Constantin Nickonov <[EMAIL PROTECTED]> wrote:

> I also have this problem on a regular basis - every few days. The Apache JServ
> is smart enough to reload the servlet when it crashes, but there has to be a
> better way. My guess is that it's a memory leak, but I would like to hear
> about
> any experience and/or theories on the matter.
>
> Here's the entry from Apache's error_log:
>
> | java.lang.OutOfMemoryError
> |         at org.apache.jserv.JServConnection.sendHttpHeaders(Compiled Code)
> |         at org.apache.jserv.JServConnection.processRequest(Compiled Code)
> |         at org.apache.jserv.JServConnection.run(Compiled Code)
> |         at java.lang.Thread.run(Compiled Code)
>
> Thanks in advance for any insight from the list.
>
> Constantin

The *only* real way to deal with OOME is to increase the memory heap
allocation to the JVM. This is well documented in the FAQ.

<http://java.apache.org/jyve-faq/Turbine>

Also, make sure that your servlet isn't leaking memory. That could also be
the cause of your problems.

-jon

--
Come to the first official Apache Software Foundation
Conference!  <http://ApacheCon.Com/>

___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".

Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html

Reply via email to