Hope this helps,
David
Allistair Crossley wrote:
This is very interesting to hear. I can believe it too...we lose between 400K and 5MB per request and Tomcat 5.0.16 bombs out at 155.
We have invested in JProfiler now to see why but your comment is curious. Are you on the development team? When will 5.0.18 become stable...does not seem to be a binary download yet
Cheers ADC
-----Original Message----- From: David Strupl [mailto:[EMAIL PROTECTED] Sent: 19 January 2004 17:00 To: [EMAIL PROTECTED] Subject: Re: out of memory problem. Help!
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.
[EMAIL PROTECTED] 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:[EMAIL PROTECTED] 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
<FONT SIZE=1 FACE="VERDANA,ARIAL" COLOR=BLUE> ------------------------------------------------------- QAS Ltd. Developers of QuickAddress Software <a
href="http://www.qas.com";>www.qas.com</a> Registered in England: No
2582055 Registered in Australia: No 082 851 474 ------------------------------------------------------- </FONT
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
