RE: memory leak in tomcat 5.0.16 ?
Thanks, I will upgrade to 5.0.18 and see if it works ! /Torstein -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: 22. januar 2004 11:44 To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? We had exactly the same problem. 2 users on 5.0.16 after 20 minutes the RAM consumed was 158MB and then it crashed. Upgraded to 5.0.18 yesterday and RAM is a steady 30MB. I dont care what anyone says, 5.0.16 had a problem! -Original Message- From: Francois JEANMOUGIN [mailto:[EMAIL PROTECTED] Sent: 22 January 2004 10:19 To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? > -Original Message- > From: Dale, Matt [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 22, 2004 11:05 AM > To: Tomcat Users List > Subject: RE: memory leak in tomcat 5.0.16 ? > > > There is a known memory leak in 5.0.16, I'd upgrade to 5.0.18 and see if > this fixes your problem. Note that the download page on Jakarta.apache.org is not updated with this new release. You need to figure the good URL by yourself (not so hard). François. -- --- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- - QAS Ltd. Developers of QuickAddress Software http://www.qas.com";>www.qas.com Registered in England: No 2582055 Registered in Australia: No 082 851 474 -- - -- --- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: memory leak in tomcat 5.0.16 ?
On Thu, January 22, 2004 1at 0:25 am, Torstein Nilsen wrote: > I have now upgraded to the latest tomcat release 5.0.18 but I'm > afraid this didn't solve the problem - the tomcat-process is still > growing. > > I have monitored the ressources used very closely with 5.0.18 and it > shows a slow grow in mem-usage a couple of hours and then suddenly in > a matter of ca. 10 secs. it goes from 15% to 40% of total memory and > stays there. Tomcat access log-files doesn't show extrordinary > activity during the "bloat". Sounds like you're going to need to get a profiler to figure out where the memory is being used. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: memory leak in tomcat 5.0.16 ?
I have now upgraded to the latest tomcat release 5.0.18 but I'm afraid this didn't solve the problem - the tomcat-process is still growing. I have monitored the ressources used very closely with 5.0.18 and it shows a slow grow in mem-usage a couple of hours and then suddenly in a matter of ca. 10 secs. it goes from 15% to 40% of total memory and stays there. Tomcat access log-files doesn't show extrordinary activity during the "bloat". Thanx anyway. I will try the max / min threads and see if this helps. Torstein -Original Message- From: Filip Hanik [mailto:[EMAIL PROTECTED] Sent: 22. januar 2004 18:58 To: Tomcat Users List Subject: Re: memory leak in tomcat 5.0.16 ? try setting maxSpareThreads==minSpareThreads==maxThreads in your connector, Filip - Original Message - From: "Ralph Einfeldt" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Thursday, January 22, 2004 7:18 AM Subject: RE: memory leak in tomcat 5.0.16 ? > The heap size has nothing to do with the memory size that > is seen by the system. > > You have to look at least at the total memory. > (That is used + free memory) > > To that you have to add > - thread stacks (At least some vm's don't allocate them on the heap) > - static memory (Like the jvm itself, static strings, classes, jars, ...) > - some os memory that is used by the vm to manage it self > - ... > > I wouldn't expect that the diff between total memory and system memory > is more than a few megs. (Far less than 30MB) > > > -Original Message- > > From: Allistair Crossley [mailto:[EMAIL PROTECTED] > > Sent: Thursday, January 22, 2004 4:06 PM > > To: Tomcat Users List > > Subject: RE: memory leak in tomcat 5.0.16 ? > > > > What puzzles me is the Windows task manager process memory as > > this never ever matches anywhere near the JProfiler reported > > memory. I know there may be some system overheads but the > > 30MB heap that JProfiler reveals is actually 90MB in Windows > > task manager. > > > > -- --- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- --- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: memory leak in tomcat 5.0.16 ?
try setting maxSpareThreads==minSpareThreads==maxThreads in your connector, Filip - Original Message - From: "Ralph Einfeldt" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Thursday, January 22, 2004 7:18 AM Subject: RE: memory leak in tomcat 5.0.16 ? > The heap size has nothing to do with the memory size that > is seen by the system. > > You have to look at least at the total memory. > (That is used + free memory) > > To that you have to add > - thread stacks (At least some vm's don't allocate them on the heap) > - static memory (Like the jvm itself, static strings, classes, jars, ...) > - some os memory that is used by the vm to manage it self > - ... > > I wouldn't expect that the diff between total memory and system memory > is more than a few megs. (Far less than 30MB) > > > -Original Message- > > From: Allistair Crossley [mailto:[EMAIL PROTECTED] > > Sent: Thursday, January 22, 2004 4:06 PM > > To: Tomcat Users List > > Subject: RE: memory leak in tomcat 5.0.16 ? > > > > What puzzles me is the Windows task manager process memory as > > this never ever matches anywhere near the JProfiler reported > > memory. I know there may be some system overheads but the > > 30MB heap that JProfiler reveals is actually 90MB in Windows > > task manager. > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: memory leak in tomcat 5.0.16 ?
The heap size has nothing to do with the memory size that is seen by the system. You have to look at least at the total memory. (That is used + free memory) To that you have to add - thread stacks (At least some vm's don't allocate them on the heap) - static memory (Like the jvm itself, static strings, classes, jars, ...) - some os memory that is used by the vm to manage it self - ... I wouldn't expect that the diff between total memory and system memory is more than a few megs. (Far less than 30MB) > -Original Message- > From: Allistair Crossley [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 22, 2004 4:06 PM > To: Tomcat Users List > Subject: RE: memory leak in tomcat 5.0.16 ? > > What puzzles me is the Windows task manager process memory as > this never ever matches anywhere near the JProfiler reported > memory. I know there may be some system overheads but the > 30MB heap that JProfiler reveals is actually 90MB in Windows > task manager. > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: memory leak in tomcat 5.0.16 ?
1.4.1_03 on W2K. I have no idea what the consumption of memory should be like but previous posts where I mentioned this about of RAM have had replies saying it was a lot. Depends on what you app does I guess. Ours has a real large XML nav tree in app scope that is used a lot on each request, we have a backend CMS to get search results for thousands of docs and all their meta data gets stored in properties files and we also do lots with the SQL server. At the moment all that is down to 30MB as shown in JProfiler's heap used view. What puzzles me is the Windows task manager process memory as this never ever matches anywhere near the JProfiler reported memory. I know there may be some system overheads but the 30MB heap that JProfiler reveals is actually 90MB in Windows task manager. Go figure? -Original Message- From: Derek Mahar [mailto:[EMAIL PROTECTED] Sent: 22 January 2004 14:58 To: Tomcat Users List Cc: [EMAIL PROTECTED] Subject: RE: memory leak in tomcat 5.0.16 ? Out of curiosity, which JVM do you run? I run Tomcat 5.0.18, JVM 1.4.2_03 for Linux on Red Hat, and two instances of JSPWiki serving no more than 200 users. This combination consumes a steady 121MB. Is this normal or excessive? Derek -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: January 22, 2004 5:44 AM To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? We had exactly the same problem. 2 users on 5.0.16 after 20 minutes the RAM consumed was 158MB and then it crashed. Upgraded to 5.0.18 yesterday and RAM is a steady 30MB. I dont care what anyone says, 5.0.16 had a problem! -Original Message- From: Francois JEANMOUGIN [mailto:[EMAIL PROTECTED] Sent: 22 January 2004 10:19 To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? > -Original Message- > From: Dale, Matt [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 22, 2004 11:05 AM > To: Tomcat Users List > Subject: RE: memory leak in tomcat 5.0.16 ? > > > There is a known memory leak in 5.0.16, I'd upgrade to 5.0.18 and see > if this fixes your problem. Note that the download page on Jakarta.apache.org is not updated with this new release. You need to figure the good URL by yourself (not so hard). François. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- QAS Ltd. Developers of QuickAddress Software http://www.qas.com";>www.qas.com Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: memory leak in tomcat 5.0.16 ?
Out of curiosity, which JVM do you run? I run Tomcat 5.0.18, JVM 1.4.2_03 for Linux on Red Hat, and two instances of JSPWiki serving no more than 200 users. This combination consumes a steady 121MB. Is this normal or excessive? Derek -Original Message- From: Allistair Crossley [mailto:[EMAIL PROTECTED] Sent: January 22, 2004 5:44 AM To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? We had exactly the same problem. 2 users on 5.0.16 after 20 minutes the RAM consumed was 158MB and then it crashed. Upgraded to 5.0.18 yesterday and RAM is a steady 30MB. I dont care what anyone says, 5.0.16 had a problem! -Original Message- From: Francois JEANMOUGIN [mailto:[EMAIL PROTECTED] Sent: 22 January 2004 10:19 To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? > -Original Message- > From: Dale, Matt [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 22, 2004 11:05 AM > To: Tomcat Users List > Subject: RE: memory leak in tomcat 5.0.16 ? > > > There is a known memory leak in 5.0.16, I'd upgrade to 5.0.18 and see > if this fixes your problem. Note that the download page on Jakarta.apache.org is not updated with this new release. You need to figure the good URL by yourself (not so hard). François. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- QAS Ltd. Developers of QuickAddress Software http://www.qas.com";>www.qas.com Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: memory leak in tomcat 5.0.16 ?
Francois JEANMOUGIN wrote: There is a known memory leak in 5.0.16, I'd upgrade to 5.0.18 and see if this fixes your problem. Note that the download page on Jakarta.apache.org is not updated with this new release. You need to figure the good URL by yourself (not so hard). Before announcing something, one has to wait for: - voting to complete - mirrors to replicate the build -- x Rémy Maucherat Senior Developer & Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: memory leak in tomcat 5.0.16 ?
We had exactly the same problem. 2 users on 5.0.16 after 20 minutes the RAM consumed was 158MB and then it crashed. Upgraded to 5.0.18 yesterday and RAM is a steady 30MB. I dont care what anyone says, 5.0.16 had a problem! -Original Message- From: Francois JEANMOUGIN [mailto:[EMAIL PROTECTED] Sent: 22 January 2004 10:19 To: Tomcat Users List Subject: RE: memory leak in tomcat 5.0.16 ? > -Original Message- > From: Dale, Matt [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 22, 2004 11:05 AM > To: Tomcat Users List > Subject: RE: memory leak in tomcat 5.0.16 ? > > > There is a known memory leak in 5.0.16, I'd upgrade to 5.0.18 and see if > this fixes your problem. Note that the download page on Jakarta.apache.org is not updated with this new release. You need to figure the good URL by yourself (not so hard). François. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --- QAS Ltd. Developers of QuickAddress Software http://www.qas.com";>www.qas.com Registered in England: No 2582055 Registered in Australia: No 082 851 474 --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: memory leak in tomcat 5.0.16 ?
> -Original Message- > From: Dale, Matt [mailto:[EMAIL PROTECTED] > Sent: Thursday, January 22, 2004 11:05 AM > To: Tomcat Users List > Subject: RE: memory leak in tomcat 5.0.16 ? > > > There is a known memory leak in 5.0.16, I'd upgrade to 5.0.18 and see if > this fixes your problem. Note that the download page on Jakarta.apache.org is not updated with this new release. You need to figure the good URL by yourself (not so hard). François. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: memory leak in tomcat 5.0.16 ?
Dale, Matt wrote: There is a known memory leak in 5.0.16, I'd upgrade to 5.0.18 and see if this fixes your problem. You should read his report. 1) I don't see how he would be affected, since he seems to have a rather small server; you need large variations in traffic to get the leak (and the workaround is easy enough anyway) 2) He's using AJP, not HTTP ;) I am developing an intranet for a housing community using apache/tomcat and mysql. It was put in production to 200 users a few weeks ago and I noticed that the java-proces (tomcat) was "growing" from 8% memory usage when started to over 50% (seen with top / ps aux). When the mem-usage reach a certain level the java-proces uses most of the CPU- ressources as well - verbose:GC showed that this is the GC trying to keep up. This usually happens in a matter of 2-5 hours depending on the Xmx-settings - the number of active users / load seems to speed the process up (not confirmed). Restarting tomcat solves the problem for a while - but I would prefer a better permament solution. System settings: CPU: Pentium 1600 mhz RAM: 512 MB OS: Linux (Redhat) Java: j2re1.4.2_03 / jikes TOMCAT: 5.0.16 Connector: org.apache.coyote.tomcat5.CoyoteConnector (AJP/1.3) CATALINA_OPTS: -Xmx200m -Xms200m -Dbuild.compiler.emacs=true (have tried 117 different settings) At first I used tomcat 4 and j2sdk1.4.1_03 and the "normal" javac-compiler. I changed to jakarta-tomcat-5.0.16 / j2re1.4.2_03 and jikes - this seems to have made the problem even worse. Before the update tomcat could go for more than 12 hours whitout restarting - now I have to restart every few hours. The application is quite DB-intensive: Every 30 secs. a java-thread queries a mysql-table with updated network-traffic data (used for traffic-shaping). In the same loop I SAX-parse a little XML-string using the JDOM-API (I have read about the StringBuffer-problem but this is not the cause since I'm now using j2re1.4.2_03 - right ?). I'm using mysql-connector-3.0.9 as JDBC-driver and protomatter-1.1.8 to pool DB-connections. In the same loop I connect to a TCP- socket on the local server. I have done some profiling with HPJmeter and the -Xrunhprof argument with different settings. I'm a newbie in profiling but these observations might be useful: -Using HPJmeter' "guess memory leaks" the top-4 suggested candidates are: java.util.vector, org.apache.commons.modeler.Registry, org.apache.jk.core.MsgContext and org.apache.coyote.Request -"Residual objects" shows the following top-4-classes (bytes): int[] (10 MB) char[] (4 MB) java.lang.String (2 MB) byte[] (2 MB) Any help would be much appreciated... Regards Torstein Nilsen -- x Rémy Maucherat Senior Developer & Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: memory leak in tomcat 5.0.16 ?
There is a known memory leak in 5.0.16, I'd upgrade to 5.0.18 and see if this fixes your problem. Ta Matt -Original Message- From: Torstein Nilsen [mailto:[EMAIL PROTECTED] Sent: 22 January 2004 10:01 To: [EMAIL PROTECTED] Subject: memory leak in tomcat 5.0.16 ? I am developing an intranet for a housing community using apache/tomcat and mysql. It was put in production to 200 users a few weeks ago and I noticed that the java-proces (tomcat) was "growing" from 8% memory usage when started to over 50% (seen with top / ps aux). When the mem-usage reach a certain level the java-proces uses most of the CPU- ressources as well - verbose:GC showed that this is the GC trying to keep up. This usually happens in a matter of 2-5 hours depending on the Xmx-settings - the number of active users / load seems to speed the process up (not confirmed). Restarting tomcat solves the problem for a while - but I would prefer a better permament solution. System settings: CPU: Pentium 1600 mhz RAM: 512 MB OS: Linux (Redhat) Java: j2re1.4.2_03 / jikes TOMCAT: 5.0.16 Connector: org.apache.coyote.tomcat5.CoyoteConnector (AJP/1.3) CATALINA_OPTS: -Xmx200m -Xms200m -Dbuild.compiler.emacs=true (have tried 117 different settings) At first I used tomcat 4 and j2sdk1.4.1_03 and the "normal" javac-compiler. I changed to jakarta-tomcat-5.0.16 / j2re1.4.2_03 and jikes - this seems to have made the problem even worse. Before the update tomcat could go for more than 12 hours whitout restarting - now I have to restart every few hours. The application is quite DB-intensive: Every 30 secs. a java-thread queries a mysql-table with updated network-traffic data (used for traffic-shaping). In the same loop I SAX-parse a little XML-string using the JDOM-API (I have read about the StringBuffer-problem but this is not the cause since I'm now using j2re1.4.2_03 - right ?). I'm using mysql-connector-3.0.9 as JDBC-driver and protomatter-1.1.8 to pool DB-connections. In the same loop I connect to a TCP- socket on the local server. I have done some profiling with HPJmeter and the -Xrunhprof argument with different settings. I'm a newbie in profiling but these observations might be useful: -Using HPJmeter' "guess memory leaks" the top-4 suggested candidates are: java.util.vector, org.apache.commons.modeler.Registry, org.apache.jk.core.MsgContext and org.apache.coyote.Request -"Residual objects" shows the following top-4-classes (bytes): int[] (10 MB) char[] (4 MB) java.lang.String (2 MB) byte[] (2 MB) Any help would be much appreciated... Regards Torstein Nilsen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
