tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Strupl <da...@solutions.cz>
Subject Re: out of memory problem. Help!
Date Mon, 19 Jan 2004 16:59:33 GMT
If you use tomcat 5.0.x upgrade to 5.0.18. If you use 4.1.x downgrade to 
4.1.27. There is a significant memory leak in tomcat in 5.0.16, 4.1.28(29).

Hope this helps,

David

Christian Witucki wrote:
> We fixed our session timeout to 15 minutes for 100 users and Tomcat
> hasn't crashed for 36 hours.  Does anyone know how we can adjust for
> the possibilities of 1000's of users???
> 
> Christian Witucki Network Analyst 375 Essjay Road Williamsville, NY
> 14221 716-631-3001 x3812
> 
> CONFIDENTIALITY NOTICE. This e-mail and attachments, if any, may
> contain confidential information which is privileged and protected
> from disclosure by Federal and State confidentiality laws, rules or
> regulations.  This e-mail and attachments, if any, are intended for
> the designated addressee only .  If you are not the designated
> addressee, you are hereby notified that any disclosure, copying, or
> distribution of this e-mail and its attachments, if any, may be
> unlawful and may subject you to legal consequences.  If you have
> received this e-mail and attachments in error, please contact
> Independent Health immediately at (716) 631-3001 and delete the
> e-mail and its attachments from your computer.  Thank you for your
> attention.
> 
> 
>>>> sanjeev@julysystems.com 01/19/04 01:20AM >>>
> 
> 
> Check session-timeout in web.xml. -1 is never timeout 
> <session-timeout>-1</session-timeout>
> 
> -----Original Message----- From: Christophe Andreoli
> [mailto:andreoli@gsf.de] Sent: Friday, January 16, 2004 9:19 PM To:
> Tomcat Users List Subject: Re: out of memory problem. Help!
> 
> "Shapira, Yoav" wrote:
> 
>> Howdy,
>> 
>> 
>>> root cause
>>> 
>>> java.lang.OutOfMemoryError
>>> 
>>> 
>>> It happens When the corresponding request returns more than
> 
> 20000-30000
> 
>>> rows from the database, not every time
> 
> 
> 
> 
> 
>> Perhaps you should allocate your JVM more memory, by using the Java
>> 
> 
> -Xmx
> 
>> parameter.
> 
> 
> I did it and I gave 512 Mb.
> 
> It works better but why are the 2000 objects are not garbaged after
> each request ?
> 
> 
> 
> 
> 
> 
> 
> 
> Alternatively, consider a system design that retrieves a
> 
>> smaller, fixed number of rows instead of "20000-30000" and lets the
>> 
> 
> user
> 
>> scroll, say 100 rows at a time.
>> 
>> Yoav Shapira
>> 
> 
> 
> ---------------------------------------------------------------------
>  To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org 
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message