Re: [Wrapper-user] Out of memory error

[Leif M. <le...@ta...>]

Ashish Gawarikar wrote:

> Thanks for the info. I have used the settings (currently I have the 
> max set to 128 MB).
> But the real question (may be I missed to say that), is that the JVM 
> stops responding,
> and the tomcat responds with a page saying "horrible exception". My 
> question in
> regards to that was, if the JVM does stop responding, doesnt the 
> wrapper detect that,
> and restart the JVM? 

If this is easy to reproduce.  Could you please try running tomcat with 
the Wrapper's
debug output enabled.  My guess is that the JVM is actually fine but 
Tomcat has had a
critical error and it has stopped functioning.  If that is the case, 
then it would be a bug that
should be reported to the Tomcat team.

One thing that would be possible for me to do on the Wrapper side of 
things is to add a
property which would would have the Wrapper search for the string
"java.lang.OutOfMemoryError" in the stdout/stderr output of the JVM and 
then restart
the JVM.  It shouldn't cause that much of a performance hit, but I would 
still want it to be
optional.  Might as well allow users to enter their own trigger 
string(s) while I'm at it.
Needless to say, this would only work where output was sent to the JVM 
console.
These are actually problems caused by the application, but they can 
sometimes be
difficult to handle when the problem would need to be trapped within 3rd 
party code.

Cheers,
Leif