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]
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: Suspected memory leak in Tomcat or JVM?
There are some memory leaks in the AJP/1.3 Connector (e.g. http://issues.apache.org/bugzilla/show_bug.cgi?id=32141), but the CVS logs say that these were introduced after 4.1.27. Jochen Wiedmann [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hi, we have an elder application running on Tomcat 4.1.27 with Java 1.4.2_08 on Sparc Solaris 8. Recently we moved the application to a new machine running on Sparc Solaris 9. Since then we have a serious memory problem and need to restart the same application twice a day. One minor change: We are now using mod_jk 1.2.14 and no longer mod_proxy. As I am unaware of any serious heap profiler that is fast enough for production use, I decided to try the very simple heap profiler from http://www.virtualmachine.de/. I made a dump after starting the application and before shutting down. The results were (to me) quite surprising: The main difference was in the following numbers: At startBefore shutdown Objects Size Objects Size [byte5638 6M160796569M [char 3006402 195M 3211457418M ByteChunk62 2K 345450 14M CharChunk 46 2K 324080 13M (With ByteChunk and CharChunk being from the org.apache.tomcat.util.buf package.) To me, this numbers seem to be related. Any ideas? Regards, Jochen -- Having experienced 7 years of labour/green government, I now know the reason, why a conservative government is good for the economy: The economy's unable to imagine anything else ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Suspected memory leak in Tomcat or JVM?
Hi, we have an elder application running on Tomcat 4.1.27 with Java 1.4.2_08 on Sparc Solaris 8. Recently we moved the application to a new machine running on Sparc Solaris 9. Since then we have a serious memory problem and need to restart the same application twice a day. One minor change: We are now using mod_jk 1.2.14 and no longer mod_proxy. As I am unaware of any serious heap profiler that is fast enough for production use, I decided to try the very simple heap profiler from http://www.virtualmachine.de/. I made a dump after starting the application and before shutting down. The results were (to me) quite surprising: The main difference was in the following numbers: At startBefore shutdown Objects Size Objects Size [byte5638 6M160796569M [char 3006402 195M 3211457418M ByteChunk62 2K 345450 14M CharChunk 46 2K 324080 13M (With ByteChunk and CharChunk being from the org.apache.tomcat.util.buf package.) To me, this numbers seem to be related. Any ideas? Regards, Jochen -- Having experienced 7 years of labour/green government, I now know the reason, why a conservative government is good for the economy: The economy's unable to imagine anything else ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Memory leak in simple spring webapp
I'm deploying and then undeploying a very simple spring-based test app to my tomcat container. However, my WebappClassLoader never gets garbage collected, because tomcat objects (loaded by the StandardClassLoader) have hard references to the classes of my app. I've figured out / fixed a couple of these problems. For example if you have the xerces lib in your app, and not in tomcat's server/lib, the container will create instances of your app's xml parser. At the moment I'm looking at this nasty link of references: StandardClassLoader - org.apache.tomcat.util.IntrospectionUtils.objectMethods - Hashtable [30].key - org.springframework.beans.factory.BeanDefinitionStoreException. Unlike the beans introspector, the tomcat IntrospectionUtils has no 'flushCache' method. Any suggestions for how I get around this without making changes in IntrospectionUtils? From my basic understanding of these things, IntrospectionUtils should be using weak references in its class/method cache. Should I file this as a bug in IntrospectionUtils? -Magnus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
application memory leak
Hello,
May be it's some kind of stupid question, but where in tomcat
environment may be memory leak?
I can imagine three subjects:
- objects stored in application scope
- objects stored in session scope
- objects handled by static properties
Is there any other place where objects can be referenced from
and not to be gc'ed?
My situation:
Application eats about 40 kb on each request.
More precisely - about 200m on 5000 requests, as i have measured.
At start of an application I have about 100m of heap occupied.
After the next gc it's about 105, and so on - after about 5000
requests it's about 300 mb occupied.
I've examined all objects that are stored in application scope - so
their size do not change with growth of eaten memory.
Session can be relatively large, but there are about 150 sessions all
the time (their number does not grow uncontrollable).
By the way I removed from session any large objects - no change in
memory-leak-behaviour.
I've examined static properties too - there are no properties that can
grow (almost all - int and string constants)
I use tomcat 5.0.25 with all view pages in jsp, most controller work
done by struts actions.
In jsp relatively often I use construction
c:set var=html.../c:set
...
${html}
(pregenerate part of the page, use some data it produced
[such as custom title] and only then output html)
May it be memory bottleneck?..
May be it's necessary to avoid some kind of pooling of pageContext's
or String handlers (or even HttpRequest objects?) in Tomcat config?
BTW, is there any other well-known memory-leak issues?
--
Best regards,
Dmitrymailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Help with memory leak using Tomcat
Hi. There was a discussion on this topic on Hibernate forum: http://forum.hibernate.org/viewtopic.php?t=935948postdays=0postorder=ascstart=0 If you find how to solve it, please let us know - I'm currently having the same problem :). Regards, Sergey. sudip shrestha wrote: I have experienced similar kind of memory leak, but that was while reloading the context. There was a steady increase in the memory usage after each autoReload of my struts 1.2.7-hibernate 2.1.8 powered webApp in Tomcat 5.5.7/JDK 1.5/Fedora Core 2. At the beginning: the process memory used by tomcat was 6.6%, then after each reload it went on slight increase such as: 7.8%, 8.3%, 8.8%, 9.1%, 10.1%, 10.7%Then I shutdown the tomcat server and restarted the server, I saw the memory usage as 6.4%, then on the next reload the usage was 7.9%. Meanwhile, the Java memory ( Runtime.getRuntime().totalMemory() Runtime.getRuntime().freeMemory() ) seem to stay pretty stabilizedSo, basically only process memory is increasing...which tells me that there is a leak in native memory. I saw similar threads like this when somebody had memory leaks with application reload/startup/shutdown with Tomcat Manager webapp... I am also looking for a good direction to move ahead. On 6/10/05, Mark Thomas [EMAIL PROTECTED] wrote: Does your profiling tool tell you the classes of the objects being created? Can you take a snapshot at two points in time, compare them and see what is different? If we know the class of the objects being created, it gives us a pretty good pointer as to where to start looking. Without this information, it is needle in haystack time. If your profiler doesn't do this, you probably need to get a new profiler. Mark Ed Hamilton wrote: I posted something similar to the Tomcat bug list and was asked to move it here. My first mailing to this list, so please correct any gaffes on my part... I'm running Tomcat 5.5.9; isapi redirector 1.2.13; J2SE 1.5.0.03; JDBC 3.1.8a; to support 2 very low volume websites. I have some kind of memory leak which triples tomcat's memory usage over about 4-5 days. I downloaded and installed AppPerfect profiler, and it shows a steady, consistent increase in objects and a corresponding decrease in the heap size. Even with my webserver shutdown and no Tomcat usage, this leak is persistent. The memory leak checker portion of AppPerfect reports multiple memory leaks (even with the web server shutdown as I mentioned.) Can anybody help me figure out how to find out where this is coming from? Best regards, Ed Hamilton - 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: Help with memory leak using Tomcat
Does your profiling tool tell you the classes of the objects being created? Can you take a snapshot at two points in time, compare them and see what is different? If we know the class of the objects being created, it gives us a pretty good pointer as to where to start looking. Without this information, it is needle in haystack time. If your profiler doesn't do this, you probably need to get a new profiler. Mark Ed Hamilton wrote: I posted something similar to the Tomcat bug list and was asked to move it here. My first mailing to this list, so please correct any gaffes on my part... I'm running Tomcat 5.5.9; isapi redirector 1.2.13; J2SE 1.5.0.03; JDBC 3.1.8a; to support 2 very low volume websites. I have some kind of memory leak which triples tomcat's memory usage over about 4-5 days. I downloaded and installed AppPerfect profiler, and it shows a steady, consistent increase in objects and a corresponding decrease in the heap size. Even with my webserver shutdown and no Tomcat usage, this leak is persistent. The memory leak checker portion of AppPerfect reports multiple memory leaks (even with the web server shutdown as I mentioned.) Can anybody help me figure out how to find out where this is coming from? Best regards, Ed Hamilton - 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: Help with memory leak using Tomcat
I have experienced similar kind of memory leak, but that was while reloading the context. There was a steady increase in the memory usage after each autoReload of my struts 1.2.7-hibernate 2.1.8 powered webApp in Tomcat 5.5.7/JDK 1.5/Fedora Core 2. At the beginning: the process memory used by tomcat was 6.6%, then after each reload it went on slight increase such as: 7.8%, 8.3%, 8.8%, 9.1%, 10.1%, 10.7%Then I shutdown the tomcat server and restarted the server, I saw the memory usage as 6.4%, then on the next reload the usage was 7.9%. Meanwhile, the Java memory ( Runtime.getRuntime().totalMemory() Runtime.getRuntime().freeMemory() ) seem to stay pretty stabilizedSo, basically only process memory is increasing...which tells me that there is a leak in native memory. I saw similar threads like this when somebody had memory leaks with application reload/startup/shutdown with Tomcat Manager webapp... I am also looking for a good direction to move ahead. On 6/10/05, Mark Thomas [EMAIL PROTECTED] wrote: Does your profiling tool tell you the classes of the objects being created? Can you take a snapshot at two points in time, compare them and see what is different? If we know the class of the objects being created, it gives us a pretty good pointer as to where to start looking. Without this information, it is needle in haystack time. If your profiler doesn't do this, you probably need to get a new profiler. Mark Ed Hamilton wrote: I posted something similar to the Tomcat bug list and was asked to move it here. My first mailing to this list, so please correct any gaffes on my part... I'm running Tomcat 5.5.9; isapi redirector 1.2.13; J2SE 1.5.0.03; JDBC 3.1.8a; to support 2 very low volume websites. I have some kind of memory leak which triples tomcat's memory usage over about 4-5 days. I downloaded and installed AppPerfect profiler, and it shows a steady, consistent increase in objects and a corresponding decrease in the heap size. Even with my webserver shutdown and no Tomcat usage, this leak is persistent. The memory leak checker portion of AppPerfect reports multiple memory leaks (even with the web server shutdown as I mentioned.) Can anybody help me figure out how to find out where this is coming from? Best regards, Ed Hamilton - 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]
[Fwd: Re: Help with memory leak using Tomcat]
Ed Hamilton wrote: Mark, Thanks for the response. I'm repling to you directly - if that's wrong, please let me know. Please always reply to the list. This is for two reasons: - The extra information you provide might be enough for someone else to help you even if the original respondent can not. - The point of the list is to share knowledge and experience. This stops working once people switch to private mail. I've determined that with all my webapps shutdown, Tomcat allocates a new ojbect(s) of about 80KB exactly every 10 seconds and doesn't release it/them. The GC collector doesn't seem to clear it automatically. If I use the profiler's run GC the objects are released, the heap is returned to full size, and then the objectes start piling up again. What you describe is not a memory leak, just normal operation of the JVM. Tomcat is clearly doing something on a regular basis (at a guess this will be the auto-deploy code doing its work). Whatever this regular activity is, it creates objects. These objects are correctly released, since running garbage collection removes them. The JVM makes no guarantees when, or indeed if, garbage collection will be run. Since garbage collection is expensive, the JVM doesn't normally do it unless it has to. Therefore it is perfectly normal to see a steady rise in memory over time. If you leave it long enough you will see memory usage come back down when GC runs. If you were seeing a steady rise in memory after GC, this would be a memory leak. Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Help with memory leak using Tomcat
I posted something similar to the Tomcat bug list and was asked to move it here. My first mailing to this list, so please correct any gaffes on my part... I'm running Tomcat 5.5.9; isapi redirector 1.2.13; J2SE 1.5.0.03; JDBC 3.1.8a; to support 2 very low volume websites. I have some kind of memory leak which triples tomcat's memory usage over about 4-5 days. I downloaded and installed AppPerfect profiler, and it shows a steady, consistent increase in objects and a corresponding decrease in the heap size. Even with my webserver shutdown and no Tomcat usage, this leak is persistent. The memory leak checker portion of AppPerfect reports multiple memory leaks (even with the web server shutdown as I mentioned.) Can anybody help me figure out how to find out where this is coming from? Best regards, Ed Hamilton - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Static field memory leak on application reload
There still might be other references keeping the class alive (Like a logging package) Some have gone as far as calling Introspector.flushCaches() http://java.sun.com/j2se/1.4.2/docs/api/java/beans/Introspector.html#flushCaches() -Tim Otgonbayar wrote: I am using some static fields in my beans, but when I am reloading application the blocks were referenced by static fields still stays in memory. I detected these using a profiler tool. I wrote a context listener to free these blocks on destroy. But it doesn't help? So what can I do? Please help me - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Static field memory leak on application reload
I am using some static fields in my beans, but when I am reloading application the blocks were referenced by static fields still stays in memory. I detected these using a profiler tool. I wrote a context listener to free these blocks on destroy. But it doesn't help? So what can I do? Please help me Thanks Otgo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Memory Leak Solved
We have struggled with a memory leak in 5.0.28/5.0.30 for months. There have been many complaints about the necessity to restart Tomcat every couple days due to Out of Memory errors, but no solutions that cured it. Well, the suggestion to put the single line: Introspector.flushCaches(); in the destroy method of a servlet in a redeployable app finally solves it. Our Tomcat web server has now run for seven days without an OOM error. The amount of time spent with the Optimizeit profiler trying to locate a nonexistent memory leak in the application code cannot be overestimated. This discovery should be bold red lettered in the docs. Gary Harris
RE: Memory Leak Solved
I'm sorry, ignorance here... We've been using Tomcat 5.0.28 for more than a few months using Jetspeed1.5. Our production server probably has gone down once every week to 2 weeks, and we haven't experienced a memory leak. I thought that was one of the fixes when using Java 1.4.2 ? -Zach -Original Message- From: sysdba [mailto:[EMAIL PROTECTED] Sent: Friday, April 15, 2005 9:49 AM To: Tomcat Users List Subject: Memory Leak Solved We have struggled with a memory leak in 5.0.28/5.0.30 for months. There have been many complaints about the necessity to restart Tomcat every couple days due to Out of Memory errors, but no solutions that cured it. Well, the suggestion to put the single line: Introspector.flushCaches(); in the destroy method of a servlet in a redeployable app finally solves it. Our Tomcat web server has now run for seven days without an OOM error. The amount of time spent with the Optimizeit profiler trying to locate a nonexistent memory leak in the application code cannot be overestimated. This discovery should be bold red lettered in the docs. Gary Harris ** The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory Leak Solved
Hi, don't know if you are using it, but there's also a known issue with 5.0.28 and 'swallowOutput' in the Context element. After I turned it off, I haven't gotten any out of memory errors... Trond sysdba wrote: We have struggled with a memory leak in 5.0.28/5.0.30 for months. There have been many complaints about the necessity to restart Tomcat every couple days due to Out of Memory errors, but no solutions that cured it. Well, the suggestion to put the single line: Introspector.flushCaches(); in the destroy method of a servlet in a redeployable app finally solves it. Our Tomcat web server has now run for seven days without an OOM error. The amount of time spent with the Optimizeit profiler trying to locate a nonexistent memory leak in the application code cannot be overestimated. This discovery should be bold red lettered in the docs. Gary Harris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RES: Memory Leak Solved
The Introspector.flushCaches(); in the contextDestroyed wasn't enough for us... How should we use the 'swallowOutput'? We've tried this way without results: Context displayName=eCompany 3.0 docBase=/eprj path=eprj.war privileged=true swallowOutput=false (...) Trond, Do you have links to this known issue? -Mensagem original- De: Trond G. Ziarkowski [mailto:[EMAIL PROTECTED] Enviada em: sexta-feira, 15 de abril de 2005 11:08 Para: Tomcat Users List Assunto: Re: Memory Leak Solved Hi, don't know if you are using it, but there's also a known issue with 5.0.28 and 'swallowOutput' in the Context element. After I turned it off, I haven't gotten any out of memory errors... Trond sysdba wrote: We have struggled with a memory leak in 5.0.28/5.0.30 for months. There have been many complaints about the necessity to restart Tomcat every couple days due to Out of Memory errors, but no solutions that cured it. Well, the suggestion to put the single line: Introspector.flushCaches(); in the destroy method of a servlet in a redeployable app finally solves it. Our Tomcat web server has now run for seven days without an OOM error. The amount of time spent with the Optimizeit profiler trying to locate a nonexistent memory leak in the application code cannot be overestimated. This discovery should be bold red lettered in the docs. Gary Harris - 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: RES: Memory Leak Solved
Hi, here's the bugzilla: http://issues.apache.org/bugzilla/show_bug.cgi?id=33368, and here's a link to the archives where Robert Willie found this issue (read the entire thread...): http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg146409.html. Trond Paulo Alvim wrote: The Introspector.flushCaches(); in the contextDestroyed wasn't enough for us... How should we use the 'swallowOutput'? We've tried this way without results: Context displayName=eCompany 3.0 docBase=/eprj path=eprj.war privileged=true swallowOutput=false (...) Trond, Do you have links to this known issue? -Mensagem original- De: Trond G. Ziarkowski [mailto:[EMAIL PROTECTED] Enviada em: sexta-feira, 15 de abril de 2005 11:08 Para: Tomcat Users List Assunto: Re: Memory Leak Solved Hi, don't know if you are using it, but there's also a known issue with 5.0.28 and 'swallowOutput' in the Context element. After I turned it off, I haven't gotten any out of memory errors... Trond sysdba wrote: We have struggled with a memory leak in 5.0.28/5.0.30 for months. There have been many complaints about the necessity to restart Tomcat every couple days due to Out of Memory errors, but no solutions that cured it. Well, the suggestion to put the single line: Introspector.flushCaches(); in the destroy method of a servlet in a redeployable app finally solves it. Our Tomcat web server has now run for seven days without an OOM error. The amount of time spent with the Optimizeit profiler trying to locate a nonexistent memory leak in the application code cannot be overestimated. This discovery should be bold red lettered in the docs. Gary Harris - 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.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]
Memory leak in tomcat 5.0.28
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]
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
Possibly. If you are using a connection pool and do not close the
connection, it will not be released back to the pool, so subsequent
calls to the pool will create new connections.
There's a simple procedure to help you avoid this problem, even when errors
occur during your JDBC calls, and that is to close connections within a
finally block:
Connection con = null;
try {
// initialise and create connections here
// do all your other JDBC stuff here too
} catch ( SLQException e ) {
// handle exceptions here
} finally {
if ( con != null ) {
try { con.close(); } catch ( SQLException ignored ) {}
}
}
As you know, finally blocks are guaranteed to execute, even if an exception
is thrown.
HTH
Harry Mantheakis
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak
Another (simpler) solution is to let someone else write that code. ;-)
I know there are times when you need JDBC directly, but tools like
iBATIS make it darn easy to handle the other 99% of the cases.
Here is a tutorial on using struts with iBATIS that could be helpful
if people are interested.
http://www.reumann.net/struts/ibatisLesson1.do
The current iBATIS version is 2.x, and this covers 1.x, but the basics
are the same.
If someone wanted to convert it to use 2.x and put it on the iBATIS
wiki, that would rock.
http://wiki.apache.org/ibatis/
Larry
On Wed, 12 Jan 2005 10:41:28 +, Harry Mantheakis
[EMAIL PROTECTED] wrote:
Possibly. If you are using a connection pool and do not close the
connection, it will not be released back to the pool, so subsequent
calls to the pool will create new connections.
There's a simple procedure to help you avoid this problem, even when errors
occur during your JDBC calls, and that is to close connections within a
finally block:
Connection con = null;
try {
// initialise and create connections here
// do all your other JDBC stuff here too
} catch ( SLQException e ) {
// handle exceptions here
} finally {
if ( con != null ) {
try { con.close(); } catch ( SQLException ignored ) {}
}
}
As you know, finally blocks are guaranteed to execute, even if an exception
is thrown.
HTH
Harry Mantheakis
-
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]
Memory leak
Hi I have got a simple web application containing a html page with a link to a jsp page, which prints the memory status to the console(Runtime.getRuntime().totalMemory()) . Now I let about 50 concurrent user browsing to those pages and I noticed that the memory usage is constantly going up. The Total Memory Amount as well as the memory usage stated in the TaskManager. I don't want to believe that this little web app is leaking memory. Therefore I must do something wrong how I monitor the memory usage. Any help is very much appreciated. I'm using Windows2k Server + Tomcat 5.5 and sdk 1.4.2.06 Strangers are friends, which haven't met yet ! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak
how are you monitoring tomcat? peter On Wed, 12 Jan 2005 14:59:39 +1100, Rolf Zelder [EMAIL PROTECTED] wrote: Hi I have got a simple web application containing a html page with a link to a jsp page, which prints the memory status to the console(Runtime.getRuntime().totalMemory()) . Now I let about 50 concurrent user browsing to those pages and I noticed that the memory usage is constantly going up. The Total Memory Amount as well as the memory usage stated in the TaskManager. I don't want to believe that this little web app is leaking memory. Therefore I must do something wrong how I monitor the memory usage. Any help is very much appreciated. I'm using Windows2k Server + Tomcat 5.5 and sdk 1.4.2.06 Strangers are friends, which haven't met yet ! - 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
From: Rolf Zelder [mailto:[EMAIL PROTECTED] Subject: Memory leak I don't want to believe that this little web app is leaking memory. Therefore I must do something wrong how I monitor the memory usage. I suspect the real issue is understanding how the JVM uses memory. Object allocation can use however much memory you have specified for this java execution. It may garbage collect prior to reaching the maximum, but the JVM is under no particular obligation to do so. Once the maximum is reached, garbage collection must occur, which will release the space occupied by unreachable objects back to the heap. Note that pure Java applications can't have memory leaks in the traditional sense, since the programmer can't forget to include calls to the free() interface - there isn't one. What does happen with Java is forgetting to null out references to objects that are no longer needed, thereby preventing the garbage collector from returning such objects' space to the heap. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Memory leak
Hi, Taking the context of nullifying the object in Java, when we do not nullify the database connections, statements and result set, does these objects just fill the momory or even cause the database connection bottleneck? Regards Rajaneesh -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 12, 2005 9:49 AM To: Tomcat Users List Subject: RE: Memory leak From: Rolf Zelder [mailto:[EMAIL PROTECTED] Subject: Memory leak I don't want to believe that this little web app is leaking memory. Therefore I must do something wrong how I monitor the memory usage. I suspect the real issue is understanding how the JVM uses memory. Object allocation can use however much memory you have specified for this java execution. It may garbage collect prior to reaching the maximum, but the JVM is under no particular obligation to do so. Once the maximum is reached, garbage collection must occur, which will release the space occupied by unreachable objects back to the heap. Note that pure Java applications can't have memory leaks in the traditional sense, since the programmer can't forget to include calls to the free() interface - there isn't one. What does happen with Java is forgetting to null out references to objects that are no longer needed, thereby preventing the garbage collector from returning such objects' space to the heap. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - 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
From: Rajaneesh [mailto:[EMAIL PROTECTED] Subject: RE: Memory leak Taking the context of nullifying the object in Java, when we do not nullify the database connections, statements and result set, does these objects just fill the momory or even cause the database connection bottleneck? If you're using connection pooling, then it doesn't really matter if you null out the reference to the connection, since the pool manager is keeping track of them anyway, and the connection objects will typically persist for the lifetime of the container. If you're not using pooling, then it is important to null out such references in any objects that have a lifetime longer than the connection. In either case, you want to close the connection when you're done with it, which will either release it back to the pool or free up a slot in the database server. Failure to close the connection is a frequent cause of database access problems. Statement and result set objects should be handled like other Java objects - when you're done with them, null out any references to them from any spot that has a lifetime longer than that of the object being referenced. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory leak
Possibly. If you are using a connection pool and do not close the connection, it will not be released back to the pool, so subsequent calls to the pool will create new connections. In addition, as if that were not bad enough, any resources created that are referenced by that connection (statements, prepared statements, resultsets, etc...) will not be collected, because they still have references. Bottom line: Be sure that when you use JDBC directly, that you manage the resources very carefully. To simplify things, you may want to use a tool like iBATIS SQL Maps to remove some of the burden of resource management. Larry On Wed, 12 Jan 2005 09:57:42 +0530, Rajaneesh wrote: Taking the context of nullifying the object in Java, when we do not nullify the database connections, statements and result set, does these objects just fill the momory or even cause the database connection bottleneck? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Memory Leak with Javac and Tomcat v. 4.0.28
I was going to update my Tomcat from 4.0.19 because it says there is a javac leak in the RELEASE-NOTES. However, I noticed that 4.0.28 says the same thing. Is it fixed/ Jack -- You can lead a horse to water but you cannot make it float on its back. ~Dakota Jack~ You can't wake a person who is pretending to be asleep. ~Native Proverb~ Each man is good in His sight. It is not necessary for eagles to be crows. ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ --- This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory Leak with Javac and Tomcat v. 4.0.28
Dakota Jack wrote: I was going to update my Tomcat from 4.0.19 because it says there is a javac leak in the RELEASE-NOTES. However, I noticed that 4.0.28 says the same thing. Is it fixed/ Jack AFAIK this is no Tomcat issue but a JDK/Javac issue which was fixed in Sun JDK 1.4. See: http://www.apache.de/dist/jakarta/tomcat-5/v5.0.29/RELEASE-NOTES HTH Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Memory Leak with Javac and Tomcat v. 4.0.28
From: Dakota Jack [mailto:[EMAIL PROTECTED] Subject: Memory Leak with Javac and Tomcat v. 4.0.28 I was going to update my Tomcat from 4.0.19 because it says there is a javac leak in the RELEASE-NOTES. However, I noticed that 4.0.28 says the same thing. Is it fixed/ The memory leak is in the JDK, not Tomcat itself. If you use 1.4.2 or above the javac memory leak won't be a problem. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Memory Leak with Javac and Tomcat v. 4.0.28
Thanks, all! Jack -- You can lead a horse to water but you cannot make it float on its back. ~Dakota Jack~ You can't wake a person who is pretending to be asleep. ~Native Proverb~ Each man is good in His sight. It is not necessary for eagles to be crows. ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ --- This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: purported javac memory leak?
I think this is a jdk bug fixed in java 1.4 -Original Message- From: T K [mailto:[EMAIL PROTECTED] Sent: 01 November 2004 22:41 To: [EMAIL PROTECTED] Subject: purported javac memory leak? Hi all, as most of you know the tomcat 4.1.x jasper HOW-TO claims there is a javac memory leak; is there a SUN bug report I can look up? A small test case calling com.sun.tools.Main.compile() repeatedly does not exhibit the problem with JDK 1.4.2. Tomcat 5.x uses the JDT Java compiler - what was the motivation for doing so? Just so that one would not need the full JDK? thanks /st __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - 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]
purported javac memory leak?
Hi all, as most of you know the tomcat 4.1.x jasper HOW-TO claims there is a javac memory leak; is there a SUN bug report I can look up? A small test case calling com.sun.tools.Main.compile() repeatedly does not exhibit the problem with JDK 1.4.2. Tomcat 5.x uses the JDT Java compiler - what was the motivation for doing so? Just so that one would not need the full JDK? thanks /st __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Windows 2003 Java VM memory leak due to C# garbage collection algorithm
Hi, Wish someone could provide us insight to the following problem that we encounter. We have been trying for nearly two months now researching the web including this forum and trying out various suggestions but have been unsuccessful so far. What we would like to know is that if there is a memory leak in our application, it should grow within the java heap and eventually give an out of memory error and crash the JVM. This is what I have known from the first day I got into Java and have always thought this to be correct. (until now) We are running a Tomcat/5.0.27, 3 node cluster (on the same Windows Server 2003) and use the AJP13 connector to redirect requests from IIS 6.0 (running on IIS 5.0 isolation mode) (tried with Tomcat 5.0.19 as well. The JVM :1.5.0-rc-b63 tried with 1.4 as well) Using the recommended Oracle JDBC thin drivers for this version of the JVM, we connect to Oracle 9i which also runs on the same server. The issue we are having is that the VM size for each of the Java.exe processes grows way beyond the max heap settings. (we understand that it will not be equal due to the JVM loading overhead) For example, the heap settings is set to 512MB per tomcat/JVM instance but on Windows, it keeps growing to about 1.5 GB. This happens to each of the nodes and it goes into virtual memory and then eventually crashes and we have to restart the Tomcat cluster. Now I know with regard to Java application memory leaks, you got to check your programs. But what I want to know is that if there is a memory leak from our programs, it should eventually take the full java heap and then crash with an out of memory error. But that does not happen. In fact by monitoring the GC output, the heap seem to be working fine with each GC run increasing the free memory. In fact when we monitor the tomcat status page as well, we do see the java heap memory behaving correct. Also as I said, there are no out of memory errors in the log as well. What I want to know is even if our program has a memory leak, it should crash the JVM right? It should not keep increasing the memory allocated from the Windows Server 2003 O/S. Could this be a issue with the Windows server 2003 garbage collection as I read it is written using C#? anyone has any idea if this is the problem? Any help would be very much appreciated. Thanks Travis
AW: Windows 2003 Java VM memory leak due to C# garbage collection algorithm
Hi What I want to know is even if our program has a memory leak, it should crash the JVM right? No, your program (better your webapp) should get OutOfMemoryExceptions and should continue running. Mostly, it will not do sensful things any more, but it should NEVER crash the JVM. It should not keep increasing the memory allocated from the Windows Server 2003 O/S. Right. It should go about 64 MB over your max heap setting (which is approx. the jvm overhead), but not 1 GB above. There is something wrong. Are you sure you specified both MIN AND MAX heap values? Can you show your OPTS? How are you starting tomcat - as service or as application? Could this be a issue with the Windows server 2003 garbage collection as I read it is written using C#? anyone has any idea if this is the problem? No. Windows 2003 server has nothing to do with applications garbage collection. Java JVM have their own garbage collector, you can even choose one from command line - what you could try. Windows 2003 itself has no garbage collection at all. Windows 2003 provides .net by default, which itself works semtantically like a VM and which itself DOES HAVE a garbage collector. That one IS used for C#, but I doubt it is written in C#. And even if it would be written in C#, that should not be the problem, since it is used in really huge applications and has not shown to be a big source of leaks so far. Regards, Steffen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Windows 2003 Java VM memory leak due to C# garbage collection algorithm
Hi Steffen, Thanks for your reply. What you say confirms my understanding of how the JVM works. We start Tomcat from the command prompt as an application. We have been using various settings for the OPTS. Currently its set as: set AVA_OPTS= -server -Xmx512M -XX:MaxNewSize=256M -Xminf.5 -Xmaxf.8 -XX:NewSiz e=2m -XX:NewRatio=3 -Xcompactgc -XX:+UseParallelGC -XX:+UseAdaptiveSizePolic y -XX:ParallelGCThreads=4 -XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=256m -Xloggc:%M_JVM_LOG_FILE% -XX:+PrintTLE Previously we have set the following as well (and a lot of others as well such as changing the GC algorithm etc) #set JAVA_OPTS= -Xms256m -Xmx256m -Xgc:parallel -Xcleartype:gc (the min and max heap was set to the same as we have memory on our server (4GB) and wanted to avoid the overhead associated with growing the JVM that require multiple system calls resulting in segmented system memory.) I was thinking its a windows 2003 garbage collection issue as they seem to have changed their memory handing concept and now use the garbage collection concept. In windows 2000, it was different. And when we were running our webapps on windows 2000, it was fine. Unfortunately we recently moved our webapps to a new dedicated server with a new hosting company and it came with windows 2003. Thanks for any assistance. Travis - Original Message - From: SH Solutions [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED]; 'Travis De Silva' [EMAIL PROTECTED] Sent: Friday, September 17, 2004 6:26 PM Subject: AW: Windows 2003 Java VM memory leak due to C# garbage collection algorithm Hi What I want to know is even if our program has a memory leak, it should crash the JVM right? No, your program (better your webapp) should get OutOfMemoryExceptions and should continue running. Mostly, it will not do sensful things any more, but it should NEVER crash the JVM. It should not keep increasing the memory allocated from the Windows Server 2003 O/S. Right. It should go about 64 MB over your max heap setting (which is approx. the jvm overhead), but not 1 GB above. There is something wrong. Are you sure you specified both MIN AND MAX heap values? Can you show your OPTS? How are you starting tomcat - as service or as application? Could this be a issue with the Windows server 2003 garbage collection as I read it is written using C#? anyone has any idea if this is the problem? No. Windows 2003 server has nothing to do with applications garbage collection. Java JVM have their own garbage collector, you can even choose one from command line - what you could try. Windows 2003 itself has no garbage collection at all. Windows 2003 provides .net by default, which itself works semtantically like a VM and which itself DOES HAVE a garbage collector. That one IS used for C#, but I doubt it is written in C#. And even if it would be written in C#, that should not be the problem, since it is used in really huge applications and has not shown to be a big source of leaks so far. Regards, Steffen - 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: Windows 2003 Java VM memory leak due to C# garbage collection algorithm
I'd use Windows 2003 (or .NET Server if you like) and there is no Garbage Collection to the application. About internal kernel management I don't know, but applications can't use it. Applications have to use there own algorithms. It would simply be impossible to redesign this for the Windows environment, because it will render thousands of applications completely useless. I think you are mistakenly replacing *.NET Server* with *.NET*, which is a Virtual Machine, just as the JVM is. Since *.NET* is delivered together with *.NET Server*, there is a Garbage Collector within the .NET environment, which is used by languages such as C#, VB.NET and Managed C++. Regards, Sjoerd Travis De Silva wrote: Hi Steffen, Thanks for your reply. What you say confirms my understanding of how the JVM works. We start Tomcat from the command prompt as an application. We have been using various settings for the OPTS. Currently its set as: set AVA_OPTS= -server -Xmx512M -XX:MaxNewSize=256M -Xminf.5 -Xmaxf.8 -XX:NewSiz e=2m -XX:NewRatio=3 -Xcompactgc -XX:+UseParallelGC -XX:+UseAdaptiveSizePolic y -XX:ParallelGCThreads=4 -XX:+CMSClassUnloadingEnabled -XX:MaxPermSize=256m -Xloggc:%M_JVM_LOG_FILE% -XX:+PrintTLE Previously we have set the following as well (and a lot of others as well such as changing the GC algorithm etc) #set JAVA_OPTS= -Xms256m -Xmx256m -Xgc:parallel -Xcleartype:gc (the min and max heap was set to the same as we have memory on our server (4GB) and wanted to avoid the overhead associated with growing the JVM that require multiple system calls resulting in segmented system memory.) I was thinking its a windows 2003 garbage collection issue as they seem to have changed their memory handing concept and now use the garbage collection concept. In windows 2000, it was different. And when we were running our webapps on windows 2000, it was fine. Unfortunately we recently moved our webapps to a new dedicated server with a new hosting company and it came with windows 2003. Thanks for any assistance. Travis - Original Message - From: SH Solutions [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED]; 'Travis De Silva' [EMAIL PROTECTED] Sent: Friday, September 17, 2004 6:26 PM Subject: AW: Windows 2003 Java VM memory leak due to C# garbage collection algorithm Hi What I want to know is even if our program has a memory leak, it should crash the JVM right? No, your program (better your webapp) should get OutOfMemoryExceptions and should continue running. Mostly, it will not do sensful things any more, but it should NEVER crash the JVM. It should not keep increasing the memory allocated from the Windows Server 2003 O/S. Right. It should go about 64 MB over your max heap setting (which is approx. the jvm overhead), but not 1 GB above. There is something wrong. Are you sure you specified both MIN AND MAX heap values? Can you show your OPTS? How are you starting tomcat - as service or as application? Could this be a issue with the Windows server 2003 garbage collection as I read it is written using C#? anyone has any idea if this is the problem? No. Windows 2003 server has nothing to do with applications garbage collection. Java JVM have their own garbage collector, you can even choose one from command line - what you could try. Windows 2003 itself has no garbage collection at all. Windows 2003 provides .net by default, which itself works semtantically like a VM and which itself DOES HAVE a garbage collector. That one IS used for C#, but I doubt it is written in C#. And even if it would be written in C#, that should not be the problem, since it is used in really huge applications and has not shown to be a big source of leaks so far. Regards, Steffen - 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: 5.0.19 Memory Leak?
Hi, Is jmx the Jasper compiler? And, to turn it off, is to set false for reloading and development in conf/web.xml? No to all, RTFM or STFA. Yoav - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: 5.0.19 Memory Leak?
Hola, The recommendation is pretty much always to use the latest stable release. There are rarely (but occasionally, they do exist) valid reasons to stay back [given time and deployment constraints of course]. Specifically with 5.0.19, there was something with the jmx registering requests that could be turned off in the connector configuration to alleviate the memory leak, which is significant. Yoav Shapira Millennium Research Informatics -Original Message- From: Sunitha Kumar [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 11, 2004 1:49 AM To: Tomcat Users List Subject: 5.0.19 Memory Leak? Hey folks: There was a thread which mentioned that there have been memory leaks in 5.0.19. Is this a known issue? If so, is the recommendation to move to 5.0.25? thanks, -sunitha - 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: 5.0.19 Memory Leak?
yep, it was adding request.registerRequests=false to your CATALINA_HOME/conf/jk2.properties file Allistair -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: 11 August 2004 13:43 To: Tomcat Users List Subject: RE: 5.0.19 Memory Leak? Hola, The recommendation is pretty much always to use the latest stable release. There are rarely (but occasionally, they do exist) valid reasons to stay back [given time and deployment constraints of course]. Specifically with 5.0.19, there was something with the jmx registering requests that could be turned off in the connector configuration to alleviate the memory leak, which is significant. Yoav Shapira Millennium Research Informatics -Original Message- From: Sunitha Kumar [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 11, 2004 1:49 AM To: Tomcat Users List Subject: 5.0.19 Memory Leak? Hey folks: There was a thread which mentioned that there have been memory leaks in 5.0.19. Is this a known issue? If so, is the recommendation to move to 5.0.25? thanks, -sunitha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: 5.0.19 Memory Leak?
Is jmx the Jasper compiler? And, to turn it off, is to set false for reloading and development in conf/web.xml? Thanks, -sunitha -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 11, 2004 5:43 AM To: Tomcat Users List Subject: RE: 5.0.19 Memory Leak? Hola, The recommendation is pretty much always to use the latest stable release. There are rarely (but occasionally, they do exist) valid reasons to stay back [given time and deployment constraints of course]. Specifically with 5.0.19, there was something with the jmx registering requests that could be turned off in the connector configuration to alleviate the memory leak, which is significant. Yoav Shapira Millennium Research Informatics -Original Message- From: Sunitha Kumar [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 11, 2004 1:49 AM To: Tomcat Users List Subject: 5.0.19 Memory Leak? Hey folks: There was a thread which mentioned that there have been memory leaks in 5.0.19. Is this a known issue? If so, is the recommendation to move to 5.0.25? thanks, -sunitha - 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]
5.0.19 Memory Leak?
Hey folks: There was a thread which mentioned that there have been memory leaks in 5.0.19. Is this a known issue? If so, is the recommendation to move to 5.0.25? thanks, -sunitha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Strage Behaviour - Tomcat Memory Leak
Hi, I was doing an evaluation of JProfiler in order see the improvements did since the last time I used it. I has a feature (like other profilers) that shows the heap usage in real time. As I always do, I have installed a new copy of tomcat, with NO changes. I have just unziped it into a directory (by the way, I am using winXP, J2SDK1.4.2_05, JProfiler 3.1 and tomcat 4.1.30/5.0.25). So I started JProfiler, that automatically starts tomcat (I have tested it against 4.1.30 and 5.0.25 - same behaviour), and I also started the heap monitor (that JProfiler calls VM Telemetry). What I saw, IMHO, is very strange: time to times (around every 30 minutes) the heap is totally filled, and the garbage collector runs. So the graph looks like a saw: /| /| /| / / | / | / | / / |/ |/ |/ What is strange, is that I does't touch tomcat. I just start it. Nothing is running under it (except the default applications: manager, examples, etc Anyway, I have cleaned the server.xml and webapps, removing the manager, admin and examples app. Same bahaviour again). IMHO, the heap usage should be a flat line if nothing is running under tomcat. Something like (the initial increase is due to tomcat startup) this: /-- / / My conclusion, is that OR tomcat has a huge memory leak, OR JProfiler isn't reliable. Does anyone has an explanation about this behaviour? Is it know? Maybe a listener, logger, etc? TIA, Bob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Strage Behaviour - Tomcat Memory Leak
Hi, It depends on the size of your saw teeth: if they're small (2MB), it can be attributed to anything including internal JVM optimizations. HotSpot will move things around in memory even when no activity is taking place. Also, what you're describing is not a leak by definition, since the memory is reclaimed, i.e. nothing maintains references to it ;) Yoav Shapira Millennium Research Informatics -Original Message- From: Roberto Rios [mailto:[EMAIL PROTECTED] Sent: Thursday, August 05, 2004 12:40 PM To: [EMAIL PROTECTED] Subject: Strage Behaviour - Tomcat Memory Leak Hi, I was doing an evaluation of JProfiler in order see the improvements did since the last time I used it. I has a feature (like other profilers) that shows the heap usage in real time. As I always do, I have installed a new copy of tomcat, with NO changes. I have just unziped it into a directory (by the way, I am using winXP, J2SDK1.4.2_05, JProfiler 3.1 and tomcat 4.1.30/5.0.25). So I started JProfiler, that automatically starts tomcat (I have tested it against 4.1.30 and 5.0.25 - same behaviour), and I also started the heap monitor (that JProfiler calls VM Telemetry). What I saw, IMHO, is very strange: time to times (around every 30 minutes) the heap is totally filled, and the garbage collector runs. So the graph looks like a saw: /| /| /| / / | / | / | / / |/ |/ |/ What is strange, is that I does't touch tomcat. I just start it. Nothing is running under it (except the default applications: manager, examples, etc Anyway, I have cleaned the server.xml and webapps, removing the manager, admin and examples app. Same bahaviour again). IMHO, the heap usage should be a flat line if nothing is running under tomcat. Something like (the initial increase is due to tomcat startup) this: /-- / / My conclusion, is that OR tomcat has a huge memory leak, OR JProfiler isn't reliable. Does anyone has an explanation about this behaviour? Is it know? Maybe a listener, logger, etc? TIA, Bob - 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: Strage Behaviour - Tomcat Memory Leak
I've used JProfiler in the past and I found it somewhat unreliable, since it is pretty heavy weight. I should say it was based on a half dozen tests using JProfiler and not a scientific evaluation. it was the free eval version a couple years back. I find optimizeIt more reliable for me and a little less heavy weight. I've use OptimizeIt in the past and tomcat without any requests shows flat memory usage. in other words constant. peter On Thu, 5 Aug 2004 13:39:44 -0300, Roberto Rios [EMAIL PROTECTED] wrote: Hi, I was doing an evaluation of JProfiler in order see the improvements did since the last time I used it. I has a feature (like other profilers) that shows the heap usage in real time. As I always do, I have installed a new copy of tomcat, with NO changes. I have just unziped it into a directory (by the way, I am using winXP, J2SDK1.4.2_05, JProfiler 3.1 and tomcat 4.1.30/5.0.25). So I started JProfiler, that automatically starts tomcat (I have tested it against 4.1.30 and 5.0.25 - same behaviour), and I also started the heap monitor (that JProfiler calls VM Telemetry). What I saw, IMHO, is very strange: time to times (around every 30 minutes) the heap is totally filled, and the garbage collector runs. So the graph looks like a saw: /| /| /| / / | / | / | / / |/ |/ |/ What is strange, is that I does't touch tomcat. I just start it. Nothing is running under it (except the default applications: manager, examples, etc Anyway, I have cleaned the server.xml and webapps, removing the manager, admin and examples app. Same bahaviour again). IMHO, the heap usage should be a flat line if nothing is running under tomcat. Something like (the initial increase is due to tomcat startup) this: /-- / / My conclusion, is that OR tomcat has a huge memory leak, OR JProfiler isn't reliable. Does anyone has an explanation about this behaviour? Is it know? Maybe a listener, logger, etc? TIA, Bob - 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: Strage Behaviour - Tomcat Memory Leak
From: Peter Lin [mailto:[EMAIL PROTECTED] Subject: Re: Strage Behaviour - Tomcat Memory Leak I've use OptimizeIt in the past and tomcat without any requests shows flat memory usage. in other words constant. Memory usage also depends on configuration options such as auto deploy. When this is on, Tomcat periodically probes for changes in the webapps directory. Doing so generates short-lived objects which accumulate until GC runs. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Strage Behaviour - Tomcat Memory Leak
As Yoav points out, this is quite normal. I also run JProbe and if you just leave it alone, very small memory usage is made and at regular intervals the GC will jump in, producing your saw tooth (since the GC will only jump in when it really thinks the heap needs clearing out is why it gets quite high). Also when you say the heap is totally filled I don;t think you mean that the total memory available to Tomcat is filled, e.g 128-512MB or whatever. What you mean is that the heap used is filled and I bet that heap size is actually only about 7Mb or so if as you claim it is just a startup of Tomcat. Therefore it is quite possible that it looks alarming but it is not really. Cheers, ADC. -Original Message- From: Peter Lin [mailto:[EMAIL PROTECTED] Sent: Thu 05/08/2004 17:55 To: Tomcat Users List Cc: Subject: Re: Strage Behaviour - Tomcat Memory Leak I've used JProfiler in the past and I found it somewhat unreliable, since it is pretty heavy weight. I should say it was based on a half dozen tests using JProfiler and not a scientific evaluation. it was the free eval version a couple years back. I find optimizeIt more reliable for me and a little less heavy weight. I've use OptimizeIt in the past and tomcat without any requests shows flat memory usage. in other words constant. peter On Thu, 5 Aug 2004 13:39:44 -0300, Roberto Rios [EMAIL PROTECTED] wrote: Hi, I was doing an evaluation of JProfiler in order see the improvements did since the last time I used it. I has a feature (like other profilers) that shows the heap usage in real time. As I always do, I have installed a new copy of tomcat, with NO changes. I have just unziped it into a directory (by the way, I am using winXP, J2SDK1.4.2_05, JProfiler 3.1 and tomcat 4.1.30/5.0.25). So I started JProfiler, that automatically starts tomcat (I have tested it against 4.1.30 and 5.0.25 - same behaviour), and I also started the heap monitor (that JProfiler calls VM Telemetry). What I saw, IMHO, is very strange: time to times (around every 30 minutes) the heap is totally filled, and the garbage collector runs. So the graph looks like a saw: /| /| /| / / | / | / | / / |/ |/ |/ What is strange, is that I does't touch tomcat. I just start it. Nothing is running under it (except the default applications: manager, examples, etc Anyway, I have cleaned the server.xml and webapps, removing the manager, admin and examples app. Same bahaviour again). IMHO, the heap usage should be a flat line if nothing is running under tomcat. Something like (the initial increase is due to tomcat startup) this: /-- / / My conclusion, is that OR tomcat has a huge memory leak, OR JProfiler isn't reliable. Does anyone has an explanation about this behaviour? Is it know? Maybe a listener, logger, etc? TIA, Bob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] FONT SIZE=1 FACE=VERDANA,ARIAL COLOR=BLUE --- QAS Ltd. Developers of QuickAddress Software a href=http://www.qas.com;www.qas.com/a Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- /FONT - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Strage Behaviour - Tomcat Memory Leak
Everybody is right. The saw teeth is around 3mb. The heap is around 9mb. So after the GC runs, the available heap falls to 6mb. As Yoah said this isn't a memory leak, since all the objects that area created are garbage collected. I called it as a memory leak because even with nothing running under tomcat, object were created. I did an experience (following what Allistair wrote), removing loggers and setting autodeploy to false. The saw pattern still occuring, but the cycle is a little bit longer. And, now that the problem is solved, I think that JProfiler is quite good. It has some nice features. Since the last time that I have tested it, they have improved a lot. Thanks, Bob -Mensagem original- De: Roberto Rios [mailto:[EMAIL PROTECTED] Enviada em: quinta-feira, 5 de agosto de 2004 13:40 Para: [EMAIL PROTECTED] Assunto: Strage Behaviour - Tomcat Memory Leak Hi, I was doing an evaluation of JProfiler in order see the improvements did since the last time I used it. I has a feature (like other profilers) that shows the heap usage in real time. As I always do, I have installed a new copy of tomcat, with NO changes. I have just unziped it into a directory (by the way, I am using winXP, J2SDK1.4.2_05, JProfiler 3.1 and tomcat 4.1.30/5.0.25). So I started JProfiler, that automatically starts tomcat (I have tested it against 4.1.30 and 5.0.25 - same behaviour), and I also started the heap monitor (that JProfiler calls VM Telemetry). What I saw, IMHO, is very strange: time to times (around every 30 minutes) the heap is totally filled, and the garbage collector runs. So the graph looks like a saw: /| /| /| / / | / | / | / / |/ |/ |/ What is strange, is that I does't touch tomcat. I just start it. Nothing is running under it (except the default applications: manager, examples, etc Anyway, I have cleaned the server.xml and webapps, removing the manager, admin and examples app. Same bahaviour again). IMHO, the heap usage should be a flat line if nothing is running under tomcat. Something like (the initial increase is due to tomcat startup) this: /-- / / My conclusion, is that OR tomcat has a huge memory leak, OR JProfiler isn't reliable. Does anyone has an explanation about this behaviour? Is it know? Maybe a listener, logger, etc? TIA, Bob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Strage Behaviour - Tomcat Memory Leak
I believe you would need to set the backgroundProcessorDelay attribute on the Engine element to -1 in server.xml if you wanted keep it from generating a little bit of garbage every 10 seconds. I'm not aware that this would disable anything critical (assuming you can live without the auto, live and reloading features), but I'm too lazy to make sure. Cheers, Larry -Original Message- From: Roberto Rios [mailto:[EMAIL PROTECTED] Sent: Thursday, August 05, 2004 3:35 PM To: [EMAIL PROTECTED] Subject: RE: Strage Behaviour - Tomcat Memory Leak Importance: High Everybody is right. The saw teeth is around 3mb. The heap is around 9mb. So after the GC runs, the available heap falls to 6mb. As Yoah said this isn't a memory leak, since all the objects that area created are garbage collected. I called it as a memory leak because even with nothing running under tomcat, object were created. I did an experience (following what Allistair wrote), removing loggers and setting autodeploy to false. The saw pattern still occuring, but the cycle is a little bit longer. And, now that the problem is solved, I think that JProfiler is quite good. It has some nice features. Since the last time that I have tested it, they have improved a lot. Thanks, Bob -Mensagem original- De: Roberto Rios [mailto:[EMAIL PROTECTED] Enviada em: quinta-feira, 5 de agosto de 2004 13:40 Para: [EMAIL PROTECTED] Assunto: Strage Behaviour - Tomcat Memory Leak Hi, I was doing an evaluation of JProfiler in order see the improvements did since the last time I used it. I has a feature (like other profilers) that shows the heap usage in real time. As I always do, I have installed a new copy of tomcat, with NO changes. I have just unziped it into a directory (by the way, I am using winXP, J2SDK1.4.2_05, JProfiler 3.1 and tomcat 4.1.30/5.0.25). So I started JProfiler, that automatically starts tomcat (I have tested it against 4.1.30 and 5.0.25 - same behaviour), and I also started the heap monitor (that JProfiler calls VM Telemetry). What I saw, IMHO, is very strange: time to times (around every 30 minutes) the heap is totally filled, and the garbage collector runs. So the graph looks like a saw: /| /| /| / / | / | / | / / |/ |/ |/ What is strange, is that I does't touch tomcat. I just start it. Nothing is running under it (except the default applications: manager, examples, etc Anyway, I have cleaned the server.xml and webapps, removing the manager, admin and examples app. Same bahaviour again). IMHO, the heap usage should be a flat line if nothing is running under tomcat. Something like (the initial increase is due to tomcat startup) this: /-- / / My conclusion, is that OR tomcat has a huge memory leak, OR JProfiler isn't reliable. Does anyone has an explanation about this behaviour? Is it know? Maybe a listener, logger, etc? TIA, Bob - 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]
mod_jk2 memory leak?
Greetings. Ok, I posted yesterday about the fork attribute - no response yet and stuff. Now I indicated that the fork setting of true *seemed* to have solved many of my problems RE the apparent memory leak on my server. I am now revising that statement in that the server now stayed up for 25 hours as opposed to the 12 or so it was before I set the fork init-param to true. So now I am where the OTHER memory leak is. I have run profilers on the server and cannot seem to find anything obvious in my code (in fact my code seems to garbage collect very well and properly)... I do recall certain posts on this list about a potential memory leak in mod_jk2 - I am running Apache 2.0.49 with mod_jk2 connecting to Tomcat behind. Does anyone know if this was ever proved to be the case? I will be attempting to run the server on Tomcat standalone - to see if the memory leak persists or not. Anyway, any pointers would be welcome! Regards, Carl Olivier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: mod_jk2 memory leak?
Hi, I had a similar problem with apache 1.3 and mod jk2. The httpd processes kept growing and growing. I didn't have this problem when I was using jk1.2 so I suppose it's a problem with jk2. To prevent the httpd processes getting to big causing the server to crash / running out of memory I just changed the MaxRequestsPerChild property in the httpd.conf from 0 (unlimited) to 1500. This way a processe gets killed after 1500 accesses and all the memory bound to it gets released. Of course you have to try which value suits your configuration best depending on the amount of memory you got and the number of max clients. Hope this helps Thomas -Ursprüngliche Nachricht- Von: Carl Olivier [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 18. Juni 2004 09:38 An: '[EMAIL PROTECTED]' Betreff: mod_jk2 memory leak? Greetings. Ok, I posted yesterday about the fork attribute - no response yet and stuff. Now I indicated that the fork setting of true *seemed* to have solved many of my problems RE the apparent memory leak on my server. I am now revising that statement in that the server now stayed up for 25 hours as opposed to the 12 or so it was before I set the fork init-param to true. So now I am where the OTHER memory leak is. I have run profilers on the server and cannot seem to find anything obvious in my code (in fact my code seems to garbage collect very well and properly)... I do recall certain posts on this list about a potential memory leak in mod_jk2 - I am running Apache 2.0.49 with mod_jk2 connecting to Tomcat behind. Does anyone know if this was ever proved to be the case? I will be attempting to run the server on Tomcat standalone - to see if the memory leak persists or not. Anyway, any pointers would be welcome! Regards, Carl Olivier - 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: AW: mod_jk2 memory leak?
MatrixOne Tech Support eMail incident submission functionality requires specific subject line. The following subject lines are recognized. Request for CustomerLink Access - This will submit a request for new CustomerLink account Request for CustomerLink Password Reset - This will submit a request for existing CustomerLink account password reset Submit [PUT YOUR SUBJECT LINE HERE] - This will submit a new incident (please only use when CustomerLink is not available to ensure prompt service) Keywords Request or Submit must be the 1st word in the subject line. If you already have a CustomerLink account, please use CustomerLink (https://customerlink.matrixone.com) to submit or update your incidents. Otherwise, please resend your message with the required subject line. Thank you! MatrixOne Tech Support - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
Ran out of memory last night again Set to 512m and ran out at 284m Maybe I am missing a paramater in the tomcat setup on windows or something Frustrating James I was having a memory leak using mod_jk2, and it was fixed by adding request.registerRequests=false to tomcat/conf/jk2.properties. I don't know if this would work with mod_jk, but it might be worth a try. Adrian -- f y cn rd ths y cn gt a gd jb rt fpl dgm pvq! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat5/mod_jk Memory Leak/mod_jk bypass
I am just curious in this... Where did you set the 512m? Is your Tomcat's JVM size? Ran out of memory last night again Set to 512m and ran out at 284m Maybe I am missing a paramater in the tomcat setup on windows or something Frustrating James I was having a memory leak using mod_jk2, and it was fixed by adding request.registerRequests=false to tomcat/conf/jk2.properties. I don't know if this would work with mod_jk, but it might be worth a try. Adrian -- f y cn rd ths y cn gt a gd jb rt fpl dgm pvq! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ For information about the Standard Bank group visit our web site www.standardbank.co.za __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relating to the official business of Standard Bank Group Limited is proprietary to the group. It is confidential, legally privileged and protected by law. Standard Bank does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of the group. The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way. Standard Bank can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. ___
Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
Adrian Barnett wrote: Ran out of memory last night again Set to 512m and ran out at 284m Maybe I am missing a paramater in the tomcat setup on windows or something Frustrating James I was having a memory leak using mod_jk2, and it was fixed by adding request.registerRequests=false to tomcat/conf/jk2.properties. I don't know if this would work with mod_jk, but it might be worth a try. Adrian I can confirm that this works with mod_jk too. I'm a little surprised that fixing this rather horrible memory leak doesn't appear to be a high priority. We were almost at a point of abandoning Tomcat altogether since we couldn't keep our test environment running for more than 2 days without OutOfMemory problems while it would run for weeks on end with JRun3. Adding this line made all our problems go away, and we are now well on our way to completing our migration to Tomcat. 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: Tomcat5/mod_jk Memory Leak/mod_jk bypass
I actually have it fixed now(well no ramping in 24 hours). I am using tomcat on a windows machine so I adjusted to memory in the configure tomcat in the start menu(allows you to adjust jvm startup parameters) The problem did not have anything to do with tomcat if my fix works:) - Original Message - From: Kommuru, Bhaskar [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Wednesday, June 02, 2004 6:03 AM Subject: RE: Tomcat5/mod_jk Memory Leak/mod_jk bypass I am just curious in this... Where did you set the 512m? Is your Tomcat's JVM size? Ran out of memory last night again Set to 512m and ran out at 284m Maybe I am missing a paramater in the tomcat setup on windows or something Frustrating James I was having a memory leak using mod_jk2, and it was fixed by adding request.registerRequests=false to tomcat/conf/jk2.properties. I don't know if this would work with mod_jk, but it might be worth a try. Adrian -- f y cn rd ths y cn gt a gd jb rt fpl dgm pvq! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ For information about the Standard Bank group visit our web site www.standardbank.co.za __ Disclaimer and confidentiality note Everything in this e-mail and any attachments relating to the official business of Standard Bank Group Limited is proprietary to the group. It is confidential, legally privileged and protected by law. Standard Bank does not own and endorse any other content. Views and opinions are those of the sender unless clearly stated as being that of the group. The person addressed in the e-mail is the sole authorised recipient. Please notify the sender immediately if it has unintentionally reached you and do not read, disclose or use the content in any way. Standard Bank can not assure that the integrity of this communication has been maintained nor that it is free of errors, virus, interception or interference. ___ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat5/mod_jk Memory Leak/mod_jk bypass
This sounds awfully similar to what we are experiencing, although I have not determined that it is a jk2 related memory leak. Are you using some sort of profiling tool to determine this? And exactly what does request.registerRequests=false do? -Original Message- From: Michiel Toneman [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 02, 2004 3:18 AM To: Tomcat Users List Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass Adrian Barnett wrote: Ran out of memory last night again Set to 512m and ran out at 284m Maybe I am missing a paramater in the tomcat setup on windows or something Frustrating James I was having a memory leak using mod_jk2, and it was fixed by adding request.registerRequests=false to tomcat/conf/jk2.properties. I don't know if this would work with mod_jk, but it might be worth a try. Adrian I can confirm that this works with mod_jk too. I'm a little surprised that fixing this rather horrible memory leak doesn't appear to be a high priority. We were almost at a point of abandoning Tomcat altogether since we couldn't keep our test environment running for more than 2 days without OutOfMemory problems while it would run for weeks on end with JRun3. Adding this line made all our problems go away, and we are now well on our way to completing our migration to Tomcat. 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] This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error, and that any use, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender and delete it from your computer. Although our company attempts to sweep e-mail and attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
Michiel Toneman wrote, On 6/2/2004 2:18 AM: I can confirm that this works with mod_jk too. I'm a little surprised that fixing this rather horrible memory leak doesn't appear to be a high priority. We were almost at a point of abandoning Tomcat altogether since we couldn't keep our test environment running for more than 2 days without OutOfMemory problems while it would run for weeks on end with JRun3. Adding this line made all our problems go away, and we are now well on our way to completing our migration to Tomcat. This particular issue has been fixed in Tomcat 5.0.x already. Please download the latest release. As the thread starter James mentioned, his memory leak problem was not because of this issue as he is running the latest, 5.0.25. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
On Wed, 2 Jun 2004 11:48:02 -0400, Chad Morris [EMAIL PROTECTED] wrote: This sounds awfully similar to what we are experiencing, although I have not determined that it is a jk2 related memory leak. Are you using some sort of profiling tool to determine this? And exactly what does request.registerRequests=false do? Don't know what it does (other than stopping jk2 registering requests, I'd guess) or why it works. It was mentioned on this very mailing list a few weeks ago, in response to a previous memory-leak thread, so I tried it and it worked. Not very scientific, I know... Adrian -- f y cn rd ths y cn gt a gd jb rt fpl dgm pvq! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat5/mod_jk Memory Leak/mod_jk bypass
Whatever works, right? Does this only apply to tomcat 5 or is it applicable to tomcat 4 as well? -Original Message- From: Adrian Barnett [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 02, 2004 11:00 AM To: Tomcat Users List Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass On Wed, 2 Jun 2004 11:48:02 -0400, Chad Morris [EMAIL PROTECTED] wrote: This sounds awfully similar to what we are experiencing, although I have not determined that it is a jk2 related memory leak. Are you using some sort of profiling tool to determine this? And exactly what does request.registerRequests=false do? Don't know what it does (other than stopping jk2 registering requests, I'd guess) or why it works. It was mentioned on this very mailing list a few weeks ago, in response to a previous memory-leak thread, so I tried it and it worked. Not very scientific, I know... Adrian -- f y cn rd ths y cn gt a gd jb rt fpl dgm pvq! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error, and that any use, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender and delete it from your computer. Although our company attempts to sweep e-mail and attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
Try this: http://marc.theaimsgroup.com/?l=tomcat-userm=107976963131361w=2 I wasn't able to get it to work myself, but maybe you can. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
Ran out of memory last night again
Set to 512m and ran out at 284m
Maybe I am missing a paramater in the tomcat setup on windows or something
Frustrating
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 4:04 PM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
300 mb sounds a lot, i've got a hibernate and struts flavored app
running with a 128 limit, and thats being generous.
I haven't measured anything but top looks happy, with 5.0.25 with jk to
apache 2.0.47. Had a bit of traffic this afternoon albeit nothing
heavy, had 5 simultaneously this afternoon. But nothing huge.
Mark
On 31 May 2004, at 17:54, James Sherwood wrote:
Thanks Mark,
I have it currently running bypassing the mod_jk with rewrite to port
8080.
The memory has ramped to 327 mb so far which is not anything to worry
about.
I had this problem on our linux box but I had forgotten the -server
option
and that took care of it.
The problem is, windows doesnt accept -server.
Ill continue to monitor it with the mod_jk bypass in.
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 12:19 PM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
I've just set 5.0.25 up and it will run with mod_jk/1.2.3-dev and
Apache/2.0.47 , I'll see if i get the same thing happening.
When i was having problems i was getting a decoding error written to
catalina log, which 5.0.24+ hasn't given me. 5.0.24 has been working
quite happily but the next man mentioned a session error so I took his
word for it and upgraded.
You could have tomcat being served from an ip alias, but will depend
on
you configuration. And might take longer than getting jk sorted.
For the moment I can just say i'll keep and eye on things and see if
the same happens to me.
Mark
On 31 May 2004, at 14:23, James Sherwood wrote:
There are no errors anywhere that I can find in any logs. The memory
just
slowly ramps up till an out of memory error happens.
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 9:04 AM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
What does your catalina log have to say for itself?
On 31 May 2004, at 13:59, James Sherwood wrote:
As I posted before, I get a memory leak using mod_jk 1.2 with
Tomcat
5.0.25
and Apache 2.049
I beleive it may be related to the mod_jk connector and since I am
not
actually serving up anything with apache yet I want to just bypass
the
connector for 1 site and hit tomcat directly. I have to use apache
for
other
things on the server so I cannot just use tomcat.
Any idea the best route for this? (of course a fix for the leak is
the
best
route:)
My route works but certian urls within the site do not
work(although
I
think
I could get them working).
The way I have done it is this:
VirtualHost *
ServerName mysite.ca
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www\.mysite\.ca$ [NC]
RewriteRule ^(.*) http://localhost:8080$1 [p]
/VirtualHost
Thanks, James
---
--
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]
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
I have this in our startup scripts
export CATALINA_OPTS=-Djava.awt.headless=true -Xmx128m -Xdebug
Perhaps the debug argument might reveal something. I cant be much help
on windows matters as I try not to get involved with anything like
that.
My app is still running, but linux not windows so i don't know how far
i can compare. I also have no idea about compiling jk under windows,
i've always found that I've needed to compile jk often with the head
version out of cvs (there's always a fix thats needed somewhere).
Mark
On 1 Jun 2004, at 13:05, James Sherwood wrote:
Ran out of memory last night again
Set to 512m and ran out at 284m
Maybe I am missing a paramater in the tomcat setup on windows or
something
Frustrating
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 4:04 PM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
300 mb sounds a lot, i've got a hibernate and struts flavored app
running with a 128 limit, and thats being generous.
I haven't measured anything but top looks happy, with 5.0.25 with jk
to
apache 2.0.47. Had a bit of traffic this afternoon albeit nothing
heavy, had 5 simultaneously this afternoon. But nothing huge.
Mark
On 31 May 2004, at 17:54, James Sherwood wrote:
Thanks Mark,
I have it currently running bypassing the mod_jk with rewrite to port
8080.
The memory has ramped to 327 mb so far which is not anything to worry
about.
I had this problem on our linux box but I had forgotten the -server
option
and that took care of it.
The problem is, windows doesnt accept -server.
Ill continue to monitor it with the mod_jk bypass in.
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 12:19 PM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
I've just set 5.0.25 up and it will run with mod_jk/1.2.3-dev and
Apache/2.0.47 , I'll see if i get the same thing happening.
When i was having problems i was getting a decoding error written to
catalina log, which 5.0.24+ hasn't given me. 5.0.24 has been working
quite happily but the next man mentioned a session error so I took
his
word for it and upgraded.
You could have tomcat being served from an ip alias, but will depend
on
you configuration. And might take longer than getting jk sorted.
For the moment I can just say i'll keep and eye on things and see if
the same happens to me.
Mark
On 31 May 2004, at 14:23, James Sherwood wrote:
There are no errors anywhere that I can find in any logs. The
memory
just
slowly ramps up till an out of memory error happens.
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 9:04 AM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
What does your catalina log have to say for itself?
On 31 May 2004, at 13:59, James Sherwood wrote:
As I posted before, I get a memory leak using mod_jk 1.2 with
Tomcat
5.0.25
and Apache 2.049
I beleive it may be related to the mod_jk connector and since I
am
not
actually serving up anything with apache yet I want to just
bypass
the
connector for 1 site and hit tomcat directly. I have to use
apache
for
other
things on the server so I cannot just use tomcat.
Any idea the best route for this? (of course a fix for the leak
is
the
best
route:)
My route works but certian urls within the site do not
work(although
I
think
I could get them working).
The way I have done it is this:
VirtualHost *
ServerName mysite.ca
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www\.mysite\.ca$ [NC]
RewriteRule ^(.*) http://localhost:8080$1 [p]
/VirtualHost
Thanks, James
-
--
--
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]
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL
RE: Tomcat5/mod_jk Memory Leak/mod_jk bypass
Hi Mark,
This option
-Xmx128m
Will cause OutOfMemory for you,
As it basically sets maximum Java heap size, which will cause JVM to
through whenever the limit is reached. Set it to a high value.
Chall,
-Original Message-
From: Mark Lowe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 01, 2004 4:55 PM
To: Tomcat Users List
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
I have this in our startup scripts
export CATALINA_OPTS=-Djava.awt.headless=true -Xmx128m -Xdebug
Perhaps the debug argument might reveal something. I cant be much help
on windows matters as I try not to get involved with anything like that.
My app is still running, but linux not windows so i don't know how far i
can compare. I also have no idea about compiling jk under windows, i've
always found that I've needed to compile jk often with the head version
out of cvs (there's always a fix thats needed somewhere).
Mark
On 1 Jun 2004, at 13:05, James Sherwood wrote:
Ran out of memory last night again
Set to 512m and ran out at 284m
Maybe I am missing a paramater in the tomcat setup on windows or
something
Frustrating
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 4:04 PM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
300 mb sounds a lot, i've got a hibernate and struts flavored app
running with a 128 limit, and thats being generous.
I haven't measured anything but top looks happy, with 5.0.25 with jk
to apache 2.0.47. Had a bit of traffic this afternoon albeit nothing
heavy, had 5 simultaneously this afternoon. But nothing huge.
Mark
On 31 May 2004, at 17:54, James Sherwood wrote:
Thanks Mark,
I have it currently running bypassing the mod_jk with rewrite to
port 8080.
The memory has ramped to 327 mb so far which is not anything to
worry about.
I had this problem on our linux box but I had forgotten the -server
option and that took care of it.
The problem is, windows doesnt accept -server.
Ill continue to monitor it with the mod_jk bypass in.
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 12:19 PM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
I've just set 5.0.25 up and it will run with mod_jk/1.2.3-dev and
Apache/2.0.47 , I'll see if i get the same thing happening.
When i was having problems i was getting a decoding error written
to catalina log, which 5.0.24+ hasn't given me. 5.0.24 has been
working quite happily but the next man mentioned a session error so
I took his word for it and upgraded.
You could have tomcat being served from an ip alias, but will
depend on you configuration. And might take longer than getting jk
sorted.
For the moment I can just say i'll keep and eye on things and see
if the same happens to me.
Mark
On 31 May 2004, at 14:23, James Sherwood wrote:
There are no errors anywhere that I can find in any logs. The
memory just slowly ramps up till an out of memory error happens.
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 9:04 AM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
What does your catalina log have to say for itself?
On 31 May 2004, at 13:59, James Sherwood wrote:
As I posted before, I get a memory leak using mod_jk 1.2 with
Tomcat
5.0.25
and Apache 2.049
I beleive it may be related to the mod_jk connector and since I
am not actually serving up anything with apache yet I want to
just bypass the connector for 1 site and hit tomcat directly. I
have to use apache for other things on the server so I cannot
just use tomcat.
Any idea the best route for this? (of course a fix for the leak
is the best
route:)
My route works but certian urls within the site do not
work(although I think I could get them working).
The way I have done it is this:
VirtualHost *
ServerName mysite.ca
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www\.mysite\.ca$ [NC]
RewriteRule ^(.*) http://localhost:8080$1 [p]
/VirtualHost
Thanks, James
-
--
--
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED
RE: Tomcat5/mod_jk Memory Leak/mod_jk bypass
Hi James,
You have said
windows doesnt accept -server
I believe you have either
- Installed the pre 1.3.0 version of JVM
- Your %JAVA_HOME%/bin does not have this server directory
For the second part what you can do is copy everything (only jvm.dll is
required mostly)
'%JAVA_HOME%/jre/bin/server' to '%JAVA_HOME%/bin' directory
And
use this '-Xms256m -Xms512m'
Changa fer,
-Original Message-
From: Mark Lowe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 01, 2004 4:55 PM
To: Tomcat Users List
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
I have this in our startup scripts
export CATALINA_OPTS=-Djava.awt.headless=true -Xmx128m -Xdebug
Perhaps the debug argument might reveal something. I cant be much help
on windows matters as I try not to get involved with anything like that.
My app is still running, but linux not windows so i don't know how far i
can compare. I also have no idea about compiling jk under windows, i've
always found that I've needed to compile jk often with the head version
out of cvs (there's always a fix thats needed somewhere).
Mark
On 1 Jun 2004, at 13:05, James Sherwood wrote:
Ran out of memory last night again
Set to 512m and ran out at 284m
Maybe I am missing a paramater in the tomcat setup on windows or
something
Frustrating
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 4:04 PM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
300 mb sounds a lot, i've got a hibernate and struts flavored app
running with a 128 limit, and thats being generous.
I haven't measured anything but top looks happy, with 5.0.25 with jk
to apache 2.0.47. Had a bit of traffic this afternoon albeit nothing
heavy, had 5 simultaneously this afternoon. But nothing huge.
Mark
On 31 May 2004, at 17:54, James Sherwood wrote:
Thanks Mark,
I have it currently running bypassing the mod_jk with rewrite to
port 8080.
The memory has ramped to 327 mb so far which is not anything to
worry about.
I had this problem on our linux box but I had forgotten the -server
option and that took care of it.
The problem is, windows doesnt accept -server.
Ill continue to monitor it with the mod_jk bypass in.
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 12:19 PM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
I've just set 5.0.25 up and it will run with mod_jk/1.2.3-dev and
Apache/2.0.47 , I'll see if i get the same thing happening.
When i was having problems i was getting a decoding error written
to catalina log, which 5.0.24+ hasn't given me. 5.0.24 has been
working quite happily but the next man mentioned a session error so
I took his word for it and upgraded.
You could have tomcat being served from an ip alias, but will
depend on you configuration. And might take longer than getting jk
sorted.
For the moment I can just say i'll keep and eye on things and see
if the same happens to me.
Mark
On 31 May 2004, at 14:23, James Sherwood wrote:
There are no errors anywhere that I can find in any logs. The
memory just slowly ramps up till an out of memory error happens.
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 9:04 AM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
What does your catalina log have to say for itself?
On 31 May 2004, at 13:59, James Sherwood wrote:
As I posted before, I get a memory leak using mod_jk 1.2 with
Tomcat
5.0.25
and Apache 2.049
I beleive it may be related to the mod_jk connector and since I
am not actually serving up anything with apache yet I want to
just bypass the connector for 1 site and hit tomcat directly. I
have to use apache for other things on the server so I cannot
just use tomcat.
Any idea the best route for this? (of course a fix for the leak
is the best
route:)
My route works but certian urls within the site do not
work(although I think I could get them working).
The way I have done it is this:
VirtualHost *
ServerName mysite.ca
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www\.mysite\.ca$ [NC]
RewriteRule ^(.*) http://localhost:8080$1 [p]
/VirtualHost
Thanks, James
-
--
--
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: Tomcat5/mod_jk Memory Leak/mod_jk bypass
Been fine up until now.
I want to limit the ram assigned to each webapp, but if this is the
wrong way of doing this then I'd appreciate being told what the correct
argument would be.
The only out of memory problems I had were caused by some shadiness
between jk and coyote. but seems to be sorted now.
Thanks
Mark
On 1 Jun 2004, at 14:16, [EMAIL PROTECTED] wrote:
Hi Mark,
This option
-Xmx128m
Will cause OutOfMemory for you,
As it basically sets maximum Java heap size, which will cause JVM to
through whenever the limit is reached. Set it to a high value.
Chall,
-Original Message-
From: Mark Lowe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 01, 2004 4:55 PM
To: Tomcat Users List
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
I have this in our startup scripts
export CATALINA_OPTS=-Djava.awt.headless=true -Xmx128m -Xdebug
Perhaps the debug argument might reveal something. I cant be much help
on windows matters as I try not to get involved with anything like
that.
My app is still running, but linux not windows so i don't know how far
i
can compare. I also have no idea about compiling jk under windows, i've
always found that I've needed to compile jk often with the head version
out of cvs (there's always a fix thats needed somewhere).
Mark
On 1 Jun 2004, at 13:05, James Sherwood wrote:
Ran out of memory last night again
Set to 512m and ran out at 284m
Maybe I am missing a paramater in the tomcat setup on windows or
something
Frustrating
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 4:04 PM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
300 mb sounds a lot, i've got a hibernate and struts flavored app
running with a 128 limit, and thats being generous.
I haven't measured anything but top looks happy, with 5.0.25 with jk
to apache 2.0.47. Had a bit of traffic this afternoon albeit nothing
heavy, had 5 simultaneously this afternoon. But nothing huge.
Mark
On 31 May 2004, at 17:54, James Sherwood wrote:
Thanks Mark,
I have it currently running bypassing the mod_jk with rewrite to
port 8080.
The memory has ramped to 327 mb so far which is not anything to
worry about.
I had this problem on our linux box but I had forgotten the -server
option and that took care of it.
The problem is, windows doesnt accept -server.
Ill continue to monitor it with the mod_jk bypass in.
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 12:19 PM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
I've just set 5.0.25 up and it will run with mod_jk/1.2.3-dev and
Apache/2.0.47 , I'll see if i get the same thing happening.
When i was having problems i was getting a decoding error written
to catalina log, which 5.0.24+ hasn't given me. 5.0.24 has been
working quite happily but the next man mentioned a session error so
I took his word for it and upgraded.
You could have tomcat being served from an ip alias, but will
depend on you configuration. And might take longer than getting jk
sorted.
For the moment I can just say i'll keep and eye on things and see
if the same happens to me.
Mark
On 31 May 2004, at 14:23, James Sherwood wrote:
There are no errors anywhere that I can find in any logs. The
memory just slowly ramps up till an out of memory error happens.
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 9:04 AM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
What does your catalina log have to say for itself?
On 31 May 2004, at 13:59, James Sherwood wrote:
As I posted before, I get a memory leak using mod_jk 1.2 with
Tomcat
5.0.25
and Apache 2.049
I beleive it may be related to the mod_jk connector and since I
am not actually serving up anything with apache yet I want to
just bypass the connector for 1 site and hit tomcat directly. I
have to use apache for other things on the server so I cannot
just use tomcat.
Any idea the best route for this? (of course a fix for the leak
is the best
route:)
My route works but certian urls within the site do not
work(although I think I could get them working).
The way I have done it is this:
VirtualHost *
ServerName mysite.ca
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www\.mysite\.ca$ [NC]
RewriteRule ^(.*) http://localhost:8080$1 [p]
/VirtualHost
Thanks, James
-
--
--
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
Tomcat5/mod_jk Memory Leak/mod_jk bypass
As I posted before, I get a memory leak using mod_jk 1.2 with Tomcat 5.0.25
and Apache 2.049
I beleive it may be related to the mod_jk connector and since I am not
actually serving up anything with apache yet I want to just bypass the
connector for 1 site and hit tomcat directly. I have to use apache for other
things on the server so I cannot just use tomcat.
Any idea the best route for this? (of course a fix for the leak is the best
route:)
My route works but certian urls within the site do not work(although I think
I could get them working).
The way I have done it is this:
VirtualHost *
ServerName mysite.ca
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www\.mysite\.ca$ [NC]
RewriteRule ^(.*) http://localhost:8080$1 [p]
/VirtualHost
Thanks, James
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
What does your catalina log have to say for itself?
On 31 May 2004, at 13:59, James Sherwood wrote:
As I posted before, I get a memory leak using mod_jk 1.2 with Tomcat
5.0.25
and Apache 2.049
I beleive it may be related to the mod_jk connector and since I am not
actually serving up anything with apache yet I want to just bypass the
connector for 1 site and hit tomcat directly. I have to use apache for
other
things on the server so I cannot just use tomcat.
Any idea the best route for this? (of course a fix for the leak is the
best
route:)
My route works but certian urls within the site do not work(although I
think
I could get them working).
The way I have done it is this:
VirtualHost *
ServerName mysite.ca
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www\.mysite\.ca$ [NC]
RewriteRule ^(.*) http://localhost:8080$1 [p]
/VirtualHost
Thanks, James
-
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: Tomcat5/mod_jk Memory Leak/mod_jk bypass
There are no errors anywhere that I can find in any logs. The memory just
slowly ramps up till an out of memory error happens.
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 9:04 AM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
What does your catalina log have to say for itself?
On 31 May 2004, at 13:59, James Sherwood wrote:
As I posted before, I get a memory leak using mod_jk 1.2 with Tomcat
5.0.25
and Apache 2.049
I beleive it may be related to the mod_jk connector and since I am not
actually serving up anything with apache yet I want to just bypass the
connector for 1 site and hit tomcat directly. I have to use apache for
other
things on the server so I cannot just use tomcat.
Any idea the best route for this? (of course a fix for the leak is the
best
route:)
My route works but certian urls within the site do not work(although I
think
I could get them working).
The way I have done it is this:
VirtualHost *
ServerName mysite.ca
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www\.mysite\.ca$ [NC]
RewriteRule ^(.*) http://localhost:8080$1 [p]
/VirtualHost
Thanks, James
-
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: Tomcat5/mod_jk Memory Leak/mod_jk bypass
I've just set 5.0.25 up and it will run with mod_jk/1.2.3-dev and
Apache/2.0.47 , I'll see if i get the same thing happening.
When i was having problems i was getting a decoding error written to
catalina log, which 5.0.24+ hasn't given me. 5.0.24 has been working
quite happily but the next man mentioned a session error so I took his
word for it and upgraded.
You could have tomcat being served from an ip alias, but will depend on
you configuration. And might take longer than getting jk sorted.
For the moment I can just say i'll keep and eye on things and see if
the same happens to me.
Mark
On 31 May 2004, at 14:23, James Sherwood wrote:
There are no errors anywhere that I can find in any logs. The memory
just
slowly ramps up till an out of memory error happens.
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 9:04 AM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
What does your catalina log have to say for itself?
On 31 May 2004, at 13:59, James Sherwood wrote:
As I posted before, I get a memory leak using mod_jk 1.2 with Tomcat
5.0.25
and Apache 2.049
I beleive it may be related to the mod_jk connector and since I am
not
actually serving up anything with apache yet I want to just bypass
the
connector for 1 site and hit tomcat directly. I have to use apache
for
other
things on the server so I cannot just use tomcat.
Any idea the best route for this? (of course a fix for the leak is
the
best
route:)
My route works but certian urls within the site do not work(although
I
think
I could get them working).
The way I have done it is this:
VirtualHost *
ServerName mysite.ca
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www\.mysite\.ca$ [NC]
RewriteRule ^(.*) http://localhost:8080$1 [p]
/VirtualHost
Thanks, James
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
Thanks Mark,
I have it currently running bypassing the mod_jk with rewrite to port 8080.
The memory has ramped to 327 mb so far which is not anything to worry about.
I had this problem on our linux box but I had forgotten the -server option
and that took care of it.
The problem is, windows doesnt accept -server.
Ill continue to monitor it with the mod_jk bypass in.
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 12:19 PM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
I've just set 5.0.25 up and it will run with mod_jk/1.2.3-dev and
Apache/2.0.47 , I'll see if i get the same thing happening.
When i was having problems i was getting a decoding error written to
catalina log, which 5.0.24+ hasn't given me. 5.0.24 has been working
quite happily but the next man mentioned a session error so I took his
word for it and upgraded.
You could have tomcat being served from an ip alias, but will depend on
you configuration. And might take longer than getting jk sorted.
For the moment I can just say i'll keep and eye on things and see if
the same happens to me.
Mark
On 31 May 2004, at 14:23, James Sherwood wrote:
There are no errors anywhere that I can find in any logs. The memory
just
slowly ramps up till an out of memory error happens.
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 9:04 AM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
What does your catalina log have to say for itself?
On 31 May 2004, at 13:59, James Sherwood wrote:
As I posted before, I get a memory leak using mod_jk 1.2 with Tomcat
5.0.25
and Apache 2.049
I beleive it may be related to the mod_jk connector and since I am
not
actually serving up anything with apache yet I want to just bypass
the
connector for 1 site and hit tomcat directly. I have to use apache
for
other
things on the server so I cannot just use tomcat.
Any idea the best route for this? (of course a fix for the leak is
the
best
route:)
My route works but certian urls within the site do not work(although
I
think
I could get them working).
The way I have done it is this:
VirtualHost *
ServerName mysite.ca
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www\.mysite\.ca$ [NC]
RewriteRule ^(.*) http://localhost:8080$1 [p]
/VirtualHost
Thanks, James
-
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]
-
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: Tomcat5/mod_jk Memory Leak/mod_jk bypass
300 mb sounds a lot, i've got a hibernate and struts flavored app
running with a 128 limit, and thats being generous.
I haven't measured anything but top looks happy, with 5.0.25 with jk to
apache 2.0.47. Had a bit of traffic this afternoon albeit nothing
heavy, had 5 simultaneously this afternoon. But nothing huge.
Mark
On 31 May 2004, at 17:54, James Sherwood wrote:
Thanks Mark,
I have it currently running bypassing the mod_jk with rewrite to port
8080.
The memory has ramped to 327 mb so far which is not anything to worry
about.
I had this problem on our linux box but I had forgotten the -server
option
and that took care of it.
The problem is, windows doesnt accept -server.
Ill continue to monitor it with the mod_jk bypass in.
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 12:19 PM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
I've just set 5.0.25 up and it will run with mod_jk/1.2.3-dev and
Apache/2.0.47 , I'll see if i get the same thing happening.
When i was having problems i was getting a decoding error written to
catalina log, which 5.0.24+ hasn't given me. 5.0.24 has been working
quite happily but the next man mentioned a session error so I took his
word for it and upgraded.
You could have tomcat being served from an ip alias, but will depend
on
you configuration. And might take longer than getting jk sorted.
For the moment I can just say i'll keep and eye on things and see if
the same happens to me.
Mark
On 31 May 2004, at 14:23, James Sherwood wrote:
There are no errors anywhere that I can find in any logs. The memory
just
slowly ramps up till an out of memory error happens.
James
- Original Message -
From: Mark Lowe [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Monday, May 31, 2004 9:04 AM
Subject: Re: Tomcat5/mod_jk Memory Leak/mod_jk bypass
What does your catalina log have to say for itself?
On 31 May 2004, at 13:59, James Sherwood wrote:
As I posted before, I get a memory leak using mod_jk 1.2 with
Tomcat
5.0.25
and Apache 2.049
I beleive it may be related to the mod_jk connector and since I am
not
actually serving up anything with apache yet I want to just bypass
the
connector for 1 site and hit tomcat directly. I have to use apache
for
other
things on the server so I cannot just use tomcat.
Any idea the best route for this? (of course a fix for the leak is
the
best
route:)
My route works but certian urls within the site do not
work(although
I
think
I could get them working).
The way I have done it is this:
VirtualHost *
ServerName mysite.ca
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www\.mysite\.ca$ [NC]
RewriteRule ^(.*) http://localhost:8080$1 [p]
/VirtualHost
Thanks, James
---
--
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]
-
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: Horrible memory leak in tomcat 5.0.19
I'm running out of memory with the msg: ... WARNING: Error registering request May 25, 2004 5:36:44 PM org.apache.tomcat.util.threads.ThreadPool$ControlRunnable run SEVERE: Caught exception (java.lang.OutOfMemoryError) executing [EMAIL PROTECTED], terminating thread May 25, 2004 5:37:05 PM org.apache.jk.common.HandlerRequest invoke INFO: Unknown message 0 java.lang.OutOfMemoryError java.lang.OutOfMemoryError java.lang.OutOfMemoryError ... I've seen a sugestion of the request.registerRequests=false to put in jk2.properties. I'm using mod_jk, but as I see a similar message, I'll try this too. But... where do I put this conf, as mod_jk does not have a jk.properties file. could be it worker.properties? :) thanks in advance Joseph Shraibman wrote: Robert Krüger wrote: Hi, we had the same problem (enormous memory leak which frequently made our production system crash), downgraded to 5.0.18 and everything went back to normal. Just yesterday a colleague of mine came to the conclusion that it is not too unlikely that it is the problem described in the message http://www.mail-archive.com/[EMAIL PROTECTED]/msg53035.html It that is so, you can simply disable the JMX registration of requests to get rid of the problem. We will try that probably later today but of course you can give it a shot yourself. There is not much to lose. I was able to figure out how to reproduce this problem on my test machine (using multiple concurrent requests). I added to my jk2.properties: request.registerRequests=false This got rid of some of the messages in catalina.out but left these: Mar 19, 2004 1:47:51 PM org.apache.jk.common.HandlerRequest invoke INFO: Unknown message 0 Mar 19, 2004 1:47:52 PM org.apache.jk.common.HandlerRequest invoke INFO: Unknown message 0 ... and the memory leak did not go away. The message that I'm not getting anymore are: Mar 19, 2004 1:25:34 PM org.apache.jk.common.HandlerRequest decodeRequest WARNING: Error registering request Mar 19, 2004 1:25:34 PM org.apache.jk.common.HandlerRequest decodeRequest WARNING: Error registering request - 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
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]
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
