Re: [Wrapper-user] Out of memory error

[Ashish G. <as...@se...>]

Leif Mortenson wrote:

> Ashish,
>    The Wrapper does not do anything special in the event of 
> OutOfMemoryErrors.
> This is because in most cases, while a single thread may terminate, 
> the JVM as
> a whole will continue to function.   It is actually possible to catch 
> out of memory
> errors and continue just as can be done with any other error or 
> exception.
>
>    Java by default sets a maximum memory limit of 65MB.   The Wrapper 
> preserves
> this default.  If, as in this case, you find it necessary to make use 
> of more memory then
> you can do so by passing a -Xmx64m parameter to the JVM.  The Wrapper 
> provides
> a pair of parameters to make it easier to set the maximum and initial 
> memory settings.
>    wrapper.java.initmemory=16
>    wrapper.java.maxmemory=64
>
>    I usually run Tomcat myself with only 64MB of memory.  But have a 
> few other apps
> that run with a setting of 256.  Be aware that this is the maximum 
> memory setting, the
> JVM will not use that much memory unless it is necessary.  Giving the 
> JVM more
> room to work with can make garbage collection run a little more smoothly.
>
>    The initial memory setting defines how much memory the JVM 
> allocates at startup.
> If you know that your application always takes 96MB of memory, then 
> setting this to
> a large initial value will make the app startup a little faster..
>
>    Please see the documentation for more info on these properties.
>
> Cheers,
> Leif 

Leif,

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?

Thanks,

Ashish