tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pradeep Chauhan" <>
Subject RE: Tomact 5 - Out of Memory
Date Thu, 05 Aug 2004 05:41:03 GMT
There is one more way which efftively help you to control memory leak .
On Close event of you application Call session.invalidate().
otherwise it will get invalidate after timeout period.

-----Original Message-----
From: Jon Doe []
Sent: 04.08.2004 21:48
Subject: Re: Tomact 5 - Out of Memory

>From: David Smith <>
>Reply-To: "Tomcat Users List" <>
>To: Tomcat Users List <>
>Subject: Re: Tomact 5 - Out of Memory
>Date: Wed, 04 Aug 2004 07:38:57 -0400
>I would set JAVA_OPTS in the startup script you're using to start
>Tomcat. There are loads of emails on the list regarding this. This issue
>is common enough you should be able to google the archives for details
>and get loads of responses.

Fair point -- if you haven't enough memory overhead, then until the garbage
collector kicks in to free objects up you will have a problem.
>Also as others have suggested, check your code for memory leaks --
>especially if it's not under load when it dies.

But hey, I thought one of the big selling points is that Java DOES NOT LEAK!
Am I mistaken? Isn't it's absence of pointers its big plus? If it does leak
then changing the heap size is going to be irrelevant. No matter how large
you set it it will bite you in the bum eventually!


Tired of spam? Get advanced junk mail protection with MSN 8.

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message