Re: Memory leak in Tomcat
--- Ingrid Morterud Rosvall [EMAIL PROTECTED] wrote: Hello. We are running an application on Tomcat 4.1.30, and java 1.4.2. Our application is using the struts framework with jsp's, and cocoon to render the xml's. There seems to be a major memory leak at startup - the application seems to constantly be using between 40 - 45 mb of the memory. We also have some memory leak during runtime, when users log on and starts using the application. So far we have not been able to find anything in our code review that will explain these memory leaks, and when we monitor the memory used, there is no obvious reason, nor is there any connection with how the users use our application and the amount of memory being used. We would highly appreciate any help on this topic, and any tips and hints you can provide us with. Ingrid and Tommy One, I think you might be having issues by not understanding the java heap...just an observation by the way you phrased the question. Two, do you have any more information about the memory being used? How much were you expecting to be used? Are you seeing the virtual memory usage or the real memory usage? How did you determine the amount of memory used? Do you have any numbers? Have you tried to use a memory profiler? Search the list for memory profiler. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Memory leak in Tomcat
Ingrid, I am not on the tomcat developer committer list so my reply is just an FYI from my own experience. I saw unstable performance myself in a very similar deployment of Struts applications similar to yours. I too thought there was a memory leak and there may be, but I don't think it is in the applications themselves. The behavior I saw, led me to think it was related to socket allocation as after a period of time my system began to complain and slow down and other socket related programs began to complain about timeouts, etc. I found that my tomcat needed to use virtual memory to avoid out of memory exceptions. I added physical memory and the problems all but went away, however it still occurs just less frequently. I am using j2sdk1.4.2_09 Tomcat-5.0.28 On Windows XP Pro sp1 Michael Oliver CTO Alarius Systems LLC 6800 E. Lake Mead Blvd, #1096 Las Vegas, NV 89156 Phone:(702)643-7425 Fax:(702)974-0341 *Note new email changed from [EMAIL PROTECTED] -Original Message- From: Ingrid Morterud Rosvall [mailto:[EMAIL PROTECTED] Sent: Monday, September 12, 2005 1:00 PM To: tomcat-user@jakarta.apache.org Subject: Memory leak in Tomcat Hello. We are running an application on Tomcat 4.1.30, and java 1.4.2. Our application is using the struts framework with jsp's, and cocoon to render the xml's. There seems to be a major memory leak at startup - the application seems to constantly be using between 40 - 45 mb of the memory. We also have some memory leak during runtime, when users log on and starts using the application. So far we have not been able to find anything in our code review that will explain these memory leaks, and when we monitor the memory used, there is no obvious reason, nor is there any connection with how the users use our application and the amount of memory being used. We would highly appreciate any help on this topic, and any tips and hints you can provide us with. Ingrid and Tommy -- I am using the free version of SPAMfighter for private users. It has removed 4102 spam emails to date. Paying users do not have this message in their emails. Try www.SPAMfighter.com for free now! - 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: Memory leak in Tomcat
Hi, Can you share how much memory do you have and how much used by tomcat and what JAVA_OPTs do you have. Thanks a lot, Mark. --- Michael Oliver [EMAIL PROTECTED] wrote: Ingrid, I am not on the tomcat developer committer list so my reply is just an FYI from my own experience. I saw unstable performance myself in a very similar deployment of Struts applications similar to yours. I too thought there was a memory leak and there may be, but I don't think it is in the applications themselves. The behavior I saw, led me to think it was related to socket allocation as after a period of time my system began to complain and slow down and other socket related programs began to complain about timeouts, etc. I found that my tomcat needed to use virtual memory to avoid out of memory exceptions. I added physical memory and the problems all but went away, however it still occurs just less frequently. I am using j2sdk1.4.2_09 Tomcat-5.0.28 On Windows XP Pro sp1 Michael Oliver CTO Alarius Systems LLC 6800 E. Lake Mead Blvd, #1096 Las Vegas, NV 89156 Phone:(702)643-7425 Fax:(702)974-0341 *Note new email changed from [EMAIL PROTECTED] -Original Message- From: Ingrid Morterud Rosvall [mailto:[EMAIL PROTECTED] Sent: Monday, September 12, 2005 1:00 PM To: tomcat-user@jakarta.apache.org Subject: Memory leak in Tomcat Hello. We are running an application on Tomcat 4.1.30, and java 1.4.2. Our application is using the struts framework with jsp's, and cocoon to render the xml's. There seems to be a major memory leak at startup - the application seems to constantly be using between 40 - 45 mb of the memory. We also have some memory leak during runtime, when users log on and starts using the application. So far we have not been able to find anything in our code review that will explain these memory leaks, and when we monitor the memory used, there is no obvious reason, nor is there any connection with how the users use our application and the amount of memory being used. We would highly appreciate any help on this topic, and any tips and hints you can provide us with. Ingrid and Tommy -- I am using the free version of SPAMfighter for private users. It has removed 4102 spam emails to date. Paying users do not have this message in their emails. Try www.SPAMfighter.com for free now! - 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] __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Memory leak in Tomcat
Hi, On my test environment I am just on 64 Mb of memory. I know I can increase that - but that still will not fix my initial problem. My application is using 40 - 45 Mb - and that is more than I thought it should use. At the moment I have no JAVA_OPTS. Thanks for trying to help. :-) Ingrid and Tommy -Original Message- From: Mark [mailto:[EMAIL PROTECTED] Sent: 12. september 2005 22:36 To: Tomcat Users List; [EMAIL PROTECTED] Subject: RE: Memory leak in Tomcat Hi, Can you share how much memory do you have and how much used by tomcat and what JAVA_OPTs do you have. Thanks a lot, Mark. --- Michael Oliver [EMAIL PROTECTED] wrote: Ingrid, I am not on the tomcat developer committer list so my reply is just an FYI from my own experience. I saw unstable performance myself in a very similar deployment of Struts applications similar to yours. I too thought there was a memory leak and there may be, but I don't think it is in the applications themselves. The behavior I saw, led me to think it was related to socket allocation as after a period of time my system began to complain and slow down and other socket related programs began to complain about timeouts, etc. I found that my tomcat needed to use virtual memory to avoid out of memory exceptions. I added physical memory and the problems all but went away, however it still occurs just less frequently. I am using j2sdk1.4.2_09 Tomcat-5.0.28 On Windows XP Pro sp1 Michael Oliver CTO Alarius Systems LLC 6800 E. Lake Mead Blvd, #1096 Las Vegas, NV 89156 Phone:(702)643-7425 Fax:(702)974-0341 *Note new email changed from [EMAIL PROTECTED] -Original Message- From: Ingrid Morterud Rosvall [mailto:[EMAIL PROTECTED] Sent: Monday, September 12, 2005 1:00 PM To: tomcat-user@jakarta.apache.org Subject: Memory leak in Tomcat Hello. We are running an application on Tomcat 4.1.30, and java 1.4.2. Our application is using the struts framework with jsp's, and cocoon to render the xml's. There seems to be a major memory leak at startup - the application seems to constantly be using between 40 - 45 mb of the memory. We also have some memory leak during runtime, when users log on and starts using the application. So far we have not been able to find anything in our code review that will explain these memory leaks, and when we monitor the memory used, there is no obvious reason, nor is there any connection with how the users use our application and the amount of memory being used. We would highly appreciate any help on this topic, and any tips and hints you can provide us with. Ingrid and Tommy -- I am using the free version of SPAMfighter for private users. It has removed 4102 spam emails to date. Paying users do not have this message in their emails. Try www.SPAMfighter.com for free now! - 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] __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I am using the free version of SPAMfighter for private users. It has removed 4102 spam emails to date. Paying users do not have this message in their emails. Try www.SPAMfighter.com for free now! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Memory leak in Tomcat
--- Ingrid Morterud [EMAIL PROTECTED] wrote: Thanks for the quick reply. You might be right in us not understanding the java heap. Still - then we are even more at a loss on how to fix the problem than if we really had understood how it works. We are running on a test server with 64 mb total memory. I know I can increase that, still increasing it will not solve the original problem. To be quite honest I am not quite sure what I would be expecting to be using, but I would think that the application up and running would use less than what it is using at the moment. We are using the following code to determine the memory used: br %=java.lang.Runtime.getRuntime().freeMemory()/1024% KB br %=java.lang.Runtime.getRuntime().maxMemory()/1024% KB br %=java.lang.Runtime.getRuntime().totalMemory()/1024% KB br The application uses approx 40 - 45 Mb when it is running. During runtime (when users access and use the application) they use from zero to 25 Mb of memory. I still cannot find any pattern as to when it uses the memory. The amount of memory used changes not accordingly to the user input, that means that when a user does the same thing twice, that does not mean that the same amount of memory is used. We haven't used a memory profiler as of yet, but we are going to try that out now. If you have any more hints and tips, it would be highly appreciated. Ingrid and Tommy Ingrid, I included this on the tomcat users list. Yes, any time you reply to a mail where you asked the question on the list then please include the entire list. It will help everyone help you out as they will get the information you give me, and if it is something they could better help you with then the right person got the info, and you can get helped faster. Yeah, 64mb of memory could be enough depending on what you are doing, but you are using struts and I don't know what other libraries. The jvm itself will use a number of megs of memory simply by loading classes and static information into what is know as Persistent memory. A good link would be: http://java.sun.com/docs/performance/ where you will find a lot of information about memory and performance. Also see: http://java.sun.com/docs/hotspot/gc1.4.2/ Also understand that the info you will see with the commands you are using in your source code are not going to show you the memory being used by the persistent section of the JVM process nor are they going to show you the OS reserved memory for the process or virtual memory. So, you might have issues trying to use Tomcat on a 64MB machine depending on the number of libraries used to the number of classes loaded to the number of static variables and things of that nature. The OS will use a number of memory along with what ever other applications you are using. After that memory is used you start paging to disk a lot and performance will stink at best. You can also search the list for JProfiler. There have been other mailings about memory and leaks on the list and a lot of information for a starting point has already been provided. I can simply start tomcat with only the admin and manager application running and be using 22mb of memory. Are you memory usage reports after your web application has loaded. Then after it has loaded you are using 40+mb? You can find jstat and install it into your 1.4.2 jvm. If you have 1.5 it will already be available. Then with tomcat running do a jps to locate your PID and then jstat -class PID to explain the classes loaded before you hit your first URL to your web app vs after. Might tell you something as well. Using: http://java.sun.com/docs/hotspot/gc1.4.2/ and JAVA_OPTS you should be able to adjust the memory usage of tomcat, and if not you might have to dig into catalina.bat or if on windows use the configure tomcat GUI for the service. But, that amount of memory is so tiny I don't think you'll have much luck if your web application expects much usage. It will all depend on the number of classes being loaded and used and the number of objects being instantiated. You can limit your entire heap with the -mx option of the JVM. This will not however limit your persistent memory usage. You'll have to use -XX:MaxPermSize to limit that. Limiting your heap and your permsize however will mean you know for a fact or good close estimate that you should be loading x number of classes and using x number of perm memory and limiting your heap means you have calculated your application and tomcats expected memory usage and number of supported users for your needs. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak in tomcat 5.0.28
Marx, Mitchell E (Mitch), ALABS wrote: I see the bugzilla ID: http://issues.apache.org/bugzilla/show_bug.cgi?id=33368 Anyone know if this is present in Tomcat 4.1.30? This is now fixed in CVS for TC4. Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak in tomcat 5.0.28
Marx, Mitchell E (Mitch), ALABS wrote: I see the bugzilla ID: http://issues.apache.org/bugzilla/show_bug.cgi?id=33368 Anyone know if this is present in Tomcat 4.1.30? Yes. http://issues.apache.org/bugzilla/show_bug.cgi?id=20758 is also present but is fixed in 4.1.31 Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak in tomcat 5.0.28
Thank you Robert!! Just wanna say thanks alot for sharing all your findings with the rest of us. I start my tomcat 5.0.28 server with -ms252m -mx512m and it was running for about 3-4 days before i got the OutOfMemoryError. Since i removed the swallowOutput from my context, my server has'nt been over 200m of used memory for 5 days!! Once again thank you for finding this leak. Regards Trond - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak in tomcat 5.0.28
I see the bugzilla ID: http://issues.apache.org/bugzilla/show_bug.cgi?id=33368 Anyone know if this is present in Tomcat 4.1.30? - Original Message - From: Robert Wille [EMAIL PROTECTED] To: tomcat-user@jakarta.apache.org Sent: Wednesday, February 02, 2005 1:25 PM Subject: RE: Memory leak in tomcat 5.0.28 I've figured out my problem. I'm posting what I've discovered for the benefit of others. The SystemLogHandler uses a map called logs where the key is a ThreadWithAttributes and the value is a stack of CaptureLogs. The problem is that when a thread dies, the ThreadWithAttributes object lives forever because the map is never cleaned out. Threads come and go in the thread pool, so stuff keeps accumulating there forever. You can prevent the problem by turning off swallowOutput. logs should be a ThreadLocal, not a map. That way the ThreadWithAttributes objects can be collected (as well as the stack of CaptureLogs). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Memory leak in tomcat 5.0.28
I've figured out my problem. I'm posting what I've discovered for the benefit of others. The SystemLogHandler uses a map called logs where the key is a ThreadWithAttributes and the value is a stack of CaptureLogs. The problem is that when a thread dies, the ThreadWithAttributes object lives forever because the map is never cleaned out. Threads come and go in the thread pool, so stuff keeps accumulating there forever. You can prevent the problem by turning off swallowOutput. logs should be a ThreadLocal, not a map. That way the ThreadWithAttributes objects can be collected (as well as the stack of CaptureLogs). From: Robert Wille [EMAIL PROTECTED] Reply-To: Tomcat Users List tomcat-user@jakarta.apache.org To: tomcat-user@jakarta.apache.org Subject: Memory leak in tomcat 5.0.28 Date: Wed, 02 Feb 2005 09:16:49 -0700 I'm running tomcat 5.0.28 on Linux with JRE 1.4.2_04 and I seem to have a memory leak. I am not using Apache, but am using the Coyote connector. The server has been running under heavy load, being accessed by about 150 computers running automated tests. I took heap snapshots about 8 and 20 hours into the test using YourKit Java Profiler. When taking the snapshots, I first paused the system for several minutes, attempted to allocate more memory than was available to cause all collectable objects to be collected, and then took the snapshot. Therefore, the snapshots should contain very few collectable objects, and there should be very few open http connections. The following seems very suspicious: The last snapshot shows 419 Http11Processor objects referencing 41M of memory. That is an increase of 232 Http11Processor objects. It also shows 81,829 objects in the org.apache.tomcat.util.buf package, which reference 37M of memory. This is an increase of 44,874 objects. The buffers and Http11Processor objects appear to be referenced by org.apache.tomcat.util.threads.ThreadWithAttributes. I show 425 instances, which is an increase of 225. The first snapshot was 8 hours into the test, and in reality, I think the system should have reached steady state just a few minutes into the test. But I am obviously accumulating a lot of stuff. Can somebody help? Robert Wille _ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak in tomcat 5.0.28
feel free to open a bug report, so that this issue can be tracked. - Original Message - From: Robert Wille [EMAIL PROTECTED] To: tomcat-user@jakarta.apache.org Sent: Wednesday, February 02, 2005 1:25 PM Subject: RE: Memory leak in tomcat 5.0.28 I've figured out my problem. I'm posting what I've discovered for the benefit of others. The SystemLogHandler uses a map called logs where the key is a ThreadWithAttributes and the value is a stack of CaptureLogs. The problem is that when a thread dies, the ThreadWithAttributes object lives forever because the map is never cleaned out. Threads come and go in the thread pool, so stuff keeps accumulating there forever. You can prevent the problem by turning off swallowOutput. logs should be a ThreadLocal, not a map. That way the ThreadWithAttributes objects can be collected (as well as the stack of CaptureLogs). From: Robert Wille [EMAIL PROTECTED] Reply-To: Tomcat Users List tomcat-user@jakarta.apache.org To: tomcat-user@jakarta.apache.org Subject: Memory leak in tomcat 5.0.28 Date: Wed, 02 Feb 2005 09:16:49 -0700 I'm running tomcat 5.0.28 on Linux with JRE 1.4.2_04 and I seem to have a memory leak. I am not using Apache, but am using the Coyote connector. The server has been running under heavy load, being accessed by about 150 computers running automated tests. I took heap snapshots about 8 and 20 hours into the test using YourKit Java Profiler. When taking the snapshots, I first paused the system for several minutes, attempted to allocate more memory than was available to cause all collectable objects to be collected, and then took the snapshot. Therefore, the snapshots should contain very few collectable objects, and there should be very few open http connections. The following seems very suspicious: The last snapshot shows 419 Http11Processor objects referencing 41M of memory. That is an increase of 232 Http11Processor objects. It also shows 81,829 objects in the org.apache.tomcat.util.buf package, which reference 37M of memory. This is an increase of 44,874 objects. The buffers and Http11Processor objects appear to be referenced by org.apache.tomcat.util.threads.ThreadWithAttributes. I show 425 instances, which is an increase of 225. The first snapshot was 8 hours into the test, and in reality, I think the system should have reached steady state just a few minutes into the test. But I am obviously accumulating a lot of stuff. Can somebody help? Robert Wille _ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ - 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: Memory leak with Tomcat 5.0.19
On 20-05-2004 11:58, wsedio wrote: On 19-05-2004 23:15, Michiel Toneman wrote: We were having severe memory problems too with 5.0.19. Does Tomcat 5.0.24 fix this problem? We added this to the jk2.properties: request.registerRequests=false and the memory usage was normal again. Somewhat non-obvious, I agree. It also gets rid of Error registering request messages in catalina.out. We are using mod_jk (1.2) with Apache 1.3.x on Sun Solaris and Linux. Do you have to add the setting even if you are using jk 1.2 (not jk 2)? Below is the memory profile of one of our servers before and after the change (old generation memory refers to the memory buckets in the garbage collector. For more information, see jvmstat. At 100% you will start getting OutOfMemory errors): How do you get the memory profile? Is it a Tomcat command? Thanks. Any help with my questions? Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak with Tomcat 5.0.19
wsedio wrote: On 20-05-2004 11:58, wsedio wrote: On 19-05-2004 23:15, Michiel Toneman wrote: We were having severe memory problems too with 5.0.19. Does Tomcat 5.0.24 fix this problem? I have no idea, haven't tried it out yet. No plans as yet to test/roll-out 5.0.24, so it will be a while before I know. We added this to the jk2.properties: request.registerRequests=false and the memory usage was normal again. Somewhat non-obvious, I agree. It also gets rid of Error registering request messages in catalina.out. We are using mod_jk (1.2) with Apache 1.3.x on Sun Solaris and Linux. Do you have to add the setting even if you are using jk 1.2 (not jk 2)? Apparently so. Somewhat weird that it is in jk2.properties. Any Guru care to explain? Below is the memory profile of one of our servers before and after the change (old generation memory refers to the memory buckets in the garbage collector. For more information, see jvmstat. At 100% you will start getting OutOfMemory errors): How do you get the memory profile? Is it a Tomcat command? No, it is just a bit of messing around with jvmstat in a script. First we get the Tomcat PID with jvmps. Then we use jvmsnap $TOMCAT_PID to get (grep) hotspot.gc.generation.1.space.0.capacity and hotspot.gc.generation.1.space.0.used The script then calculates the percentage in use and total amount in Mb. The old generation space usage is (as far as I know) a good place to look if you are experiencing memory problems (assuming you set -Xmx and -Xms memory the same, otherwise it isn't all that meaningful!!!). In my experience, if it fills up above 70% the garbage collector (+ you) is in trouble. Cheers, Michiel -- Michiel Toneman Software Engineer Bibit Global Payment Services Regulierenring 10 3981 LB Bunnik [EMAIL PROTECTED] Tel. +31-30-6595168 Fax +31-30-6564464 http://www.bibit.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Memory leak with Tomcat 5.0.19
I added the request.registerRequests=false to jk2.properties yesterday, but I still do not have a definite confirmation on whether this problem is fixed. The JVM did grow to over 600MB, which is more that my Tomcat 4.1.x instances, but Tomcat crashed the site yesterday at about 7pm, so I didn't have a chance to see if the memory continued to grow. (there was about 200MB free of the 624 MB allocated at the time of the crash - I'll have to deal with that later). I read the documentation on jk2.properties, but didn't really get much there. Is there anyone with a good documented jk2.properties files that would care to share? BTW - for all interested, I also set development to false, and fork to true in web.xml. I have also removed jsvc from the equation just to make sure it is not part of the problem. Brian Beckham [EMAIL PROTECTED] Office: 770.924.6444 ext. 203 Mobile: 404.406.8355 -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Thursday, May 20, 2004 1:09 PM To: Tomcat Users List Subject: Re: Memory leak with Tomcat 5.0.19 wsedio wrote: On 19-05-2004 23:15, Michiel Toneman wrote: We were having severe memory problems too with 5.0.19. Does Tomcat 5.0.24 fix this problem? We added this to the jk2.properties: request.registerRequests=false and the memory usage was normal again. Somewhat non-obvious, I agree. It also gets rid of Error registering request messages in catalina.out. We are using mod_jk (1.2) with Apache 1.3.x on Sun Solaris and Linux. Do you have to add the setting even if you are using jk 1.2 (not jk 2)? Someone could answer this question, please? Becouse my available memory is going down from 120 to 50 and to 10 megabytes to fast. And I'm not finding any leak in my apps... Below is the memory profile of one of our servers before and after the change (old generation memory refers to the memory buckets in the garbage collector. For more information, see jvmstat. At 100% you will start getting OutOfMemory errors): How do you get the memory profile? Is it a Tomcat command? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181 - 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: Memory leak with Tomcat 5.0.19
Ok, after adding that setting in jk2.properties I have had 2 lockups of tomcat on my production siteany help!!?!!? Brian Beckham [EMAIL PROTECTED] Office: 770.924.6444 ext. 203 Mobile: 404.406.8355 -Original Message- From: Brian Beckham [mailto:[EMAIL PROTECTED] Sent: Friday, May 21, 2004 8:53 AM To: Tomcat Users List Subject: RE: Memory leak with Tomcat 5.0.19 I added the request.registerRequests=false to jk2.properties yesterday, but I still do not have a definite confirmation on whether this problem is fixed. The JVM did grow to over 600MB, which is more that my Tomcat 4.1.x instances, but Tomcat crashed the site yesterday at about 7pm, so I didn't have a chance to see if the memory continued to grow. (there was about 200MB free of the 624 MB allocated at the time of the crash - I'll have to deal with that later). I read the documentation on jk2.properties, but didn't really get much there. Is there anyone with a good documented jk2.properties files that would care to share? BTW - for all interested, I also set development to false, and fork to true in web.xml. I have also removed jsvc from the equation just to make sure it is not part of the problem. Brian Beckham [EMAIL PROTECTED] Office: 770.924.6444 ext. 203 Mobile: 404.406.8355 -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Thursday, May 20, 2004 1:09 PM To: Tomcat Users List Subject: Re: Memory leak with Tomcat 5.0.19 wsedio wrote: On 19-05-2004 23:15, Michiel Toneman wrote: We were having severe memory problems too with 5.0.19. Does Tomcat 5.0.24 fix this problem? We added this to the jk2.properties: request.registerRequests=false and the memory usage was normal again. Somewhat non-obvious, I agree. It also gets rid of Error registering request messages in catalina.out. We are using mod_jk (1.2) with Apache 1.3.x on Sun Solaris and Linux. Do you have to add the setting even if you are using jk 1.2 (not jk 2)? Someone could answer this question, please? Becouse my available memory is going down from 120 to 50 and to 10 megabytes to fast. And I'm not finding any leak in my apps... Below is the memory profile of one of our servers before and after the change (old generation memory refers to the memory buckets in the garbage collector. For more information, see jvmstat. At 100% you will start getting OutOfMemory errors): How do you get the memory profile? Is it a Tomcat command? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181 - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak with Tomcat 5.0.19
Brian Beckham wrote: Ok, after adding that setting in jk2.properties I have had 2 lockups of tomcat on my production siteany help!!?!!? lockup doesn't mean anything to me. Details please :) Also, this property cannot possibly cause that (look in the code if in doubt). -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Memory leak with Tomcat 5.0.19
Sorry bout that...got a little flustered :) Some more details...tomcat non-responsive, but JVM still running ps -ef showed several java processes still running, several defunct - Running with following: LD_ASSUME_KERNEL=2.2.5 CATALINA_HOME=/opt/jakarta-tomcat-5.0.19 JAVA_HOME=/opt/j2sdk1.4.2_04 CATALINA_OPTS=-server -Xms256m -Xmx1024m -Djava.awt.headless=true error file created (attached): Unexpected Signal : 11 occurred at PC=0x3FC6AC09 Function=(null)+0x3FC6AC09 Library=/opt/j2sdk1.4.2_04/jre/lib/i386/server/libjvm.so NOTE: We are unable to locate the function name symbol for the error just occurred. Please refer to release documentation for possible reason and solutions. Current Java thread: at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353) - locked 0x7b528488 (a java.net.PlainSocketImpl) at java.net.ServerSocket.implAccept(ServerSocket.java:448) at java.net.ServerSocket.accept(ServerSocket.java:419) at org.apache.catalina.core.StandardServer.await(StandardServer.java:551) at org.apache.catalina.startup.Catalina.await(Catalina.java:657) at org.apache.catalina.startup.Catalina.start(Catalina.java:617) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:297) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:398) System was at about 128 MB when crash occurred. Brian Beckham [EMAIL PROTECTED] Office: 770.924.6444 ext. 203 Mobile: 404.406.8355 -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Friday, May 21, 2004 10:21 AM To: Tomcat Users List Subject: Re: Memory leak with Tomcat 5.0.19 Brian Beckham wrote: Ok, after adding that setting in jk2.properties I have had 2 lockups of tomcat on my production siteany help!!?!!? lockup doesn't mean anything to me. Details please :) Also, this property cannot possibly cause that (look in the code if in doubt). -- x Rémy Maucherat Developer Consultant JBoss Group (Europe) SàRL x - 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: Memory leak with Tomcat 5.0.19
Hmm, signal 11's are bad news and usually not related to OutOfMemory problems. There is a dated, but pretty good explanation at: http://www.bitwizard.nl/sig11/ Michiel Brian Beckham wrote: Sorry bout that...got a little flustered :) Some more details...tomcat non-responsive, but JVM still running ps -ef showed several java processes still running, several defunct - Running with following: LD_ASSUME_KERNEL=2.2.5 CATALINA_HOME=/opt/jakarta-tomcat-5.0.19 JAVA_HOME=/opt/j2sdk1.4.2_04 CATALINA_OPTS=-server -Xms256m -Xmx1024m -Djava.awt.headless=true error file created (attached): Unexpected Signal : 11 occurred at PC=0x3FC6AC09 Function=(null)+0x3FC6AC09 Library=/opt/j2sdk1.4.2_04/jre/lib/i386/server/libjvm.so NOTE: We are unable to locate the function name symbol for the error just occurred. Please refer to release documentation for possible reason and solutions. Current Java thread: at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353) - locked 0x7b528488 (a java.net.PlainSocketImpl) at java.net.ServerSocket.implAccept(ServerSocket.java:448) at java.net.ServerSocket.accept(ServerSocket.java:419) at org.apache.catalina.core.StandardServer.await(StandardServer.java:551) at org.apache.catalina.startup.Catalina.await(Catalina.java:657) at org.apache.catalina.startup.Catalina.start(Catalina.java:617) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:297) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:398) System was at about 128 MB when crash occurred. Brian Beckham [EMAIL PROTECTED] Office: 770.924.6444 ext. 203 Mobile: 404.406.8355 -Original Message- From: Remy Maucherat [mailto:[EMAIL PROTECTED] Sent: Friday, May 21, 2004 10:21 AM To: Tomcat Users List Subject: Re: Memory leak with Tomcat 5.0.19 Brian Beckham wrote: Ok, after adding that setting in jk2.properties I have had 2 lockups of tomcat on my production siteany help!!?!!? lockup doesn't mean anything to me. Details please :) Also, this property cannot possibly cause that (look in the code if in doubt). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Michiel Toneman Software Engineer Bibit Global Payment Services Regulierenring 10 3981 LB Bunnik [EMAIL PROTECTED] Tel. +31-30-6595168 Fax +31-30-6564464 http://www.bibit.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak with Tomcat 5.0.19
Brian Beckham wrote: Sorry bout that...got a little flustered :) I don't have any answers but I'd just like to chime in to say that I've had nearly identical problems when I was using 5.0.19. I've moved on to 5.0.24 now, but I found some error logs in one of my backups so I'm attaching them in case they might help. I think with both of these errors I was using j2sdk1.4.1 although I was having the same problem using 1.4.2 too. -- Jeff Hoffmann PropertyKey.com Unexpected Signal : 11 occurred at PC=0x403647F4 Function=(null)+0x403647F4 Library=/usr/java/j2sdk1.4.1/jre/lib/i386/server/libjvm.so NOTE: We are unable to locate the function name symbol for the error just occurred. Please refer to release documentation for possible reason and solutions. Current Java thread: at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353) - locked 0x49fcd1c0 (a java.net.PlainSocketImpl) at java.net.ServerSocket.implAccept(ServerSocket.java:439) at java.net.ServerSocket.accept(ServerSocket.java:410) at org.apache.jk.common.ChannelSocket.accept(ChannelSocket.java:312) at org.apache.jk.common.ChannelSocket.acceptConnections(ChannelSocket.java:613) at org.apache.jk.common.SocketAcceptor.runIt(ChannelSocket.java:810) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:688) at java.lang.Thread.run(Thread.java:536) Dynamic libraries: 08048000-0804e000 r-xp 03:04 817673 /usr/java/j2sdk1.4.1/bin/java 0804e000-0804f000 rw-p 5000 03:04 817673 /usr/java/j2sdk1.4.1/bin/java 4000-40013000 r-xp 03:04 1602502/lib/ld-2.2.5.so 40013000-40014000 rw-p 00013000 03:04 1602502/lib/ld-2.2.5.so 40014000-40017000 r--s 03:04 1144706 /usr/java/j2sdk1.4.1/jre/lib/ext/dnsns.jar 40017000-40018000 r--s 03:04 801367 /home/iris/tomcat-5.0.19/common/lib/naming-java.jar 40018000-40025000 r-xp 03:04 2371049/lib/i686/libpthread-0.9.so 40025000-4002c000 rw-p d000 03:04 2371049/lib/i686/libpthread-0.9.so 4002d000-4002f000 r-xp 03:04 1602515/lib/libdl-2.2.5.so 4002f000-4003 rw-p 1000 03:04 1602515/lib/libdl-2.2.5.so 4003-404c8000 r-xp 03:04 883027 /usr/java/j2sdk1.4.1/jre/lib/i386/server/libjvm.so 404c8000-406d4000 rw-p 00497000 03:04 883027 /usr/java/j2sdk1.4.1/jre/lib/i386/server/libjvm.so 406e6000-406f8000 r-xp 03:04 1602519/lib/libnsl-2.2.5.so 406f8000-406f9000 rw-p 00012000 03:04 1602519/lib/libnsl-2.2.5.so 406fb000-4071c000 r-xp 03:04 2371047/lib/i686/libm-2.2.5.so 4071c000-4071d000 rw-p 0002 03:04 2371047/lib/i686/libm-2.2.5.so 4071d000-40726000 r-xp 03:04 359767 /usr/java/j2sdk1.4.1/jre/lib/i386/native_threads/libhpi.so 40726000-40727000 rw-p 8000 03:04 359767 /usr/java/j2sdk1.4.1/jre/lib/i386/native_threads/libhpi.so 40728000-40738000 r-xp 03:04 245402 /usr/java/j2sdk1.4.1/jre/lib/i386/libverify.so 40738000-4073a000 rw-p f000 03:04 245402 /usr/java/j2sdk1.4.1/jre/lib/i386/libverify.so 4073a000-4075b000 r-xp 03:04 245403 /usr/java/j2sdk1.4.1/jre/lib/i386/libjava.so 4075b000-4075d000 rw-p 0002 03:04 245403 /usr/java/j2sdk1.4.1/jre/lib/i386/libjava.so 4075d000-40772000 r-xp 03:04 245405 /usr/java/j2sdk1.4.1/jre/lib/i386/libzip.so 40772000-40774000 rw-p 00014000 03:04 245405 /usr/java/j2sdk1.4.1/jre/lib/i386/libzip.so 40774000-4085f000 r--s 03:04 212729 /home/iris/tomcat-5.0.19/common/endorsed/xercesImpl.jar 4085f000-4087e000 r--s 03:04 212730 /home/iris/tomcat-5.0.19/common/endorsed/xmlParserAPIs.jar 4087e000-41f4c000 r--s 03:04 1373665/usr/java/j2sdk1.4.1/jre/lib/rt.jar 41f8f000-41fa6000 r--s 03:04 1373645 /usr/java/j2sdk1.4.1/jre/lib/sunrsasign.jar 41fa6000-41fb9000 r--s 03:04 1373646/usr/java/j2sdk1.4.1/jre/lib/jce.jar 41fe1000-41fe7000 r--s 03:04 2354875/usr/lib/gconv/gconv-modules.cache 41fe7000-41ff r-xp 03:04 1602535/lib/libnss_files-2.2.5.so 41ff-41ff1000 rw-p 9000 03:04 1602535/lib/libnss_files-2.2.5.so 41ff1000-41fff000 r--s 03:04 1144708 /usr/java/j2sdk1.4.1/jre/lib/ext/ldapsec.jar 41fff000-4200 r--s 03:04 1782607 /home/iris/tomcat-5.0.19/server/lib/jkshm.jar 4200-4212c000 r-xp 03:04 2371045/lib/i686/libc-2.2.5.so 4212c000-42131000 rw-p 0012c000 03:04 2371045/lib/i686/libc-2.2.5.so 42135000-421a6000 r--s 03:04 1373647/usr/java/j2sdk1.4.1/jre/lib/jsse.jar 421a6000-42462000 r--s 03:04 1373663 /usr/java/j2sdk1.4.1/jre/lib/charsets.jar 444e2000-444e8000 r--s 03:04 2076877 /home/iris/tomcat-5.0.19/bin/bootstrap.jar 444e8000-444eb000 r--s 03:04 2076880
RE: Memory leak with Tomcat 5.0.19
Jeff, Can you tell me more about your sitation? Did 5.0.24 help? What options were you setting? Were you using / are you using jsvc? What OS? Brian Beckham [EMAIL PROTECTED] Office: 770.924.6444 ext. 203 Mobile: 404.406.8355 -Original Message- From: Jeff Hoffmann [mailto:[EMAIL PROTECTED] Sent: Friday, May 21, 2004 10:54 AM To: Tomcat Users List Subject: Re: Memory leak with Tomcat 5.0.19 Brian Beckham wrote: Sorry bout that...got a little flustered :) I don't have any answers but I'd just like to chime in to say that I've had nearly identical problems when I was using 5.0.19. I've moved on to 5.0.24 now, but I found some error logs in one of my backups so I'm attaching them in case they might help. I think with both of these errors I was using j2sdk1.4.1 although I was having the same problem using 1.4.2 too. -- Jeff Hoffmann PropertyKey.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak with Tomcat 5.0.19
Brian Beckham wrote: Jeff, Can you tell me more about your sitation? Did 5.0.24 help? So far I haven't had any problems with 5.0.24, although I've only been running it a couple of days. When I had the problem with 5.0.19, I jumped back to 5.0.16 until a couple of days ago when I went up to 5.0.24. What options were you setting? They were essentially the same. My initial memory was set to 128M and max memory was set to 512M but I never maxed out the memory before the crash. I was using server VM and set the headless property. Were you using / are you using jsvc? No. What OS? It's mostly Redhat Hat 7.3 with kernel 2.4.20-20.7smp. I've used both of the following java environments and saw the same problem with both: Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-b21) Java HotSpot(TM) Client VM (build 1.4.1-b21, mixed mode) Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05) Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode) I don't know what else you'd like to know. I'm not running that version any more so it'd be kind of hard for me to test things but I'd be glad to tell you what I can remember from when I was. Like I said, I never found an answer but I wanted to corroborate in case somebody was inclined to dismiss it as a one-off problem. -- Jeff Hoffmann PropertyKey.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak with Tomcat 5.0.19
On 19-05-2004 23:15, Michiel Toneman wrote: We were having severe memory problems too with 5.0.19. Does Tomcat 5.0.24 fix this problem? We added this to the jk2.properties: request.registerRequests=false and the memory usage was normal again. Somewhat non-obvious, I agree. It also gets rid of Error registering request messages in catalina.out. We are using mod_jk (1.2) with Apache 1.3.x on Sun Solaris and Linux. Do you have to add the setting even if you are using jk 1.2 (not jk 2)? Below is the memory profile of one of our servers before and after the change (old generation memory refers to the memory buckets in the garbage collector. For more information, see jvmstat. At 100% you will start getting OutOfMemory errors): How do you get the memory profile? Is it a Tomcat command? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak with Tomcat 5.0.19
wsedio wrote: On 19-05-2004 23:15, Michiel Toneman wrote: We were having severe memory problems too with 5.0.19. Does Tomcat 5.0.24 fix this problem? We added this to the jk2.properties: request.registerRequests=false and the memory usage was normal again. Somewhat non-obvious, I agree. It also gets rid of Error registering request messages in catalina.out. We are using mod_jk (1.2) with Apache 1.3.x on Sun Solaris and Linux. Do you have to add the setting even if you are using jk 1.2 (not jk 2)? Someone could answer this question, please? Becouse my available memory is going down from 120 to 50 and to 10 megabytes to fast. And I'm not finding any leak in my apps... Below is the memory profile of one of our servers before and after the change (old generation memory refers to the memory buckets in the garbage collector. For more information, see jvmstat. At 100% you will start getting OutOfMemory errors): How do you get the memory profile? Is it a Tomcat command? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak with Tomcat 5.0.19
Someone could answer this question, please? Becouse my available memory is going down from 120 to 50 and to 10 megabytes to fast. And I'm not finding any leak in my apps... Sorry if I looked rude, didn't mean that :P Maybe this leak is solved in tomcat 5.0.24?? Emerson Cargnin wrote: wsedio wrote: On 19-05-2004 23:15, Michiel Toneman wrote: We were having severe memory problems too with 5.0.19. Does Tomcat 5.0.24 fix this problem? We added this to the jk2.properties: request.registerRequests=false and the memory usage was normal again. Somewhat non-obvious, I agree. It also gets rid of Error registering request messages in catalina.out. We are using mod_jk (1.2) with Apache 1.3.x on Sun Solaris and Linux. Do you have to add the setting even if you are using jk 1.2 (not jk 2)? Below is the memory profile of one of our servers before and after the change (old generation memory refers to the memory buckets in the garbage collector. For more information, see jvmstat. At 100% you will start getting OutOfMemory errors): How do you get the memory profile? Is it a Tomcat command? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Memory leak with Tomcat 5.0.19
Hi, What if your webapp actually requires more than 120MB of memory under your load? Yoav Shapira Millennium Research Informatics -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Thursday, May 20, 2004 1:09 PM To: Tomcat Users List Subject: Re: Memory leak with Tomcat 5.0.19 wsedio wrote: On 19-05-2004 23:15, Michiel Toneman wrote: We were having severe memory problems too with 5.0.19. Does Tomcat 5.0.24 fix this problem? We added this to the jk2.properties: request.registerRequests=false and the memory usage was normal again. Somewhat non-obvious, I agree. It also gets rid of Error registering request messages in catalina.out. We are using mod_jk (1.2) with Apache 1.3.x on Sun Solaris and Linux. Do you have to add the setting even if you are using jk 1.2 (not jk 2)? Someone could answer this question, please? Becouse my available memory is going down from 120 to 50 and to 10 megabytes to fast. And I'm not finding any leak in my apps... Below is the memory profile of one of our servers before and after the change (old generation memory refers to the memory buckets in the garbage collector. For more information, see jvmstat. At 100% you will start getting OutOfMemory errors): How do you get the memory profile? Is it a Tomcat command? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] 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: Memory leak with Tomcat 5.0.19
Our load is very low, and all the new app deployed after changing to 5.0.19 was tested (undeployed to see if mem usage get lower) and I didn't find any other clue. I think I'll have to profile it... hope to find the hole ;P thanks anyway Emerson Shapira, Yoav wrote: Hi, What if your webapp actually requires more than 120MB of memory under your load? Yoav Shapira Millennium Research Informatics -Original Message- From: Emerson Cargnin [mailto:[EMAIL PROTECTED] Sent: Thursday, May 20, 2004 1:09 PM To: Tomcat Users List Subject: Re: Memory leak with Tomcat 5.0.19 wsedio wrote: On 19-05-2004 23:15, Michiel Toneman wrote: We were having severe memory problems too with 5.0.19. Does Tomcat 5.0.24 fix this problem? We added this to the jk2.properties: request.registerRequests=false and the memory usage was normal again. Somewhat non-obvious, I agree. It also gets rid of Error registering request messages in catalina.out. We are using mod_jk (1.2) with Apache 1.3.x on Sun Solaris and Linux. Do you have to add the setting even if you are using jk 1.2 (not jk 2)? Someone could answer this question, please? Becouse my available memory is going down from 120 to 50 and to 10 megabytes to fast. And I'm not finding any leak in my apps... Below is the memory profile of one of our servers before and after the change (old generation memory refers to the memory buckets in the garbage collector. For more information, see jvmstat. At 100% you will start getting OutOfMemory errors): How do you get the memory profile? Is it a Tomcat command? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] 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] -- Emerson Cargnin Analista de Sistemas Setor de Desenvolvimento de Sistemas - TRE-SC tel : (048) - 251-3700 - Ramal 3181 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak with Tomcat 5.0.19
We were having severe memory problems too with 5.0.19. We added this to the jk2.properties: request.registerRequests=false and the memory usage was normal again. Somewhat non-obvious, I agree. It also gets rid of Error registering request messages in catalina.out. We are using mod_jk (1.2) with Apache 1.3.x on Sun Solaris and Linux. Below is the memory profile of one of our servers before and after the change (old generation memory refers to the memory buckets in the garbage collector. For more information, see jvmstat. At 100% you will start getting OutOfMemory errors): before: 20040427-01:03: Using 0% of available old generation memory (853 Mb total) 20040427-13:03: Using 11% of available old generation memory (853 Mb total) 20040428-01:03: Using 13% of available old generation memory (853 Mb total) 20040428-13:03: Using 18% of available old generation memory (853 Mb total) 20040429-01:03: Using 20% of available old generation memory (853 Mb total) 20040429-13:03: Using 25% of available old generation memory (853 Mb total) 20040430-01:03: Using 26% of available old generation memory (853 Mb total) 20040430-13:03: Using 30% of available old generation memory (853 Mb total) 20040501-01:03: Using 32% of available old generation memory (853 Mb total) 20040501-13:03: Using 37% of available old generation memory (853 Mb total) 20040502-01:03: Using 44% of available old generation memory (853 Mb total) 20040502-13:03: Using 51% of available old generation memory (853 Mb total) 20040503-01:03: Using 57% of available old generation memory (853 Mb total) 20040503-13:03: Using 64% of available old generation memory (853 Mb total) 20040504-01:03: Using 65% of available old generation memory (853 Mb total) 20040504-13:03: Using 70% of available old generation memory (853 Mb total) 20040505-01:03: Using 72% of available old generation memory (853 Mb total) 20040505-13:03: Using 76% of available old generation memory (853 Mb total) 20040506-01:03: Using 78% of available old generation memory (853 Mb total) Tomcat restarted at 81% after: 20040506-13:03: Using 0% of available old generation memory (853 Mb total) 20040507-01:03: Using 2% of available old generation memory (853 Mb total) 20040507-13:03: Using 2% of available old generation memory (853 Mb total) 20040508-01:03: Using 2% of available old generation memory (853 Mb total) 20040508-13:03: Using 2% of available old generation memory (853 Mb total) 20040509-01:03: Using 2% of available old generation memory (853 Mb total) 20040509-13:03: Using 2% of available old generation memory (853 Mb total) 20040510-01:03: Using 2% of available old generation memory (853 Mb total) 20040510-13:03: Using 2% of available old generation memory (853 Mb total) 20040511-01:03: Using 3% of available old generation memory (853 Mb total) 20040511-11:03: Using 3% of available old generation memory (853 Mb total) 20040512-01:03: Using 4% of available old generation memory (853 Mb total) Tomcat restarted due to system upgrade. Cheers, Michiel Brian Beckham wrote: I have a site that gets a fair amount of traffic - roughly 300,000 page views per day - a mix of servlets and JSP The site runs on 3 separate servers - one of which we upgraded to Tomcat 5.0.19. We have been running the site successfully for the past year using Tomcat 4.1.x, and 2 of the servers are still running Tomcat 4.1.x and are fine. Other differences between the two 4.1.x machines and the Tomcat 5.0.19 machine include: - Tomcat 5.0.19 machine uses jk2 / tomcat 4.1.x servers use mod_jk - Tomcat 5.0.19 machine using jsvc The Tomcat 5.0.19 machine is leaking memory at an alarming rate. I am using the following options on all: -Xms256 -Xmx1024 The Tomcat 4.1.x machines all run the site and stay around 350MB, but the Tomcat 5.x machine grows until the JVM runs out of memory. The sites are using DBCP, and connecting to an Oracle 10g RAC cluster using the newest JDBC Thin drivers from Oracle (same on all 3). I plan on running a profiler on the system, but thought I would perform a sanity check and make sure I am not missing something obvious (to someone else). Thanks, Brian Beckham [EMAIL PROTECTED] Office: 770.924.6444 ext. 203 Mobile: 404.406.8355 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Memory leak with Tomcat 5.0.19
http://marc.theaimsgroup.com/?l=tomcat-userm=108304447126396w=2 ? -Original Message- From: Brian Beckham [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 19, 2004 3:36 PM To: Tomcat Users List Subject: Memory leak with Tomcat 5.0.19 I have a site that gets a fair amount of traffic - roughly 300,000 page views per day - a mix of servlets and JSP The site runs on 3 separate servers - one of which we upgraded to Tomcat 5.0.19. We have been running the site successfully for the past year using Tomcat 4.1.x, and 2 of the servers are still running Tomcat 4.1.x and are fine. Other differences between the two 4.1.x machines and the Tomcat 5.0.19 machine include: - Tomcat 5.0.19 machine uses jk2 / tomcat 4.1.x servers use mod_jk - Tomcat 5.0.19 machine using jsvc The Tomcat 5.0.19 machine is leaking memory at an alarming rate. I am using the following options on all: -Xms256 -Xmx1024 The Tomcat 4.1.x machines all run the site and stay around 350MB, but the Tomcat 5.x machine grows until the JVM runs out of memory. The sites are using DBCP, and connecting to an Oracle 10g RAC cluster using the newest JDBC Thin drivers from Oracle (same on all 3). I plan on running a profiler on the system, but thought I would perform a sanity check and make sure I am not missing something obvious (to someone else). Thanks, Brian Beckham [EMAIL PROTECTED] Office: 770.924.6444 ext. 203 Mobile: 404.406.8355 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak with Tomcat 5.0.19
We are runnning Tomcat 5.0.19 and experiencing the same problems. This is what we defined for the memory. Our tomcat is crawling at this point. We have to restart it everyday. CATALINA_OPTS=$CATALINA_OPTS -server -Xms1152M -Xmx1536M - Xincgc Thanks, Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: memory leak in tomcat 5.0.16 ?
Thanks, I will upgrade to 5.0.18 and see if it works ! /Torstein -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: 22. januar 2004 11:44 To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? We had exactly the same problem. 2 users on 5.0.16 after 20 minutes the RAM consumed was 158MB and then it crashed. Upgraded to 5.0.18 yesterday and RAM is a steady 30MB. I dont care what anyone says, 5.0.16 had a problem! -Original Message- From: Francois JEANMOUGIN [mailto:[EMAIL PROTECTED] Sent: 22 January 2004 10:19 To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? -Original Message- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 11:05 AM To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? There is a known memory leak in 5.0.16, I'd upgrade to 5.0.18 and see if this fixes your problem. Note that the download page on Jakarta.apache.org is not updated with this new release. You need to figure the good URL by yourself (not so hard). François. -- --- 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: memory leak in tomcat 5.0.16 ?
There is a known memory leak in 5.0.16, I'd upgrade to 5.0.18 and see if this fixes your problem. Ta Matt -Original Message- From: Torstein Nilsen [mailto:[EMAIL PROTECTED] Sent: 22 January 2004 10:01 To: [EMAIL PROTECTED] Subject: memory leak in tomcat 5.0.16 ? I am developing an intranet for a housing community using apache/tomcat and mysql. It was put in production to 200 users a few weeks ago and I noticed that the java-proces (tomcat) was growing from 8% memory usage when started to over 50% (seen with top / ps aux). When the mem-usage reach a certain level the java-proces uses most of the CPU- ressources as well - verbose:GC showed that this is the GC trying to keep up. This usually happens in a matter of 2-5 hours depending on the Xmx-settings - the number of active users / load seems to speed the process up (not confirmed). Restarting tomcat solves the problem for a while - but I would prefer a better permament solution. System settings: CPU: Pentium 1600 mhz RAM: 512 MB OS: Linux (Redhat) Java: j2re1.4.2_03 / jikes TOMCAT: 5.0.16 Connector: org.apache.coyote.tomcat5.CoyoteConnector (AJP/1.3) CATALINA_OPTS: -Xmx200m -Xms200m -Dbuild.compiler.emacs=true (have tried 117 different settings) At first I used tomcat 4 and j2sdk1.4.1_03 and the normal javac-compiler. I changed to jakarta-tomcat-5.0.16 / j2re1.4.2_03 and jikes - this seems to have made the problem even worse. Before the update tomcat could go for more than 12 hours whitout restarting - now I have to restart every few hours. The application is quite DB-intensive: Every 30 secs. a java-thread queries a mysql-table with updated network-traffic data (used for traffic-shaping). In the same loop I SAX-parse a little XML-string using the JDOM-API (I have read about the StringBuffer-problem but this is not the cause since I'm now using j2re1.4.2_03 - right ?). I'm using mysql-connector-3.0.9 as JDBC-driver and protomatter-1.1.8 to pool DB-connections. In the same loop I connect to a TCP- socket on the local server. I have done some profiling with HPJmeter and the -Xrunhprof argument with different settings. I'm a newbie in profiling but these observations might be useful: -Using HPJmeter' guess memory leaks the top-4 suggested candidates are: java.util.vector, org.apache.commons.modeler.Registry, org.apache.jk.core.MsgContext and org.apache.coyote.Request -Residual objects shows the following top-4-classes (bytes): int[] (10 MB) char[] (4 MB) java.lang.String (2 MB) byte[] (2 MB) Any help would be much appreciated... Regards Torstein Nilsen - 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: memory leak in tomcat 5.0.16 ?
Dale, Matt wrote: There is a known memory leak in 5.0.16, I'd upgrade to 5.0.18 and see if this fixes your problem. You should read his report. 1) I don't see how he would be affected, since he seems to have a rather small server; you need large variations in traffic to get the leak (and the workaround is easy enough anyway) 2) He's using AJP, not HTTP ;) I am developing an intranet for a housing community using apache/tomcat and mysql. It was put in production to 200 users a few weeks ago and I noticed that the java-proces (tomcat) was growing from 8% memory usage when started to over 50% (seen with top / ps aux). When the mem-usage reach a certain level the java-proces uses most of the CPU- ressources as well - verbose:GC showed that this is the GC trying to keep up. This usually happens in a matter of 2-5 hours depending on the Xmx-settings - the number of active users / load seems to speed the process up (not confirmed). Restarting tomcat solves the problem for a while - but I would prefer a better permament solution. System settings: CPU: Pentium 1600 mhz RAM: 512 MB OS: Linux (Redhat) Java: j2re1.4.2_03 / jikes TOMCAT: 5.0.16 Connector: org.apache.coyote.tomcat5.CoyoteConnector (AJP/1.3) CATALINA_OPTS: -Xmx200m -Xms200m -Dbuild.compiler.emacs=true (have tried 117 different settings) At first I used tomcat 4 and j2sdk1.4.1_03 and the normal javac-compiler. I changed to jakarta-tomcat-5.0.16 / j2re1.4.2_03 and jikes - this seems to have made the problem even worse. Before the update tomcat could go for more than 12 hours whitout restarting - now I have to restart every few hours. The application is quite DB-intensive: Every 30 secs. a java-thread queries a mysql-table with updated network-traffic data (used for traffic-shaping). In the same loop I SAX-parse a little XML-string using the JDOM-API (I have read about the StringBuffer-problem but this is not the cause since I'm now using j2re1.4.2_03 - right ?). I'm using mysql-connector-3.0.9 as JDBC-driver and protomatter-1.1.8 to pool DB-connections. In the same loop I connect to a TCP- socket on the local server. I have done some profiling with HPJmeter and the -Xrunhprof argument with different settings. I'm a newbie in profiling but these observations might be useful: -Using HPJmeter' guess memory leaks the top-4 suggested candidates are: java.util.vector, org.apache.commons.modeler.Registry, org.apache.jk.core.MsgContext and org.apache.coyote.Request -Residual objects shows the following top-4-classes (bytes): int[] (10 MB) char[] (4 MB) java.lang.String (2 MB) byte[] (2 MB) Any help would be much appreciated... Regards Torstein Nilsen -- 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: memory leak in tomcat 5.0.16 ?
-Original Message- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 11:05 AM To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? There is a known memory leak in 5.0.16, I'd upgrade to 5.0.18 and see if this fixes your problem. Note that the download page on Jakarta.apache.org is not updated with this new release. You need to figure the good URL by yourself (not so hard). François. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: memory leak in tomcat 5.0.16 ?
We had exactly the same problem. 2 users on 5.0.16 after 20 minutes the RAM consumed was 158MB and then it crashed. Upgraded to 5.0.18 yesterday and RAM is a steady 30MB. I dont care what anyone says, 5.0.16 had a problem! -Original Message- From: Francois JEANMOUGIN [mailto:[EMAIL PROTECTED] Sent: 22 January 2004 10:19 To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? -Original Message- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 11:05 AM To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? There is a known memory leak in 5.0.16, I'd upgrade to 5.0.18 and see if this fixes your problem. Note that the download page on Jakarta.apache.org is not updated with this new release. You need to figure the good URL by yourself (not so hard). François. - 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: memory leak in tomcat 5.0.16 ?
Francois JEANMOUGIN wrote: There is a known memory leak in 5.0.16, I'd upgrade to 5.0.18 and see if this fixes your problem. Note that the download page on Jakarta.apache.org is not updated with this new release. You need to figure the good URL by yourself (not so hard). Before announcing something, one has to wait for: - voting to complete - mirrors to replicate the build -- 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: memory leak in tomcat 5.0.16 ?
Out of curiosity, which JVM do you run? I run Tomcat 5.0.18, JVM 1.4.2_03 for Linux on Red Hat, and two instances of JSPWiki serving no more than 200 users. This combination consumes a steady 121MB. Is this normal or excessive? Derek -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: January 22, 2004 5:44 AM To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? We had exactly the same problem. 2 users on 5.0.16 after 20 minutes the RAM consumed was 158MB and then it crashed. Upgraded to 5.0.18 yesterday and RAM is a steady 30MB. I dont care what anyone says, 5.0.16 had a problem! -Original Message- From: Francois JEANMOUGIN [mailto:[EMAIL PROTECTED] Sent: 22 January 2004 10:19 To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? -Original Message- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 11:05 AM To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? There is a known memory leak in 5.0.16, I'd upgrade to 5.0.18 and see if this fixes your problem. Note that the download page on Jakarta.apache.org is not updated with this new release. You need to figure the good URL by yourself (not so hard). François. - 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: memory leak in tomcat 5.0.16 ?
1.4.1_03 on W2K. I have no idea what the consumption of memory should be like but previous posts where I mentioned this about of RAM have had replies saying it was a lot. Depends on what you app does I guess. Ours has a real large XML nav tree in app scope that is used a lot on each request, we have a backend CMS to get search results for thousands of docs and all their meta data gets stored in properties files and we also do lots with the SQL server. At the moment all that is down to 30MB as shown in JProfiler's heap used view. What puzzles me is the Windows task manager process memory as this never ever matches anywhere near the JProfiler reported memory. I know there may be some system overheads but the 30MB heap that JProfiler reveals is actually 90MB in Windows task manager. Go figure? -Original Message- From: Derek Mahar [mailto:[EMAIL PROTECTED] Sent: 22 January 2004 14:58 To: Tomcat Users List Cc: [EMAIL PROTECTED] Subject: RE: memory leak in tomcat 5.0.16 ? Out of curiosity, which JVM do you run? I run Tomcat 5.0.18, JVM 1.4.2_03 for Linux on Red Hat, and two instances of JSPWiki serving no more than 200 users. This combination consumes a steady 121MB. Is this normal or excessive? Derek -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: January 22, 2004 5:44 AM To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? We had exactly the same problem. 2 users on 5.0.16 after 20 minutes the RAM consumed was 158MB and then it crashed. Upgraded to 5.0.18 yesterday and RAM is a steady 30MB. I dont care what anyone says, 5.0.16 had a problem! -Original Message- From: Francois JEANMOUGIN [mailto:[EMAIL PROTECTED] Sent: 22 January 2004 10:19 To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? -Original Message- From: Dale, Matt [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 11:05 AM To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? There is a known memory leak in 5.0.16, I'd upgrade to 5.0.18 and see if this fixes your problem. Note that the download page on Jakarta.apache.org is not updated with this new release. You need to figure the good URL by yourself (not so hard). François. - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: memory leak in tomcat 5.0.16 ?
The heap size has nothing to do with the memory size that is seen by the system. You have to look at least at the total memory. (That is used + free memory) To that you have to add - thread stacks (At least some vm's don't allocate them on the heap) - static memory (Like the jvm itself, static strings, classes, jars, ...) - some os memory that is used by the vm to manage it self - ... I wouldn't expect that the diff between total memory and system memory is more than a few megs. (Far less than 30MB) -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 4:06 PM To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? What puzzles me is the Windows task manager process memory as this never ever matches anywhere near the JProfiler reported memory. I know there may be some system overheads but the 30MB heap that JProfiler reveals is actually 90MB in Windows task manager. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: memory leak in tomcat 5.0.16 ?
try setting maxSpareThreads==minSpareThreads==maxThreads in your connector, Filip - Original Message - From: Ralph Einfeldt [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, January 22, 2004 7:18 AM Subject: RE: memory leak in tomcat 5.0.16 ? The heap size has nothing to do with the memory size that is seen by the system. You have to look at least at the total memory. (That is used + free memory) To that you have to add - thread stacks (At least some vm's don't allocate them on the heap) - static memory (Like the jvm itself, static strings, classes, jars, ...) - some os memory that is used by the vm to manage it self - ... I wouldn't expect that the diff between total memory and system memory is more than a few megs. (Far less than 30MB) -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 4:06 PM To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? What puzzles me is the Windows task manager process memory as this never ever matches anywhere near the JProfiler reported memory. I know there may be some system overheads but the 30MB heap that JProfiler reveals is actually 90MB in Windows task manager. - 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: memory leak in tomcat 5.0.16 ?
I have now upgraded to the latest tomcat release 5.0.18 but I'm afraid this didn't solve the problem - the tomcat-process is still growing. I have monitored the ressources used very closely with 5.0.18 and it shows a slow grow in mem-usage a couple of hours and then suddenly in a matter of ca. 10 secs. it goes from 15% to 40% of total memory and stays there. Tomcat access log-files doesn't show extrordinary activity during the bloat. Thanx anyway. I will try the max / min threads and see if this helps. Torstein -Original Message- From: Filip Hanik [mailto:[EMAIL PROTECTED] Sent: 22. januar 2004 18:58 To: Tomcat Users List Subject: Re: memory leak in tomcat 5.0.16 ? try setting maxSpareThreads==minSpareThreads==maxThreads in your connector, Filip - Original Message - From: Ralph Einfeldt [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, January 22, 2004 7:18 AM Subject: RE: memory leak in tomcat 5.0.16 ? The heap size has nothing to do with the memory size that is seen by the system. You have to look at least at the total memory. (That is used + free memory) To that you have to add - thread stacks (At least some vm's don't allocate them on the heap) - static memory (Like the jvm itself, static strings, classes, jars, ...) - some os memory that is used by the vm to manage it self - ... I wouldn't expect that the diff between total memory and system memory is more than a few megs. (Far less than 30MB) -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 4:06 PM To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? What puzzles me is the Windows task manager process memory as this never ever matches anywhere near the JProfiler reported memory. I know there may be some system overheads but the 30MB heap that JProfiler reveals is actually 90MB in Windows task manager. -- --- 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: memory leak in tomcat 5.0.16 ?
On Thu, January 22, 2004 1at 0:25 am, Torstein Nilsen wrote: I have now upgraded to the latest tomcat release 5.0.18 but I'm afraid this didn't solve the problem - the tomcat-process is still growing. I have monitored the ressources used very closely with 5.0.18 and it shows a slow grow in mem-usage a couple of hours and then suddenly in a matter of ca. 10 secs. it goes from 15% to 40% of total memory and stays there. Tomcat access log-files doesn't show extrordinary activity during the bloat. Sounds like you're going to need to get a profiler to figure out where the memory is being used. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
