RE: OutOfMemory Exceptions AGAIN
This sounds like your sessions arent getting invalidated. If you look at the tomcat manager app it will tell you how many there are and you are likely to see this number increasing. The reason that it starts bloated is because when you shutdown the sessions get serialised and then reloaded once you restart tomcat. To stop it starting up bloated remove the SESSIONS.ser file from your context's work directory, while the server is shut down. As a more permanent solution you should explicitly invalidate the sessions in your code or reduce the session inactive timeout but i'd suggest the former. Ta Matt -Original Message- From: Nandish Rudra [mailto:[EMAIL PROTECTED] Sent: 17 August 2004 18:55 To: Tomcat Users List (E-mail) Subject: OutOfMemory Exceptions AGAIN Hello Everyone, I am getting an OutOfMemory Exceptions again. I have been running JProbe on my web application for some time now and have not noticed any memory issues, as in, memory not being released by the application. This is what my environment look like: - The environment is a cluster running on 2 Sun Blade servers running RedHat 9. Clustering is handled by my app and am not using tomcats clustering. - Apache 2, httpd 2.0.49 - Tomcat 5.0.25 - Java 2 SDK version 1.4.2_04 - Ant 1.6.1 I modified the server.xml to show the following change advised by one of the posts on the list. Engine className=org.apache.catalina.core.StandardEngine debug=0 defaultHost=localhost mapperClass=org.apache.catalina.core.StandardEngineMapper name=Standalone backgroundProcessorDelay=-1 I also set the JAVA_OPTS to JAVA_OPTS=-Xmn32M -Xmx128M -XX:MaxHeapFreeRatio=30 -XX:+UseParallelGC. I can change the -Xmx to 256 or 512 but that is not a solution, its just a way of temporarily getting away from the problem. I have the following symptons - I got OutOfMemory Exception today after moving to tomcat 5 a couple of months ago, but have been noticing some funny memory usage. I was previously using tomcat 4.1.30 and was getting memory exceptions almost everyday. - When I shutdown the server and restart it java starts bloated, same size as when it was shutdown. I have tried this with the application removed but no difference. Attempts: - I have tested the app on windows machine and VMware installations of the same environment(RedHat 9) and can't duplicate the problems. - I have used JProbe to monitor memory cleaning in both environments and have found nothing. - I am in the process of getting JProbe installed on the cluster and will be able to monitor thereafter. I can use some really good suggestions at this point. Regards, Nandish Rudra ECI Conference Call Services, LLC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory Exceptions AGAIN
Hello Matt, Thanks for the reply. When I get an http request I do not attach any session information or create and cookies/httpsessions and not using tomcat clustering, would the sessions still be serialized. Is there a way I can disable sessions completely from server.xml? Nandish Rudra ECI Conference Call Services, LLC -Original Message- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 17, 2004 2:07 PM To: Tomcat Users List Subject: RE: OutOfMemory Exceptions AGAIN This sounds like your sessions arent getting invalidated. If you look at the tomcat manager app it will tell you how many there are and you are likely to see this number increasing. The reason that it starts bloated is because when you shutdown the sessions get serialised and then reloaded once you restart tomcat. To stop it starting up bloated remove the SESSIONS.ser file from your context's work directory, while the server is shut down. As a more permanent solution you should explicitly invalidate the sessions in your code or reduce the session inactive timeout but i'd suggest the former. Ta Matt -Original Message- From: Nandish Rudra [mailto:[EMAIL PROTECTED] Sent: 17 August 2004 18:55 To: Tomcat Users List (E-mail) Subject: OutOfMemory Exceptions AGAIN Hello Everyone, I am getting an OutOfMemory Exceptions again. I have been running JProbe on my web application for some time now and have not noticed any memory issues, as in, memory not being released by the application. This is what my environment look like: - The environment is a cluster running on 2 Sun Blade servers running RedHat 9. Clustering is handled by my app and am not using tomcats clustering. - Apache 2, httpd 2.0.49 - Tomcat 5.0.25 - Java 2 SDK version 1.4.2_04 - Ant 1.6.1 I modified the server.xml to show the following change advised by one of the posts on the list. Engine className=org.apache.catalina.core.StandardEngine debug=0 defaultHost=localhost mapperClass=org.apache.catalina.core.StandardEngineMapper name=Standalone backgroundProcessorDelay=-1 I also set the JAVA_OPTS to JAVA_OPTS=-Xmn32M -Xmx128M -XX:MaxHeapFreeRatio=30 -XX:+UseParallelGC. I can change the -Xmx to 256 or 512 but that is not a solution, its just a way of temporarily getting away from the problem. I have the following symptons - I got OutOfMemory Exception today after moving to tomcat 5 a couple of months ago, but have been noticing some funny memory usage. I was previously using tomcat 4.1.30 and was getting memory exceptions almost everyday. - When I shutdown the server and restart it java starts bloated, same size as when it was shutdown. I have tried this with the application removed but no difference. Attempts: - I have tested the app on windows machine and VMware installations of the same environment(RedHat 9) and can't duplicate the problems. - I have used JProbe to monitor memory cleaning in both environments and have found nothing. - I am in the process of getting JProbe installed on the cluster and will be able to monitor thereafter. I can use some really good suggestions at this point. Regards, Nandish Rudra ECI Conference Call Services, LLC - 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: OutOfMemory Exceptions AGAIN
On Tue, Aug 17, 2004 at 02:13:40PM -0400, Nandish Rudra wrote: : Thanks for the reply. When I get an http request I do not attach any session : information or create and cookies/httpsessions and not using tomcat : clustering, would the sessions still be serialized. You may not explicitly put anything in a session, but they can still be created. For example, do all of your JSPs call %@ page session=false % ? As for your other point: :I can change the -Xmx to 256 or512 but that is not a solution, its just :a way of temporarily getting awayfrom the problem. Not necessarily true. Your app may just need more than 128M heap size. Have you load-tested the app, with your expected number of concurrent users, to see what the app's mem usage would be? -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: OutOfMemory Exceptions AGAIN
As previously mentioned you may not be explicitly using them but doesnt mean they arent there. Have you looked in your manager webapp to see how many sessions it say you are using? The sessions are always (by default) serialised on shutdown so that they are brought back again on restart. You can change this behaviour in the config. Check the documentation on session managers. I'm pretty sure you can't disable them completely but someone may put me right on this if i'm wrong. -Original Message- From: Nandish Rudra [mailto:[EMAIL PROTECTED] Sent: 17 August 2004 19:14 To: 'Tomcat Users List' Subject: RE: OutOfMemory Exceptions AGAIN Hello Matt, Thanks for the reply. When I get an http request I do not attach any session information or create and cookies/httpsessions and not using tomcat clustering, would the sessions still be serialized. Is there a way I can disable sessions completely from server.xml? Nandish Rudra ECI Conference Call Services, LLC -Original Message- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 17, 2004 2:07 PM To: Tomcat Users List Subject: RE: OutOfMemory Exceptions AGAIN This sounds like your sessions arent getting invalidated. If you look at the tomcat manager app it will tell you how many there are and you are likely to see this number increasing. The reason that it starts bloated is because when you shutdown the sessions get serialised and then reloaded once you restart tomcat. To stop it starting up bloated remove the SESSIONS.ser file from your context's work directory, while the server is shut down. As a more permanent solution you should explicitly invalidate the sessions in your code or reduce the session inactive timeout but i'd suggest the former. Ta Matt -Original Message- From: Nandish Rudra [mailto:[EMAIL PROTECTED] Sent: 17 August 2004 18:55 To: Tomcat Users List (E-mail) Subject: OutOfMemory Exceptions AGAIN Hello Everyone, I am getting an OutOfMemory Exceptions again. I have been running JProbe on my web application for some time now and have not noticed any memory issues, as in, memory not being released by the application. This is what my environment look like: - The environment is a cluster running on 2 Sun Blade servers running RedHat 9. Clustering is handled by my app and am not using tomcats clustering. - Apache 2, httpd 2.0.49 - Tomcat 5.0.25 - Java 2 SDK version 1.4.2_04 - Ant 1.6.1 I modified the server.xml to show the following change advised by one of the posts on the list. Engine className=org.apache.catalina.core.StandardEngine debug=0 defaultHost=localhost mapperClass=org.apache.catalina.core.StandardEngineMapper name=Standalone backgroundProcessorDelay=-1 I also set the JAVA_OPTS to JAVA_OPTS=-Xmn32M -Xmx128M -XX:MaxHeapFreeRatio=30 -XX:+UseParallelGC. I can change the -Xmx to 256 or 512 but that is not a solution, its just a way of temporarily getting away from the problem. I have the following symptons - I got OutOfMemory Exception today after moving to tomcat 5 a couple of months ago, but have been noticing some funny memory usage. I was previously using tomcat 4.1.30 and was getting memory exceptions almost everyday. - When I shutdown the server and restart it java starts bloated, same size as when it was shutdown. I have tried this with the application removed but no difference. Attempts: - I have tested the app on windows machine and VMware installations of the same environment(RedHat 9) and can't duplicate the problems. - I have used JProbe to monitor memory cleaning in both environments and have found nothing. - I am in the process of getting JProbe installed on the cluster and will be able to monitor thereafter. I can use some really good suggestions at this point. Regards, Nandish Rudra ECI Conference Call Services, LLC - 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] Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within
RE: OutOfMemory Exceptions AGAIN
Hello QM, As Matt had suggested, i check and there was a jsp from one of the other apps running, that was not invalidating sessions. I found 9000+ sessions of that jsp. The jsp now invalidates its sessions and hopefully things will be better. As the app is still under development the load is almost nothing hence the needs of the heap should not be great. I have been running the same app on my machine locally and have not had any memory issue as of yet. Thanks for the help guys. Regards, Nandish Rudra ECI Conference Call Services, LLC -Original Message- From: QM [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 17, 2004 4:25 PM To: Tomcat Users List Subject: Re: OutOfMemory Exceptions AGAIN On Tue, Aug 17, 2004 at 02:13:40PM -0400, Nandish Rudra wrote: : Thanks for the reply. When I get an http request I do not attach any session : information or create and cookies/httpsessions and not using tomcat : clustering, would the sessions still be serialized. You may not explicitly put anything in a session, but they can still be created. For example, do all of your JSPs call %@ page session=false % ? As for your other point: :I can change the -Xmx to 256 or512 but that is not a solution, its just :a way of temporarily getting awayfrom the problem. Not necessarily true. Your app may just need more than 128M heap size. Have you load-tested the app, with your expected number of concurrent users, to see what the app's mem usage would be? -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com - 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]
