You can also try increasing the heap size of tomcat at
startup but this again depends on how much RAM ur
machine has??
Out of memory is usually because you have lots of
session objects still out there causing an overflow.
--- Mark Lowe <[EMAIL PROTECTED]> wrote:
> If its on a live deployment and your using tc 5.019
> with jk 1 then
> upgrade to 5.024 (Look for the decoding error in the
> logs).
>
> If its a dev server and you get this when you reload
> webapps, it just
> happens. TC5 is better than 4.1 but still eventually
> happens.
>
> Scoping to request will help reduce this, but it
> will still happen
> sooner or later. But on a live server, where reloads
> are non existent
> or hopefully rare then this is unlikely to happen.
> The only condition I
> found where this did happen was as I mentioned
> before the coyote apj
> service on the tomcat side having trouble talking to
> mod_jk.
>
>
>
> On 28 May 2004, at 20:29, Ciaran Hanley wrote:
>
> > Hi,
> >
> >
> >
> > My struts webapp seems to be using up a lot of
> memory and quite often
> > get
> > OutOfMemory errors or crash Tomcat requiring a
> restart. How do I go
> > about
> > freeing up memory? I have started by storing as
> many objects as
> > possible at
> > request scope rather that at session scope, is
> there any other things I
> > should look out for?
> >
> >
> >
> > Thanks
> >
> > CH
> >
> >
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
