RE: out of memory problem. Help!
Try this in your jk2.properties file and see if it fixes it for 4.1.29. According to Bill Barker(thread: maxProcessors vs maxThreads), this is the same as the 5.x connector setting for jk2. container.maxThreads=value container.maxSpareThreads=value container.minSpareThreads=value Unfortunately I do not have time to mess with this right now, but I am interested to know if it fixes the leak. Charlie -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of David Strupl Sent: Monday, January 19, 2004 2:08 PM To: [EMAIL PROTECTED] Subject: Re: out of memory problem. Help! This did not work for me in 4.1.29 since the only way to do this is to set minProcessors==maxProcessors but that did not have any effect in 4.1.29. I am not sure whether I could use xxxThreads there but downgrading to 4.1.27 did help. For those using 5.0.16 this can help - Filip thanks for finding out. Best, David Filip Hanik wrote: set maxSpareThreads=minSpareThreads=maxThreads will cause the system to never shrink the pool Filip -Original Message- From: news [mailto:[EMAIL PROTECTED] Behalf Of David Strupl Sent: Monday, January 19, 2004 9:58 AM To: [EMAIL PROTECTED] Subject: Re: out of memory problem. Help! Remy Maucherat wrote: This is not true: there's indeed a memory leak with 5.0.16, but it would occur only with specific traffic patterns. It will not bring a server down in just a few requests. Indeed. The thread pool has to grow and shrink for this to happen. Unfortunatelly quite common e.g. day and night traffic. D. - 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]
RE: out of memory problem. Help!
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 2-3 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 2-3 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]
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 2-3 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 2-3 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]
RE: out of memory problem. Help!
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 2-3 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 2-3 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]
Re: out of memory problem. Help!
I am not on the developer team. But spent quite a lot of hours (days) latelly with figuring out why my copy of tomcat (4.1.29) leaks memory. The information bellow is based on the info from the dev mailing list + a thread on this mailing list with subject Tomcat Tuning Memory leak from last couple of days (weeks). I am still testing 4.1.27 and all seems fine so far. Re 5.0.18: thats a revision where the fix was commited - please check the dev mailing list with subject Found it - WAS: Memory leak and RE: [5.0.18] Build available. 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 2-3 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 2-3 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]
Re: out of memory problem. Help!
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 I suggest you continue investigating with your profiler: you have a different problem. -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). This is not true: there's indeed a memory leak with 5.0.16, but it would occur only with specific traffic patterns. It will not bring a server down in just a few requests. -- x Rémy Maucherat Senior Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: out of memory problem. Help!
Remy Maucherat wrote: This is not true: there's indeed a memory leak with 5.0.16, but it would occur only with specific traffic patterns. It will not bring a server down in just a few requests. Indeed. The thread pool has to grow and shrink for this to happen. Unfortunatelly quite common e.g. day and night traffic. D. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: out of memory problem. Help!
set maxSpareThreads=minSpareThreads=maxThreads will cause the system to never shrink the pool Filip -Original Message- From: news [mailto:[EMAIL PROTECTED] Behalf Of David Strupl Sent: Monday, January 19, 2004 9:58 AM To: [EMAIL PROTECTED] Subject: Re: out of memory problem. Help! Remy Maucherat wrote: This is not true: there's indeed a memory leak with 5.0.16, but it would occur only with specific traffic patterns. It will not bring a server down in just a few requests. Indeed. The thread pool has to grow and shrink for this to happen. Unfortunatelly quite common e.g. day and night traffic. D. - 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]
Re: out of memory problem. Help!
This did not work for me in 4.1.29 since the only way to do this is to set minProcessors==maxProcessors but that did not have any effect in 4.1.29. I am not sure whether I could use xxxThreads there but downgrading to 4.1.27 did help. For those using 5.0.16 this can help - Filip thanks for finding out. Best, David Filip Hanik wrote: set maxSpareThreads=minSpareThreads=maxThreads will cause the system to never shrink the pool Filip -Original Message- From: news [mailto:[EMAIL PROTECTED] Behalf Of David Strupl Sent: Monday, January 19, 2004 9:58 AM To: [EMAIL PROTECTED] Subject: Re: out of memory problem. Help! Remy Maucherat wrote: This is not true: there's indeed a memory leak with 5.0.16, but it would occur only with specific traffic patterns. It will not bring a server down in just a few requests. Indeed. The thread pool has to grow and shrink for this to happen. Unfortunatelly quite common e.g. day and night traffic. D. - 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]
RE: out of memory problem. Help!
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 2-3 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 2-3 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]
out of memory problem. Help!
Hello !
I have a Struts/jsp Application
Ich get an out of memory problem:javax.servlet.ServletException: Servlet
execution threw an exception
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:243)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:190)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:531)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2347)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:170)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:468)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:564)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at
org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:566)
at
org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472)
at
org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943)
at
org.apache.ajp.tomcat4.Ajp13Processor.process(Ajp13Processor.java:458)
at
org.apache.ajp.tomcat4.Ajp13Processor.run(Ajp13Processor.java:551)
at java.lang.Thread.run(Thread.java:536)
root cause
java.lang.OutOfMemoryError
It happens When the corresponding request returns more than 2-3
rows from the database, not every time
but surely if more request run parallely
From the 2-3 rows I am making the same number of the following
objects from this class
class{
public int humanId=-1;
public String humanDescription=;
public String swissProtId=;
public String swissProtName=;
public String function=;
public String subcellularLocation =;
public String alternativeProtein =;
public String pathway =;
public double mitoProt =-1;
public int mitoLocal=-1;
private double accuracy;
public String swissProtLink=;
private int hasEncephalHomolog=-1;
private int hasRickettsiaHomolog=-1;
private int hasYeastMitoHomolog=-1;
private int hasParalogMito=-1;
private int heartProteome=-1;
private int psort=-1;
private String mesClone=;
private String mesUnigene=;
private int holgerCandidate=-1;
private int predotar=-1;
private String omim=;
private String subLocWiemann=;
}
Can you help me ?
Thank you!
Chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: out of memory problem. Help!
- Get more memory - allocate more memory to the JVM (http://jakarta.apache.org/tomcat/faq/memory.html#adjust) - Don't place 20,000 ros of data in memory - Limit the size of your query -Tim Christophe Andreoli wrote: Hello ! I have a Struts/jsp Application Ich get an out of memory problem:javax.servlet.ServletException: Servlet execution threw an exception at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: out of memory problem. Help!
Howdy, root cause java.lang.OutOfMemoryError It happens When the corresponding request returns more than 2-3 rows from the database, not every time Perhaps you should allocate your JVM more memory, by using the Java -Xmx parameter. Alternatively, consider a system design that retrieves a smaller, fixed number of rows instead of 2-3 and lets the user scroll, say 100 rows at a time. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: out of memory problem. Help!
Shapira, Yoav wrote: Howdy, root cause java.lang.OutOfMemoryError It happens When the corresponding request returns more than 2-3 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 2-3 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]
RE: out of memory problem. Help!
Howdy, It works better but why are the 2000 objects are not garbaged after each request ? There's only one reason objects aren't garbage-collected in java: other objects are keeping references to them. You can inspect or profile your code to see what keeps references to what. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
