RE: Tomcat 4.0.x memory leak (not javac)
Howdy, Happy holidays hopefully devoid of debugging ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 4:15 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) Ok, thanks guys. I'll see what I can do. EXTREMELY busy right now, but I might be able to try it over christmas holidays. :) MAYBE! -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 12:08 PM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, You don't have to know much about the tomcat under the hood to diagnose this. It's not a problem with the tomcat classes. What you need to know is: - What 3rd party libraries does your application use - What classes stay in memory after a reload and have a 2nd instance of them created. You can use a profiler like Senor Hanik suggested (JProbe, OptimizeIt, etc.) to find out the latter. You want to look for a list of objects whose instance count increases after a reload of your webapp. OptimizeIt can do heap snapshot deltas which are the perfect tool here. Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 2:08 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) Ouch, LOL. I don't really know a whole lot about the tomcat under the hood! :) I can try though. Do you have a procedure that I should take to find this? Is there a debugging option that I can turn on for tomcat? -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:45 AM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, Since you can reproduce your error easily, can you narrow down which 3rd party library is keeping the references that cause the memory leak? Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 1:43 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) -Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:01 AM To: Tomcat Users List Subject: Re: Tomcat 4.0.x memory leak (not javac) Shapira, Yoav wrote: Besides what Senor Schultz said (which is 100% true), 1. Where is this mentioned in the release notes, and what would one have to search for? Under KNOWN ISSUES IN THIS RELEASE it does mention issues during web application reloading where shared libraries keep references to objects instantiated by the web application. That says memory leak to me although it doesn't specifically say that. 2. You mentioned in your passage the bug was marked as invalid or wontfix, and the bug you gave below is marked as new. So if anyone actually wasted time (like me) looking up what you said, they didn't find it. All I did was search for memory leak under Tomcat 4 and all status. I was not positive that it was marked WONTFIX, I should have clarified that in my original message. I had thought that the issue was something inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-) Bugzilla is obviously not working sometimes. I searched for memory leak one time and got it. Then I went to search for it for someone else so I could give them the bug number but nothing came up. I did the exact same search, memory leak. Very interesting indeed. Heck, I even searched for just memory or leak once each and came up with nothing. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - 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
Re: Tomcat 4.0.x memory leak (not javac)
We first ran into this bug when hot-deploying JetSpeed - about seven times would cause an out of memory w/ the default heap size. JetSpeed had so many leaks itself that we dropped down to bares bones test app with a servlet, but no JSPs or third party libraries. With this small app would could do a hundred or so deploys or reloads before hitting out of memory. We purchased JProbe to try and further track down the problem. Unfortunately, JProbe appeared to disturb the environment enough that things could not clean up properly anyway. At that point we gave up the hunt. Although we're still using 4.1.x in production, we recently confirmed that the problem still exists in 5.x. In most cases we've been running RedHat 8 with a Sun 4.1 JDK, but we've seen the problem on Windows and MacOS as well. It is easy to reproduce - we used the Ant task to deploy inside a loop. No need to hit any pages or cause JSP's to compile, just redeploying will do it. On Dec 3, 2003, at 7:06 AM, Shapira, Yoav wrote: Howdy, Happy holidays hopefully devoid of debugging ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 4:15 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) Ok, thanks guys. I'll see what I can do. EXTREMELY busy right now, but I might be able to try it over christmas holidays. :) MAYBE! -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 12:08 PM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, You don't have to know much about the tomcat under the hood to diagnose this. It's not a problem with the tomcat classes. What you need to know is: - What 3rd party libraries does your application use - What classes stay in memory after a reload and have a 2nd instance of them created. You can use a profiler like Senor Hanik suggested (JProbe, OptimizeIt, etc.) to find out the latter. You want to look for a list of objects whose instance count increases after a reload of your webapp. OptimizeIt can do heap snapshot deltas which are the perfect tool here. Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 2:08 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) Ouch, LOL. I don't really know a whole lot about the tomcat under the hood! :) I can try though. Do you have a procedure that I should take to find this? Is there a debugging option that I can turn on for tomcat? -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:45 AM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, Since you can reproduce your error easily, can you narrow down which 3rd party library is keeping the references that cause the memory leak? Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 1:43 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) -Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:01 AM To: Tomcat Users List Subject: Re: Tomcat 4.0.x memory leak (not javac) Shapira, Yoav wrote: Besides what Senor Schultz said (which is 100% true), 1. Where is this mentioned in the release notes, and what would one have to search for? Under KNOWN ISSUES IN THIS RELEASE it does mention issues during web application reloading where shared libraries keep references to objects instantiated by the web application. That says memory leak to me although it doesn't specifically say that. 2. You mentioned in your passage the bug was marked as invalid or wontfix, and the bug you gave below is marked as new. So if anyone actually wasted time (like me) looking up what you said, they didn't find it. All I did was search for memory leak under Tomcat 4 and all status. I was not positive that it was marked WONTFIX, I should have clarified that in my original message. I had thought that the issue was something inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-) Bugzilla is obviously not working sometimes. I searched for memory leak one time and got it. Then I went to search for it for someone else so I could give them the bug number but nothing came up. I did the exact same search, memory leak. Very interesting indeed. Heck, I even searched for just memory or leak once each and came up with nothing. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain
RE: Tomcat 4.0.x memory leak (not javac)
I reported a JVM bug to sun yesterday. They mentioned that the problem has been fixed. Coincidently the work around is to increase the memory size that is used to store class objects and related metadata. So I thought, hey, I should try increasing and decreasing this and then reloading my context after a tomcat4 restart. Sure enough, I can make the tomcat4 run out of memory really quickly with a 16M setting. If I set it to 256M, it takes a very long time to run out of memory. In fact, I never seen it run out of memory. I reloaded it 91 times without a problem. With a 16M setting I reloaded 6 times and got an out of memory exception. In my opinion, the class loader for tomcat should keep track of all the classes it's loading. When the context gets reloaded, it should then unload all those classes. I'm not exactly sure if this is even possible, because unloading class variables might be class specific and there might not be a way of actually unloading a class so that those class variable references get discarded. Maybe that's why someone suggested implementing the ServletContextListener (in another thread)? I don't know much about class loaders! :) So, the work around until someone implements a ServletContextListener and unloads their own static variables (probably variable=null is sufficient?) is... -XX:MaxPermSize=128m -XX:PermSize=XXm And an article that the Sun support guy gave me... http://wireless.java.sun.com/midp/articles/garbagecollection2/ Specifically related to -XX flags... http://wireless.java.sun.com/midp/articles/garbagecollection2/#a.5 -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:45 AM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, Since you can reproduce your error easily, can you narrow down which 3rd party library is keeping the references that cause the memory leak? Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 1:43 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) -Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:01 AM To: Tomcat Users List Subject: Re: Tomcat 4.0.x memory leak (not javac) Shapira, Yoav wrote: Besides what Senor Schultz said (which is 100% true), 1. Where is this mentioned in the release notes, and what would one have to search for? Under KNOWN ISSUES IN THIS RELEASE it does mention issues during web application reloading where shared libraries keep references to objects instantiated by the web application. That says memory leak to me although it doesn't specifically say that. 2. You mentioned in your passage the bug was marked as invalid or wontfix, and the bug you gave below is marked as new. So if anyone actually wasted time (like me) looking up what you said, they didn't find it. All I did was search for memory leak under Tomcat 4 and all status. I was not positive that it was marked WONTFIX, I should have clarified that in my original message. I had thought that the issue was something inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-) Bugzilla is obviously not working sometimes. I searched for memory leak one time and got it. Then I went to search for it for someone else so I could give them the bug number but nothing came up. I did the exact same search, memory leak. Very interesting indeed. Heck, I even searched for just memory or leak once each and came up with nothing. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - 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
RE: Tomcat 4.0.x memory leak (not javac)
Howdy, Thanks for posting the follow-up. In my opinion, the class loader for tomcat should keep track of all the classes it's loading. When the context gets reloaded, it should then Great. Now that you have the specs, why don't you submit a patch? ;) discarded. Maybe that's why someone suggested implementing the ServletContextListener (in another thread)? I don't know much about class loaders! :) Not the same thing: the ServletContextListener solves other problems. Yoav Shapira So, the work around until someone implements a ServletContextListener and unloads their own static variables (probably variable=null is sufficient?) is... -XX:MaxPermSize=128m -XX:PermSize=XXm And an article that the Sun support guy gave me... http://wireless.java.sun.com/midp/articles/garbagecollection2/ Specifically related to -XX flags... http://wireless.java.sun.com/midp/articles/garbagecollection2/#a.5 -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:45 AM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, Since you can reproduce your error easily, can you narrow down which 3rd party library is keeping the references that cause the memory leak? Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 1:43 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) -Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:01 AM To: Tomcat Users List Subject: Re: Tomcat 4.0.x memory leak (not javac) Shapira, Yoav wrote: Besides what Senor Schultz said (which is 100% true), 1. Where is this mentioned in the release notes, and what would one have to search for? Under KNOWN ISSUES IN THIS RELEASE it does mention issues during web application reloading where shared libraries keep references to objects instantiated by the web application. That says memory leak to me although it doesn't specifically say that. 2. You mentioned in your passage the bug was marked as invalid or wontfix, and the bug you gave below is marked as new. So if anyone actually wasted time (like me) looking up what you said, they didn't find it. All I did was search for memory leak under Tomcat 4 and all status. I was not positive that it was marked WONTFIX, I should have clarified that in my original message. I had thought that the issue was something inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-) Bugzilla is obviously not working sometimes. I searched for memory leak one time and got it. Then I went to search for it for someone else so I could give them the bug number but nothing came up. I did the exact same search, memory leak. Very interesting indeed. Heck, I even searched for just memory or leak once each and came up with nothing. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - 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] - 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
RE: Tomcat 4.0.x memory leak (not javac)
-Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 3, 2003 11:21 AM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, Thanks for posting the follow-up. In my opinion, the class loader for tomcat should keep track of all the classes it's loading. When the context gets reloaded, it should then Great. Now that you have the specs, why don't you submit a patch? ;) Actually, I would really love to! :) I love programming, and I've really been wanting to take a look at the tomcat code. However, I'm very swamped right now. But, I'll certainly take a look when I get a chance. I have glanced at class loader documentation for the JVM. I can't see anywhere where there's a class unload feature. discarded. Maybe that's why someone suggested implementing the ServletContextListener (in another thread)? I don't know much about class loaders! :) Not the same thing: the ServletContextListener solves other problems. Yoav Shapira So, the work around until someone implements a ServletContextListener and unloads their own static variables (probably variable=null is sufficient?) is... -XX:MaxPermSize=128m -XX:PermSize=XXm And an article that the Sun support guy gave me... http://wireless.java.sun.com/midp/articles/garbagecollection2/ Specifically related to -XX flags... http://wireless.java.sun.com/midp/articles/garbagecollection2/#a.5 -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:45 AM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, Since you can reproduce your error easily, can you narrow down which 3rd party library is keeping the references that cause the memory leak? Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 1:43 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) -Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:01 AM To: Tomcat Users List Subject: Re: Tomcat 4.0.x memory leak (not javac) Shapira, Yoav wrote: Besides what Senor Schultz said (which is 100% true), 1. Where is this mentioned in the release notes, and what would one have to search for? Under KNOWN ISSUES IN THIS RELEASE it does mention issues during web application reloading where shared libraries keep references to objects instantiated by the web application. That says memory leak to me although it doesn't specifically say that. 2. You mentioned in your passage the bug was marked as invalid or wontfix, and the bug you gave below is marked as new. So if anyone actually wasted time (like me) looking up what you said, they didn't find it. All I did was search for memory leak under Tomcat 4 and all status. I was not positive that it was marked WONTFIX, I should have clarified that in my original message. I had thought that the issue was something inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-) Bugzilla is obviously not working sometimes. I searched for memory leak one time and got it. Then I went to search for it for someone else so I could give them the bug number but nothing came up. I did the exact same search, memory leak. Very interesting indeed. Heck, I even searched for just memory or leak once each and came up with nothing. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - 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
RE: Tomcat 4.0.x memory leak (not javac)
-Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 3, 2003 11:21 AM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, Thanks for posting the follow-up. In my opinion, the class loader for tomcat should keep track of all the classes it's loading. When the context gets reloaded, it should then Great. Now that you have the specs, why don't you submit a patch? ;) I was looking at WebappClassLoader.java. I noticed that inside the stop () method there is a call to resourceEntries.clear (). I'm kind of wondering if maybe this shouldn't be there! It's clearing the cache of loaded classes. So, it thinks it needs to reload them next time. Is this right? discarded. Maybe that's why someone suggested implementing the ServletContextListener (in another thread)? I don't know much about class loaders! :) Not the same thing: the ServletContextListener solves other problems. Yoav Shapira So, the work around until someone implements a ServletContextListener and unloads their own static variables (probably variable=null is sufficient?) is... -XX:MaxPermSize=128m -XX:PermSize=XXm And an article that the Sun support guy gave me... http://wireless.java.sun.com/midp/articles/garbagecollection2/ Specifically related to -XX flags... http://wireless.java.sun.com/midp/articles/garbagecollection2/#a.5 -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:45 AM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, Since you can reproduce your error easily, can you narrow down which 3rd party library is keeping the references that cause the memory leak? Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 1:43 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) -Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:01 AM To: Tomcat Users List Subject: Re: Tomcat 4.0.x memory leak (not javac) Shapira, Yoav wrote: Besides what Senor Schultz said (which is 100% true), 1. Where is this mentioned in the release notes, and what would one have to search for? Under KNOWN ISSUES IN THIS RELEASE it does mention issues during web application reloading where shared libraries keep references to objects instantiated by the web application. That says memory leak to me although it doesn't specifically say that. 2. You mentioned in your passage the bug was marked as invalid or wontfix, and the bug you gave below is marked as new. So if anyone actually wasted time (like me) looking up what you said, they didn't find it. All I did was search for memory leak under Tomcat 4 and all status. I was not positive that it was marked WONTFIX, I should have clarified that in my original message. I had thought that the issue was something inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-) Bugzilla is obviously not working sometimes. I searched for memory leak one time and got it. Then I went to search for it for someone else so I could give them the bug number but nothing came up. I did the exact same search, memory leak. Very interesting indeed. Heck, I even searched for just memory or leak once each and came up with nothing. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - 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
RE: Tomcat 4.0.x memory leak (not javac)
-Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: December 3, 2003 12:45 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 3, 2003 11:21 AM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, Thanks for posting the follow-up. In my opinion, the class loader for tomcat should keep track of all the classes it's loading. When the context gets reloaded, it should then Great. Now that you have the specs, why don't you submit a patch? ;) I was looking at WebappClassLoader.java. I noticed that inside the stop () method there is a call to resourceEntries.clear (). I'm kind of wondering if maybe this shouldn't be there! It's clearing the cache of loaded classes. So, it thinks it needs to reload them next time. Is this right? Actually, it calls the findLoadedClass () as well so that should cover it. hmmm. discarded. Maybe that's why someone suggested implementing the ServletContextListener (in another thread)? I don't know much about class loaders! :) Not the same thing: the ServletContextListener solves other problems. Yoav Shapira So, the work around until someone implements a ServletContextListener and unloads their own static variables (probably variable=null is sufficient?) is... -XX:MaxPermSize=128m -XX:PermSize=XXm And an article that the Sun support guy gave me... http://wireless.java.sun.com/midp/articles/garbagecollection2/ Specifically related to -XX flags... http://wireless.java.sun.com/midp/articles/garbagecollection2/#a.5 -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:45 AM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, Since you can reproduce your error easily, can you narrow down which 3rd party library is keeping the references that cause the memory leak? Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 1:43 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) -Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:01 AM To: Tomcat Users List Subject: Re: Tomcat 4.0.x memory leak (not javac) Shapira, Yoav wrote: Besides what Senor Schultz said (which is 100% true), 1. Where is this mentioned in the release notes, and what would one have to search for? Under KNOWN ISSUES IN THIS RELEASE it does mention issues during web application reloading where shared libraries keep references to objects instantiated by the web application. That says memory leak to me although it doesn't specifically say that. 2. You mentioned in your passage the bug was marked as invalid or wontfix, and the bug you gave below is marked as new. So if anyone actually wasted time (like me) looking up what you said, they didn't find it. All I did was search for memory leak under Tomcat 4 and all status. I was not positive that it was marked WONTFIX, I should have clarified that in my original message. I had thought that the issue was something inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-) Bugzilla is obviously not working sometimes. I searched for memory leak one time and got it. Then I went to search for it for someone else so I could give them the bug number but nothing came up. I did the exact same search, memory leak. Very interesting indeed. Heck, I even searched for just memory or leak once each and came up with nothing. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
Re: Tomcat 4.0.x memory leak (not javac)
Christopher Schultz wrote: We're having a problem with tomcat 4.0.4. Every time a context is reloaded it leaks memory. It's a known bug, but not fixed in 4.1.x, it still exists there. I am not sure if it still exists in 5.0.x. Can you provide a bug number or a link? I'd like to take a look at it. Come on people, a simple search of the release notes an another of bugzilla quickly turns up the relevant information. http://www.apache.org/dist/jakarta/tomcat-4/v4.1.29/RELEASE-NOTES http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20758 -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.0.x memory leak (not javac)
All, http://www.apache.org/dist/jakarta/tomcat-4/v4.1.29/RELEASE-NOTES http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20758 Uhhh... this looks like standard operating procedure for Java to me... When you dump a ClassLoader and all of it's object get GC'd, the VM almost never GC's the unused classes. The new ClassLoader re-loads all those classes, again, and you get new versions of those classes loaded into the VM. Even if there are no more instances of those classes, I thought they stuck around... I was not suprised by anything mentioned in that bug. The only thing that's a shame is the fact that it's true, and it does interfere with the ability of an app server to re-load contexts indefinately. :( The -Xnoclassgc option still exists for the 1.4.1 VM, so maybe I'm completely wrong, here. :) -chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.0.x memory leak (not javac)
Howdy, Besides what Senor Schultz said (which is 100% true), 1. Where is this mentioned in the release notes, and what would one have to search for? 2. You mentioned in your passage the bug was marked as invalid or wontfix, and the bug you gave below is marked as new. So if anyone actually wasted time (like me) looking up what you said, they didn't find it. Yoav Shapira Millennium ChemInformatics -Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 3:33 AM To: Tomcat Users List Subject: Re: Tomcat 4.0.x memory leak (not javac) Christopher Schultz wrote: We're having a problem with tomcat 4.0.4. Every time a context is reloaded it leaks memory. It's a known bug, but not fixed in 4.1.x, it still exists there. I am not sure if it still exists in 5.0.x. Can you provide a bug number or a link? I'd like to take a look at it. Come on people, a simple search of the release notes an another of bugzilla quickly turns up the relevant information. http://www.apache.org/dist/jakarta/tomcat-4/v4.1.29/RELEASE-NOTES http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20758 -Dave - 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: Tomcat 4.0.x memory leak (not javac)
Shapira, Yoav wrote: Besides what Senor Schultz said (which is 100% true), 1. Where is this mentioned in the release notes, and what would one have to search for? Under KNOWN ISSUES IN THIS RELEASE it does mention issues during web application reloading where shared libraries keep references to objects instantiated by the web application. That says memory leak to me although it doesn't specifically say that. 2. You mentioned in your passage the bug was marked as invalid or wontfix, and the bug you gave below is marked as new. So if anyone actually wasted time (like me) looking up what you said, they didn't find it. All I did was search for memory leak under Tomcat 4 and all status. I was not positive that it was marked WONTFIX, I should have clarified that in my original message. I had thought that the issue was something inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-) -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.0.x memory leak (not javac)
Howdy, Under KNOWN ISSUES IN THIS RELEASE it does mention issues during web application reloading where shared libraries keep references to objects instantiated by the web application. That says memory leak to me although it doesn't specifically say that. I see what you mean. I was searching for leak or memory and found stuff unrelated to this issue. All I did was search for memory leak under Tomcat 4 and all status. I was not positive that it was marked WONTFIX, I should have clarified that in my original message. I had thought that the issue was something Yup, I was searching for INVALID or WONTFIX resolutions for tomcat 4. inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-) It's a tough one because of the plethora of 3rd party libraries that use such static variables or threads, leaving tomcat without much choice. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.0.x memory leak (not javac)
Shapira, Yoav wrote: inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-) It's a tough one because of the plethora of 3rd party libraries that use such static variables or threads, leaving tomcat without much choice. If it was easy to fix, I'm sure that someone would have fixed it by now. I haven't had time to test it myself, but it would be interesting to see if the same issue does exist in Tomcat 5. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.0.x memory leak (not javac)
-Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:01 AM To: Tomcat Users List Subject: Re: Tomcat 4.0.x memory leak (not javac) Shapira, Yoav wrote: Besides what Senor Schultz said (which is 100% true), 1. Where is this mentioned in the release notes, and what would one have to search for? Under KNOWN ISSUES IN THIS RELEASE it does mention issues during web application reloading where shared libraries keep references to objects instantiated by the web application. That says memory leak to me although it doesn't specifically say that. 2. You mentioned in your passage the bug was marked as invalid or wontfix, and the bug you gave below is marked as new. So if anyone actually wasted time (like me) looking up what you said, they didn't find it. All I did was search for memory leak under Tomcat 4 and all status. I was not positive that it was marked WONTFIX, I should have clarified that in my original message. I had thought that the issue was something inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-) Bugzilla is obviously not working sometimes. I searched for memory leak one time and got it. Then I went to search for it for someone else so I could give them the bug number but nothing came up. I did the exact same search, memory leak. Very interesting indeed. Heck, I even searched for just memory or leak once each and came up with nothing. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.0.x memory leak (not javac)
Howdy, Since you can reproduce your error easily, can you narrow down which 3rd party library is keeping the references that cause the memory leak? Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 1:43 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) -Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:01 AM To: Tomcat Users List Subject: Re: Tomcat 4.0.x memory leak (not javac) Shapira, Yoav wrote: Besides what Senor Schultz said (which is 100% true), 1. Where is this mentioned in the release notes, and what would one have to search for? Under KNOWN ISSUES IN THIS RELEASE it does mention issues during web application reloading where shared libraries keep references to objects instantiated by the web application. That says memory leak to me although it doesn't specifically say that. 2. You mentioned in your passage the bug was marked as invalid or wontfix, and the bug you gave below is marked as new. So if anyone actually wasted time (like me) looking up what you said, they didn't find it. All I did was search for memory leak under Tomcat 4 and all status. I was not positive that it was marked WONTFIX, I should have clarified that in my original message. I had thought that the issue was something inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-) Bugzilla is obviously not working sometimes. I searched for memory leak one time and got it. Then I went to search for it for someone else so I could give them the bug number but nothing came up. I did the exact same search, memory leak. Very interesting indeed. Heck, I even searched for just memory or leak once each and came up with nothing. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - 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: Tomcat 4.0.x memory leak (not javac)
Ouch, LOL. I don't really know a whole lot about the tomcat under the hood! :) I can try though. Do you have a procedure that I should take to find this? Is there a debugging option that I can turn on for tomcat? -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:45 AM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, Since you can reproduce your error easily, can you narrow down which 3rd party library is keeping the references that cause the memory leak? Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 1:43 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) -Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:01 AM To: Tomcat Users List Subject: Re: Tomcat 4.0.x memory leak (not javac) Shapira, Yoav wrote: Besides what Senor Schultz said (which is 100% true), 1. Where is this mentioned in the release notes, and what would one have to search for? Under KNOWN ISSUES IN THIS RELEASE it does mention issues during web application reloading where shared libraries keep references to objects instantiated by the web application. That says memory leak to me although it doesn't specifically say that. 2. You mentioned in your passage the bug was marked as invalid or wontfix, and the bug you gave below is marked as new. So if anyone actually wasted time (like me) looking up what you said, they didn't find it. All I did was search for memory leak under Tomcat 4 and all status. I was not positive that it was marked WONTFIX, I should have clarified that in my original message. I had thought that the issue was something inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-) Bugzilla is obviously not working sometimes. I searched for memory leak one time and got it. Then I went to search for it for someone else so I could give them the bug number but nothing came up. I did the exact same search, memory leak. Very interesting indeed. Heck, I even searched for just memory or leak once each and came up with nothing. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.0.x memory leak (not javac)
download a trial of JProbe :) Filip - Original Message - From: Trenton D. Adams [EMAIL PROTECTED] To: 'Tomcat Users List' [EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 11:08 AM Subject: RE: Tomcat 4.0.x memory leak (not javac) Ouch, LOL. I don't really know a whole lot about the tomcat under the hood! :) I can try though. Do you have a procedure that I should take to find this? Is there a debugging option that I can turn on for tomcat? -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:45 AM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, Since you can reproduce your error easily, can you narrow down which 3rd party library is keeping the references that cause the memory leak? Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 1:43 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) -Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:01 AM To: Tomcat Users List Subject: Re: Tomcat 4.0.x memory leak (not javac) Shapira, Yoav wrote: Besides what Senor Schultz said (which is 100% true), 1. Where is this mentioned in the release notes, and what would one have to search for? Under KNOWN ISSUES IN THIS RELEASE it does mention issues during web application reloading where shared libraries keep references to objects instantiated by the web application. That says memory leak to me although it doesn't specifically say that. 2. You mentioned in your passage the bug was marked as invalid or wontfix, and the bug you gave below is marked as new. So if anyone actually wasted time (like me) looking up what you said, they didn't find it. All I did was search for memory leak under Tomcat 4 and all status. I was not positive that it was marked WONTFIX, I should have clarified that in my original message. I had thought that the issue was something inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-) Bugzilla is obviously not working sometimes. I searched for memory leak one time and got it. Then I went to search for it for someone else so I could give them the bug number but nothing came up. I did the exact same search, memory leak. Very interesting indeed. Heck, I even searched for just memory or leak once each and came up with nothing. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - 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] - 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: Tomcat 4.0.x memory leak (not javac)
Howdy, You don't have to know much about the tomcat under the hood to diagnose this. It's not a problem with the tomcat classes. What you need to know is: - What 3rd party libraries does your application use - What classes stay in memory after a reload and have a 2nd instance of them created. You can use a profiler like Senor Hanik suggested (JProbe, OptimizeIt, etc.) to find out the latter. You want to look for a list of objects whose instance count increases after a reload of your webapp. OptimizeIt can do heap snapshot deltas which are the perfect tool here. Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 2:08 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) Ouch, LOL. I don't really know a whole lot about the tomcat under the hood! :) I can try though. Do you have a procedure that I should take to find this? Is there a debugging option that I can turn on for tomcat? -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:45 AM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, Since you can reproduce your error easily, can you narrow down which 3rd party library is keeping the references that cause the memory leak? Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 1:43 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) -Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:01 AM To: Tomcat Users List Subject: Re: Tomcat 4.0.x memory leak (not javac) Shapira, Yoav wrote: Besides what Senor Schultz said (which is 100% true), 1. Where is this mentioned in the release notes, and what would one have to search for? Under KNOWN ISSUES IN THIS RELEASE it does mention issues during web application reloading where shared libraries keep references to objects instantiated by the web application. That says memory leak to me although it doesn't specifically say that. 2. You mentioned in your passage the bug was marked as invalid or wontfix, and the bug you gave below is marked as new. So if anyone actually wasted time (like me) looking up what you said, they didn't find it. All I did was search for memory leak under Tomcat 4 and all status. I was not positive that it was marked WONTFIX, I should have clarified that in my original message. I had thought that the issue was something inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-) Bugzilla is obviously not working sometimes. I searched for memory leak one time and got it. Then I went to search for it for someone else so I could give them the bug number but nothing came up. I did the exact same search, memory leak. Very interesting indeed. Heck, I even searched for just memory or leak once each and came up with nothing. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - 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] - 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
RE: Tomcat 4.0.x memory leak (not javac)
Ok, thanks guys. I'll see what I can do. EXTREMELY busy right now, but I might be able to try it over christmas holidays. :) MAYBE! -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 12:08 PM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, You don't have to know much about the tomcat under the hood to diagnose this. It's not a problem with the tomcat classes. What you need to know is: - What 3rd party libraries does your application use - What classes stay in memory after a reload and have a 2nd instance of them created. You can use a profiler like Senor Hanik suggested (JProbe, OptimizeIt, etc.) to find out the latter. You want to look for a list of objects whose instance count increases after a reload of your webapp. OptimizeIt can do heap snapshot deltas which are the perfect tool here. Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 2:08 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) Ouch, LOL. I don't really know a whole lot about the tomcat under the hood! :) I can try though. Do you have a procedure that I should take to find this? Is there a debugging option that I can turn on for tomcat? -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:45 AM To: Tomcat Users List Subject: RE: Tomcat 4.0.x memory leak (not javac) Howdy, Since you can reproduce your error easily, can you narrow down which 3rd party library is keeping the references that cause the memory leak? Yoav Shapira Millennium ChemInformatics -Original Message- From: Trenton D. Adams [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 02, 2003 1:43 PM To: 'Tomcat Users List' Subject: RE: Tomcat 4.0.x memory leak (not javac) -Original Message- From: David Rees [mailto:[EMAIL PROTECTED] Sent: December 2, 2003 11:01 AM To: Tomcat Users List Subject: Re: Tomcat 4.0.x memory leak (not javac) Shapira, Yoav wrote: Besides what Senor Schultz said (which is 100% true), 1. Where is this mentioned in the release notes, and what would one have to search for? Under KNOWN ISSUES IN THIS RELEASE it does mention issues during web application reloading where shared libraries keep references to objects instantiated by the web application. That says memory leak to me although it doesn't specifically say that. 2. You mentioned in your passage the bug was marked as invalid or wontfix, and the bug you gave below is marked as new. So if anyone actually wasted time (like me) looking up what you said, they didn't find it. All I did was search for memory leak under Tomcat 4 and all status. I was not positive that it was marked WONTFIX, I should have clarified that in my original message. I had thought that the issue was something inherent to the design of Tomcat 4 (which was overhauled in Tomcat 5), but I'm sure that they are willing to accept patches if anyone can fix it. ;-) Bugzilla is obviously not working sometimes. I searched for memory leak one time and got it. Then I went to search for it for someone else so I could give them the bug number but nothing came up. I did the exact same search, memory leak. Very interesting indeed. Heck, I even searched for just memory or leak once each and came up with nothing. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - 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
Re: Tomcat 4.0.x memory leak (not javac)
Hi, I am also facing the same problem of memory leakage. I have posted on mail about this on 19th Nov too... I had contacted to the support people where our web application is hosted. I had got few suggestions. According to their suggestion - 1. I increased the heapsize in catalina.sh file. 2. I have also tried to increase the file descriptor size. Increaing the file descriptor size helped me at some extent. It stopped the frequent exceptions in Tomcat - catalina but occasionaly I am still gettng same exceptions. I would really like to have some more suggestions. Abhijeet Selukar - Original Message - From: Trenton D. Adams To: Tomcat Users List Sent: Monday, December 01, 2003 12:21 AM Subject: Re: Tomcat 4.0.x memory leak (not javac) Sven Köhler wrote: It's a known bug, but not fixed in 4.1.x, it still exists there. I am not sure if it still exists in 5.0.x. Thanks Dave. If anyone could provide some more information on this, that would be helpful. I would really like to fix it because it's really annoying me. We have two CRITICAL web applications on one server. We don't want to have to continually down the entire tomcat server just to reload a webapp. Bugs have been filed for this issue against 4.1.x and they have been marked as WONTFIX. Best to try to reproduce the problem on 5.0.x and if the bug still exists there, file a report in bugzilla if one does not already exist. Where can I find this information? Is there a bugzilla for tomcat or something? If so, I would like to go there so I can see if there's any information indicating where in the code it would be. I could go searching myself, but I've never dove into the Tomcat code before! :) Could you post the bugid or even a link to the bug-report? i'm also interested in the porblem. I would also be interested in a description of the javac-memory-leak. It has become a myth and nobody can explain it. I don't find a bug-report in both Sun's and Tomact's bug-databases. I found it once but I can't find it again. I was pretty sure I entered memory leak in the summary field and came up with results, but it doesn't work now. Anyhow, the javac bug is referenced in the release notes of 4.0.x. I don't think it's a javac bug but a tomcat bug with the interface into the javac classes. After all, it's not referenced in the release notes for the newer versions of tomcat. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat 4.0.x memory leak (not javac)
Howdy, First, prove to us it's the same bug. I say bug in quotes when referring to the original issue because I have no clue what's being discussed unless someone posts a bugzilla ID for it. Yoav Shapira Millennium ChemInformatics -Original Message- From: Abhijeet Selukar [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 11, 2003 2:49 AM To: Tomcat Users List Subject: Re: Tomcat 4.0.x memory leak (not javac) Hi, I am also facing the same problem of memory leakage. I have posted on mail about this on 19th Nov too... I had contacted to the support people where our web application is hosted. I had got few suggestions. According to their suggestion - 1. I increased the heapsize in catalina.sh file. 2. I have also tried to increase the file descriptor size. Increaing the file descriptor size helped me at some extent. It stopped the frequent exceptions in Tomcat - catalina but occasionaly I am still gettng same exceptions. I would really like to have some more suggestions. Abhijeet Selukar - Original Message - From: Trenton D. Adams To: Tomcat Users List Sent: Monday, December 01, 2003 12:21 AM Subject: Re: Tomcat 4.0.x memory leak (not javac) Sven Köhler wrote: It's a known bug, but not fixed in 4.1.x, it still exists there. I am not sure if it still exists in 5.0.x. Thanks Dave. If anyone could provide some more information on this, that would be helpful. I would really like to fix it because it's really annoying me. We have two CRITICAL web applications on one server. We don't want to have to continually down the entire tomcat server just to reload a webapp. Bugs have been filed for this issue against 4.1.x and they have been marked as WONTFIX. Best to try to reproduce the problem on 5.0.x and if the bug still exists there, file a report in bugzilla if one does not already exist. Where can I find this information? Is there a bugzilla for tomcat or something? If so, I would like to go there so I can see if there's any information indicating where in the code it would be. I could go searching myself, but I've never dove into the Tomcat code before! :) Could you post the bugid or even a link to the bug-report? i'm also interested in the porblem. I would also be interested in a description of the javac-memory-leak. It has become a myth and nobody can explain it. I don't find a bug- report in both Sun's and Tomact's bug-databases. I found it once but I can't find it again. I was pretty sure I entered memory leak in the summary field and came up with results, but it doesn't work now. Anyhow, the javac bug is referenced in the release notes of 4.0.x. I don't think it's a javac bug but a tomcat bug with the interface into the javac classes. After all, it's not referenced in the release notes for the newer versions of tomcat. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - 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: Tomcat 4.0.x memory leak (not javac)
Dave, We're having a problem with tomcat 4.0.4. Every time a context is reloaded it leaks memory. It's a known bug, but not fixed in 4.1.x, it still exists there. I am not sure if it still exists in 5.0.x. Can you provide a bug number or a link? I'd like to take a look at it. Thanks, -chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.0.x memory leak (not javac)
It's a known bug, but not fixed in 4.1.x, it still exists there. I am not sure if it still exists in 5.0.x. Thanks Dave. If anyone could provide some more information on this, that would be helpful. I would really like to fix it because it's really annoying me. We have two CRITICAL web applications on one server. We don't want to have to continually down the entire tomcat server just to reload a webapp. Bugs have been filed for this issue against 4.1.x and they have been marked as WONTFIX. Best to try to reproduce the problem on 5.0.x and if the bug still exists there, file a report in bugzilla if one does not already exist. Where can I find this information? Is there a bugzilla for tomcat or something? If so, I would like to go there so I can see if there's any information indicating where in the code it would be. I could go searching myself, but I've never dove into the Tomcat code before! :) Could you post the bugid or even a link to the bug-report? i'm also interested in the porblem. I would also be interested in a description of the javac-memory-leak. It has become a myth and nobody can explain it. I don't find a bug-report in both Sun's and Tomact's bug-databases. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.0.x memory leak (not javac)
Sven Köhler wrote: It's a known bug, but not fixed in 4.1.x, it still exists there. I am not sure if it still exists in 5.0.x. Thanks Dave. If anyone could provide some more information on this, that would be helpful. I would really like to fix it because it's really annoying me. We have two CRITICAL web applications on one server. We don't want to have to continually down the entire tomcat server just to reload a webapp. Bugs have been filed for this issue against 4.1.x and they have been marked as WONTFIX. Best to try to reproduce the problem on 5.0.x and if the bug still exists there, file a report in bugzilla if one does not already exist. Where can I find this information? Is there a bugzilla for tomcat or something? If so, I would like to go there so I can see if there's any information indicating where in the code it would be. I could go searching myself, but I've never dove into the Tomcat code before! :) Could you post the bugid or even a link to the bug-report? i'm also interested in the porblem. I would also be interested in a description of the javac-memory-leak. It has become a myth and nobody can explain it. I don't find a bug-report in both Sun's and Tomact's bug-databases. I found it once but I can't find it again. I was pretty sure I entered memory leak in the summary field and came up with results, but it doesn't work now. Anyhow, the javac bug is referenced in the release notes of 4.0.x. I don't think it's a javac bug but a tomcat bug with the interface into the javac classes. After all, it's not referenced in the release notes for the newer versions of tomcat. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.0.x memory leak (not javac)
Trenton D. Adams wrote: We're having a problem with tomcat 4.0.4. Every time a context is reloaded it leaks memory. The oddest thing about this is that it starts throwing OutOfMemoryExceptions before process list shows that it's using the memory I allocated to it. eg. It will through OutOfMemoryExceptions at like 130M memory usage when I've allocated 512M for it. Is this a known bug that's been fixed in 4.1.x? It's a known bug, but not fixed in 4.1.x, it still exists there. I am not sure if it still exists in 5.0.x. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.0.x memory leak (not javac)
David Rees wrote: Trenton D. Adams wrote: We're having a problem with tomcat 4.0.4. Every time a context is reloaded it leaks memory. The oddest thing about this is that it starts throwing OutOfMemoryExceptions before process list shows that it's using the memory I allocated to it. eg. It will throw OutOfMemoryExceptions at like 130M memory usage when I've allocated 512M for it. Is this a known bug that's been fixed in 4.1.x? It's a known bug, but not fixed in 4.1.x, it still exists there. I am not sure if it still exists in 5.0.x. -Dave Thanks Dave. If anyone could provide some more information on this, that would be helpful. I would really like to fix it because it's really annoying me. We have two CRITICAL web applications on one server. We don't want to have to continually down the entire tomcat server just to reload a webapp. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.0.x memory leak (not javac)
Trenton D. Adams wrote: David Rees wrote: Trenton D. Adams wrote: We're having a problem with tomcat 4.0.4. Every time a context is reloaded it leaks memory. The oddest thing about this is that it starts throwing OutOfMemoryExceptions before process list shows that it's using the memory I allocated to it. eg. It will throw OutOfMemoryExceptions at like 130M memory usage when I've allocated 512M for it. Is this a known bug that's been fixed in 4.1.x? It's a known bug, but not fixed in 4.1.x, it still exists there. I am not sure if it still exists in 5.0.x. Thanks Dave. If anyone could provide some more information on this, that would be helpful. I would really like to fix it because it's really annoying me. We have two CRITICAL web applications on one server. We don't want to have to continually down the entire tomcat server just to reload a webapp. Bugs have been filed for this issue against 4.1.x and they have been marked as WONTFIX. Best to try to reproduce the problem on 5.0.x and if the bug still exists there, file a report in bugzilla if one does not already exist. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.0.x memory leak (not javac)
David Rees wrote: Trenton D. Adams wrote: We're having a problem with tomcat 4.0.4. Every time a context is reloaded it leaks memory. The oddest thing about this is that it starts throwing OutOfMemoryExceptions before process list shows that it's using the memory I allocated to it. eg. It will through OutOfMemoryExceptions at like 130M memory usage when I've allocated 512M for it. Is this a known bug that's been fixed in 4.1.x? It's a known bug, but not fixed in 4.1.x, it still exists there. I am not sure if it still exists in 5.0.x. -Dave Oh, one other quick question. I was wondering about why it would start throwing out of memory exceptions before it reaches the 512M limit. Are there maybe parameters that can be passed to tomcat to tell it how much to use for web applications? And if so, are these set to a certain percentage of the -mx JVM parameter? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.0.x memory leak (not javac)
David Rees wrote: Trenton D. Adams wrote: David Rees wrote: Trenton D. Adams wrote: We're having a problem with tomcat 4.0.4. Every time a context is reloaded it leaks memory. The oddest thing about this is that it starts throwing OutOfMemoryExceptions before process list shows that it's using the memory I allocated to it. eg. It will throw OutOfMemoryExceptions at like 130M memory usage when I've allocated 512M for it. Is this a known bug that's been fixed in 4.1.x? It's a known bug, but not fixed in 4.1.x, it still exists there. I am not sure if it still exists in 5.0.x. Thanks Dave. If anyone could provide some more information on this, that would be helpful. I would really like to fix it because it's really annoying me. We have two CRITICAL web applications on one server. We don't want to have to continually down the entire tomcat server just to reload a webapp. Bugs have been filed for this issue against 4.1.x and they have been marked as WONTFIX. Best to try to reproduce the problem on 5.0.x and if the bug still exists there, file a report in bugzilla if one does not already exist. -Dave Where can I find this information? Is there a bugzilla for tomcat or something? If so, I would like to go there so I can see if there's any information indicating where in the code it would be. I could go searching myself, but I've never dove into the Tomcat code before! :) __ This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.0.x memory leak (not javac)
Trenton D. Adams wrote: Oh, one other quick question. I was wondering about why it would start throwing out of memory exceptions before it reaches the 512M limit. Are there maybe parameters that can be passed to tomcat to tell it how much to use for web applications? And if so, are these set to a certain percentage of the -mx JVM parameter? No, there's no special flags or memory partitioning going on. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat 4.0.x memory leak (not javac)
Trenton D. Adams wrote: Bugs have been filed for this issue against 4.1.x and they have been marked as WONTFIX. Best to try to reproduce the problem on 5.0.x and if the bug still exists there, file a report in bugzilla if one does not already exist. Where can I find this information? Is there a bugzilla for tomcat or something? If so, I would like to go there so I can see if there's any information indicating where in the code it would be. I could go searching myself, but I've never dove into the Tomcat code before! :) All the information you could ever hope to need is on the Tomcat website: http://jakarta.apache.org/tomcat/ -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
