Re: Why is tomcat (java) so memory intensive?
Dakota Jack wrote: Why, then, does the Tomcat 5.0 say in the RELEASE-NOTES "JAVAC leaking memory" is an issue? On Tue, 21 Dec 2004 16:06:13 -, Allistair Crossley <[EMAIL PROTECTED]> wrote: i think (from memory) it had to do with registering requests with jk. anyway, like i say, upgrade and you'll see that leak go away i am pretty sure. -Original Message- From: Allistair Crossley Sent: 21 December 2004 16:00 To: Tomcat Users List; [EMAIL PROTECTED] Subject: RE: Why is tomcat (java) so memory intensive? you are right, tomcat 5.0.19 did have a memory leak. some dispute it, but it is there, i had it also and used a profiler to show it. you should upgrade to 5.0.28. Thanks, Jack That's during compilation. I always setup tomcat to fork when compiling jsp. That means it runs a seperate process to compile pages. I do this in both production and testing. I just like the feeling it gives me :-P ... well it's just better to not worry about it for me. The bug is supposed to be gone in 1.4.2, but I still fork. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Why is tomcat (java) so memory intensive?
I think that's only with JDK 1.3 though -Original Message- From: Dakota Jack [mailto:[EMAIL PROTECTED] Sent: 21 December 2004 16:40 To: Tomcat Users List Subject: Re: Why is tomcat (java) so memory intensive? Why, then, does the Tomcat 5.0 say in the RELEASE-NOTES "JAVAC leaking memory" is an issue? On Tue, 21 Dec 2004 16:06:13 -, Allistair Crossley <[EMAIL PROTECTED]> wrote: > i think (from memory) it had to do with registering requests with jk. anyway, > like i say, upgrade and you'll see that leak go away i am pretty sure. > > > -Original Message- > > From: Allistair Crossley > > Sent: 21 December 2004 16:00 > > To: Tomcat Users List; [EMAIL PROTECTED] > > Subject: RE: Why is tomcat (java) so memory intensive? > > > > > > you are right, tomcat 5.0.19 did have a memory leak. some > > dispute it, but it is there, i had it also and used a > > profiler to show it. you should upgrade to 5.0.28. > > Thanks, Jack -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ "You can't wake a person who is pretending to be asleep." ~Native Proverb~ "Each man is good in His sight. It is not necessary for eagles to be crows." ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ --- "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Why is tomcat (java) so memory intensive?
our production server has been on 5.5.4 for a few weeks and performing very nicely. 5.5.4 is the latest stable build for 5.5 series. give it a shot on your development server if you have one. > -Original Message- > From: Dakota Jack [mailto:[EMAIL PROTECTED] > Sent: 21 December 2004 16:45 > To: Tomcat Users List > Subject: Re: Why is tomcat (java) so memory intensive? > > > Is there any reason not to upgrade to 5.5? Is that ready for prime > time? Thanks. > > Jack > > > On Tue, 21 Dec 2004 16:06:13 -, Allistair Crossley > <[EMAIL PROTECTED]> wrote: > > i think (from memory) it had to do with registering > requests with jk. anyway, like i say, upgrade and you'll see > that leak go away i am pretty sure. > > > > > -Original Message- > > > From: Allistair Crossley > > > Sent: 21 December 2004 16:00 > > > To: Tomcat Users List; [EMAIL PROTECTED] > > > Subject: RE: Why is tomcat (java) so memory intensive? > > > > > > > > > you are right, tomcat 5.0.19 did have a memory leak. some > > > dispute it, but it is there, i had it also and used a > > > profiler to show it. you should upgrade to 5.0.28. > > > > > > Allistair. > > > > > > > -Original Message----- > > > > From: Philippe Deslauriers [mailto:[EMAIL PROTECTED] > > > > Sent: 21 December 2004 15:47 > > > > To: Tomcat Users List; [EMAIL PROTECTED] > > > > Subject: RE: Why is tomcat (java) so memory intensive? > > > > > > > > > > > > > > > > Actually no, I tough it was 256Mb. Thanks. > > > > It will go out of memory around 125Mb 140Mb in the task > > > > manager. It depends. > > > > > > > > But your point just prove my problem to be even stanger: if > > > > 64 Mb shoulb be > > > > the limit > > > > where did the other 60Mb+ go? (the JVM itself never takes > > > > that much memory, > > > > not from my experience). > > > > > > > > What I did not mention in the orgininal post is that I have > > > > the same problem > > > > with an app running on 5.0.18 sam jdk, using -Xms256m > > > > -Xmx1024m, it will > > > > also run OOM, and again profiling the app did not show any > > > > leak, and a large > > > > gap between the total heap and whatever the task manger reports. > > > > > > > > My main issue here is where does the gap come from? > > > > > > > > > > > > -Original Message- > > > > From: Christoph Kutzinski [mailto:[EMAIL PROTECTED] > > > > Sent: Tuesday, December 21, 2004 10:22 AM > > > > To: Tomcat Users List > > > > Subject: Re: Why is tomcat (java) so memory intensive? > > > > > > > > > > > > Philippe Deslauriers wrote: > > > > > I am using Tomcat 5.0.19 on Windows XP SP2, J2SDK 1.4.2_03. > > > > > > > > > > I have a serious memory problem with Tomcat, it just EAT > > > > memory without > > > > > explanation, until OOM error occurs. > > > > > > > > > > The Java.exe process in the windows task manager reports > > > > using between > > > > 95Mb > > > > > and 105Mb after the startup of the webapp. I do not use Xms > > > > Xmx options in > > > > > dev mode. > > > > > > > > You do know that the VM will only allocate 64 mb for heap > > > if you don't > > > > use the Xmx option, do you? > > > > After the 64 mb are used up the vm will throw an oom error. > > > > How much memory does the taskmanager report before the oom > > > > error happens? > > > > > > > > > > > > Christoph > > > > > > > > > > > > - > > > > 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: Why is tomcat (java) so memory intensive?
Sounds like you are running out of space in the permanent generation. Add -XX:MaxPermSize=128M to your JAVA_OPTS -Original Message- From: Philippe Deslauriers [mailto:[EMAIL PROTECTED] Sent: 21 December 2004 15:47 To: Tomcat Users List; [EMAIL PROTECTED] Subject: RE: Why is tomcat (java) so memory intensive? Actually no, I tough it was 256Mb. Thanks. It will go out of memory around 125Mb 140Mb in the task manager. It depends. But your point just prove my problem to be even stanger: if 64 Mb shoulb be the limit where did the other 60Mb+ go? (the JVM itself never takes that much memory, not from my experience). What I did not mention in the orgininal post is that I have the same problem with an app running on 5.0.18 sam jdk, using -Xms256m -Xmx1024m, it will also run OOM, and again profiling the app did not show any leak, and a large gap between the total heap and whatever the task manger reports. My main issue here is where does the gap come from? -Original Message- From: Christoph Kutzinski [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:22 AM To: Tomcat Users List Subject: Re: Why is tomcat (java) so memory intensive? Philippe Deslauriers wrote: > I am using Tomcat 5.0.19 on Windows XP SP2, J2SDK 1.4.2_03. > > I have a serious memory problem with Tomcat, it just EAT memory without > explanation, until OOM error occurs. > > The Java.exe process in the windows task manager reports using between 95Mb > and 105Mb after the startup of the webapp. I do not use Xms Xmx options in > dev mode. You do know that the VM will only allocate 64 mb for heap if you don't use the Xmx option, do you? After the 64 mb are used up the vm will throw an oom error. How much memory does the taskmanager report before the oom error happens? Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why is tomcat (java) so memory intensive?
Is there any reason not to upgrade to 5.5? Is that ready for prime time? Thanks. Jack On Tue, 21 Dec 2004 16:06:13 -, Allistair Crossley <[EMAIL PROTECTED]> wrote: > i think (from memory) it had to do with registering requests with jk. anyway, > like i say, upgrade and you'll see that leak go away i am pretty sure. > > > -Original Message- > > From: Allistair Crossley > > Sent: 21 December 2004 16:00 > > To: Tomcat Users List; [EMAIL PROTECTED] > > Subject: RE: Why is tomcat (java) so memory intensive? > > > > > > you are right, tomcat 5.0.19 did have a memory leak. some > > dispute it, but it is there, i had it also and used a > > profiler to show it. you should upgrade to 5.0.28. > > > > Allistair. > > > > > -Original Message- > > > From: Philippe Deslauriers [mailto:[EMAIL PROTECTED] > > > Sent: 21 December 2004 15:47 > > > To: Tomcat Users List; [EMAIL PROTECTED] > > > Subject: RE: Why is tomcat (java) so memory intensive? > > > > > > > > > > > > Actually no, I tough it was 256Mb. Thanks. > > > It will go out of memory around 125Mb 140Mb in the task > > > manager. It depends. > > > > > > But your point just prove my problem to be even stanger: if > > > 64 Mb shoulb be > > > the limit > > > where did the other 60Mb+ go? (the JVM itself never takes > > > that much memory, > > > not from my experience). > > > > > > What I did not mention in the orgininal post is that I have > > > the same problem > > > with an app running on 5.0.18 sam jdk, using -Xms256m > > > -Xmx1024m, it will > > > also run OOM, and again profiling the app did not show any > > > leak, and a large > > > gap between the total heap and whatever the task manger reports. > > > > > > My main issue here is where does the gap come from? > > > > > > > > > -Original Message- > > > From: Christoph Kutzinski [mailto:[EMAIL PROTECTED] > > > Sent: Tuesday, December 21, 2004 10:22 AM > > > To: Tomcat Users List > > > Subject: Re: Why is tomcat (java) so memory intensive? > > > > > > > > > Philippe Deslauriers wrote: > > > > I am using Tomcat 5.0.19 on Windows XP SP2, J2SDK 1.4.2_03. > > > > > > > > I have a serious memory problem with Tomcat, it just EAT > > > memory without > > > > explanation, until OOM error occurs. > > > > > > > > The Java.exe process in the windows task manager reports > > > using between > > > 95Mb > > > > and 105Mb after the startup of the webapp. I do not use Xms > > > Xmx options in > > > > dev mode. > > > > > > You do know that the VM will only allocate 64 mb for heap > > if you don't > > > use the Xmx option, do you? > > > After the 64 mb are used up the vm will throw an oom error. > > > How much memory does the taskmanager report before the oom > > > error happens? > > > > > > > > > Christoph > > > > > > > > - > > > 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] > > > > > > > > > > > > > > --- > > 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] > > -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ "You can't wake a person who is pretending to be asleep." ~Native Proverb~ "Each man is good in His sight. It is not necessary for eagles to be crows." ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ --- "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why is tomcat (java) so memory intensive?
Sorry, misread what you said. Jack On Tue, 21 Dec 2004 08:40:01 -0800, Dakota Jack <[EMAIL PROTECTED]> wrote: > Why, then, does the Tomcat 5.0 say in the RELEASE-NOTES "JAVAC leaking > memory" is an issue? > > > On Tue, 21 Dec 2004 16:06:13 -, Allistair Crossley > <[EMAIL PROTECTED]> wrote: > > i think (from memory) it had to do with registering requests with jk. > > anyway, like i say, upgrade and you'll see that leak go away i am pretty > > sure. > > > > > -Original Message- > > > From: Allistair Crossley > > > Sent: 21 December 2004 16:00 > > > To: Tomcat Users List; [EMAIL PROTECTED] > > > Subject: RE: Why is tomcat (java) so memory intensive? > > > > > > > > > you are right, tomcat 5.0.19 did have a memory leak. some > > > dispute it, but it is there, i had it also and used a > > > profiler to show it. you should upgrade to 5.0.28. > > > > > > Thanks, > > Jack > > -- > "You can lead a horse to water but you cannot make it float on its back." > > ~Dakota Jack~ > > "You can't wake a person who is pretending to be asleep." > > ~Native Proverb~ > > "Each man is good in His sight. It is not necessary for eagles to be crows." > > ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ > > --- > > "This message may contain confidential and/or privileged information. > If you are not the addressee or authorized to receive this for the > addressee, you must not use, copy, disclose, or take any action based > on this message or any information herein. If you have received this > message in error, please advise the sender immediately by reply e-mail > and delete this message. Thank you for your cooperation." > -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ "You can't wake a person who is pretending to be asleep." ~Native Proverb~ "Each man is good in His sight. It is not necessary for eagles to be crows." ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ --- "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why is tomcat (java) so memory intensive?
Why, then, does the Tomcat 5.0 say in the RELEASE-NOTES "JAVAC leaking memory" is an issue? On Tue, 21 Dec 2004 16:06:13 -, Allistair Crossley <[EMAIL PROTECTED]> wrote: > i think (from memory) it had to do with registering requests with jk. anyway, > like i say, upgrade and you'll see that leak go away i am pretty sure. > > > -Original Message- > > From: Allistair Crossley > > Sent: 21 December 2004 16:00 > > To: Tomcat Users List; [EMAIL PROTECTED] > > Subject: RE: Why is tomcat (java) so memory intensive? > > > > > > you are right, tomcat 5.0.19 did have a memory leak. some > > dispute it, but it is there, i had it also and used a > > profiler to show it. you should upgrade to 5.0.28. > > Thanks, Jack -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ "You can't wake a person who is pretending to be asleep." ~Native Proverb~ "Each man is good in His sight. It is not necessary for eagles to be crows." ~Hunkesni (Sitting Bull), Hunkpapa Sioux~ --- "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Why is tomcat (java) so memory intensive?
i think (from memory) it had to do with registering requests with jk. anyway, like i say, upgrade and you'll see that leak go away i am pretty sure. > -Original Message- > From: Allistair Crossley > Sent: 21 December 2004 16:00 > To: Tomcat Users List; [EMAIL PROTECTED] > Subject: RE: Why is tomcat (java) so memory intensive? > > > you are right, tomcat 5.0.19 did have a memory leak. some > dispute it, but it is there, i had it also and used a > profiler to show it. you should upgrade to 5.0.28. > > Allistair. > > > -Original Message- > > From: Philippe Deslauriers [mailto:[EMAIL PROTECTED] > > Sent: 21 December 2004 15:47 > > To: Tomcat Users List; [EMAIL PROTECTED] > > Subject: RE: Why is tomcat (java) so memory intensive? > > > > > > > > Actually no, I tough it was 256Mb. Thanks. > > It will go out of memory around 125Mb 140Mb in the task > > manager. It depends. > > > > But your point just prove my problem to be even stanger: if > > 64 Mb shoulb be > > the limit > > where did the other 60Mb+ go? (the JVM itself never takes > > that much memory, > > not from my experience). > > > > What I did not mention in the orgininal post is that I have > > the same problem > > with an app running on 5.0.18 sam jdk, using -Xms256m > > -Xmx1024m, it will > > also run OOM, and again profiling the app did not show any > > leak, and a large > > gap between the total heap and whatever the task manger reports. > > > > My main issue here is where does the gap come from? > > > > > > -Original Message- > > From: Christoph Kutzinski [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, December 21, 2004 10:22 AM > > To: Tomcat Users List > > Subject: Re: Why is tomcat (java) so memory intensive? > > > > > > Philippe Deslauriers wrote: > > > I am using Tomcat 5.0.19 on Windows XP SP2, J2SDK 1.4.2_03. > > > > > > I have a serious memory problem with Tomcat, it just EAT > > memory without > > > explanation, until OOM error occurs. > > > > > > The Java.exe process in the windows task manager reports > > using between > > 95Mb > > > and 105Mb after the startup of the webapp. I do not use Xms > > Xmx options in > > > dev mode. > > > > You do know that the VM will only allocate 64 mb for heap > if you don't > > use the Xmx option, do you? > > After the 64 mb are used up the vm will throw an oom error. > > How much memory does the taskmanager report before the oom > > error happens? > > > > > > Christoph > > > > > - > > 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] > > > > > > > > --- > 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: Why is tomcat (java) so memory intensive?
you are right, tomcat 5.0.19 did have a memory leak. some dispute it, but it is there, i had it also and used a profiler to show it. you should upgrade to 5.0.28. Allistair. > -Original Message- > From: Philippe Deslauriers [mailto:[EMAIL PROTECTED] > Sent: 21 December 2004 15:47 > To: Tomcat Users List; [EMAIL PROTECTED] > Subject: RE: Why is tomcat (java) so memory intensive? > > > > Actually no, I tough it was 256Mb. Thanks. > It will go out of memory around 125Mb 140Mb in the task > manager. It depends. > > But your point just prove my problem to be even stanger: if > 64 Mb shoulb be > the limit > where did the other 60Mb+ go? (the JVM itself never takes > that much memory, > not from my experience). > > What I did not mention in the orgininal post is that I have > the same problem > with an app running on 5.0.18 sam jdk, using -Xms256m > -Xmx1024m, it will > also run OOM, and again profiling the app did not show any > leak, and a large > gap between the total heap and whatever the task manger reports. > > My main issue here is where does the gap come from? > > > -Original Message- > From: Christoph Kutzinski [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 21, 2004 10:22 AM > To: Tomcat Users List > Subject: Re: Why is tomcat (java) so memory intensive? > > > Philippe Deslauriers wrote: > > I am using Tomcat 5.0.19 on Windows XP SP2, J2SDK 1.4.2_03. > > > > I have a serious memory problem with Tomcat, it just EAT > memory without > > explanation, until OOM error occurs. > > > > The Java.exe process in the windows task manager reports > using between > 95Mb > > and 105Mb after the startup of the webapp. I do not use Xms > Xmx options in > > dev mode. > > You do know that the VM will only allocate 64 mb for heap if you don't > use the Xmx option, do you? > After the 64 mb are used up the vm will throw an oom error. > How much memory does the taskmanager report before the oom > error happens? > > > Christoph > > - > 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] > > --- 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: Why is tomcat (java) so memory intensive?
Actually no, I tough it was 256Mb. Thanks. It will go out of memory around 125Mb 140Mb in the task manager. It depends. But your point just prove my problem to be even stanger: if 64 Mb shoulb be the limit where did the other 60Mb+ go? (the JVM itself never takes that much memory, not from my experience). What I did not mention in the orgininal post is that I have the same problem with an app running on 5.0.18 sam jdk, using -Xms256m -Xmx1024m, it will also run OOM, and again profiling the app did not show any leak, and a large gap between the total heap and whatever the task manger reports. My main issue here is where does the gap come from? -Original Message- From: Christoph Kutzinski [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 10:22 AM To: Tomcat Users List Subject: Re: Why is tomcat (java) so memory intensive? Philippe Deslauriers wrote: > I am using Tomcat 5.0.19 on Windows XP SP2, J2SDK 1.4.2_03. > > I have a serious memory problem with Tomcat, it just EAT memory without > explanation, until OOM error occurs. > > The Java.exe process in the windows task manager reports using between 95Mb > and 105Mb after the startup of the webapp. I do not use Xms Xmx options in > dev mode. You do know that the VM will only allocate 64 mb for heap if you don't use the Xmx option, do you? After the 64 mb are used up the vm will throw an oom error. How much memory does the taskmanager report before the oom error happens? Christoph - 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: Why is tomcat (java) so memory intensive?
if you are using the windows service, the default is Xms 128 Xmx 256. > -Original Message- > From: Christoph Kutzinski [mailto:[EMAIL PROTECTED] > Sent: 21 December 2004 15:22 > To: Tomcat Users List > Subject: Re: Why is tomcat (java) so memory intensive? > > > Philippe Deslauriers wrote: > > I am using Tomcat 5.0.19 on Windows XP SP2, J2SDK 1.4.2_03. > > > > I have a serious memory problem with Tomcat, it just EAT > memory without > > explanation, until OOM error occurs. > > > > The Java.exe process in the windows task manager reports > using between 95Mb > > and 105Mb after the startup of the webapp. I do not use Xms > Xmx options in > > dev mode. > > You do know that the VM will only allocate 64 mb for heap if > you don't > use the Xmx option, do you? > After the 64 mb are used up the vm will throw an oom error. > How much memory does the taskmanager report before the oom > error happens? > > > Christoph > > - > 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: Why is tomcat (java) so memory intensive?
and get jvmstat from sun, it will allow you to see which area in the heap runs out of space. Ta Matt -Original Message- From: Filip Hanik (lists) [mailto:[EMAIL PROTECTED] Sent: 21 December 2004 15:12 To: Tomcat Users List Subject: RE: Why is tomcat (java) so memory intensive? you will need to dig deeper into jprobe or whatever profiler you are using. after that you will see where the memory goes. also, try the latest version of tomcat 5.0 Filip -Original Message- From: Philippe Deslauriers [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 8:53 AM To: [EMAIL PROTECTED] Subject: Why is tomcat (java) so memory intensive? I am using Tomcat 5.0.19 on Windows XP SP2, J2SDK 1.4.2_03. I have a serious memory problem with Tomcat, it just EAT memory without explanation, until OOM error occurs. The Java.exe process in the windows task manager reports using between 95Mb and 105Mb after the startup of the webapp. I do not use Xms Xmx options in dev mode. It just grows until it runs out of memory. There is not much memory available (around 150Mb), yet it should be enough for a few classes, JSP and almost not data in the database. Like a big boy, I decided to use Jprofiler demo to figure out where the memory leak was, to see that there is only 20 Mb allocated by the VM!!! So where does the rest of the memory goes? I do not use any non-java library (dll), I don't think I'm doing anything special. The app use a the Versant JDO implementation (instead of direct JDBC) using MS SQL server. But hey, the app is still in dev mode, with only the developpers using it, the DB is (almost) empty, so the amount data is not in cause. Anyways using 20Mb of heap is very reasonable (there will be at least 1gb available in production), but why is the java.exe process eating memory like a pig an the profiler is not showing where the mem goes? (by the way, I did deleted ALL the filters from Jprofiler). If the app would take 2Gb in memory I would not care, as long as I know what is using the memory. I did profile an app running on 5.0.18, and the same magic happens, the memory used by the java.exe is far from close to what the total heap size of the VM reports to be. Am I going crazy? Any ideas? Thanks Filip:) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why is tomcat (java) so memory intensive?
Philippe Deslauriers wrote: I am using Tomcat 5.0.19 on Windows XP SP2, J2SDK 1.4.2_03. I have a serious memory problem with Tomcat, it just EAT memory without explanation, until OOM error occurs. The Java.exe process in the windows task manager reports using between 95Mb and 105Mb after the startup of the webapp. I do not use Xms Xmx options in dev mode. You do know that the VM will only allocate 64 mb for heap if you don't use the Xmx option, do you? After the 64 mb are used up the vm will throw an oom error. How much memory does the taskmanager report before the oom error happens? Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why is tomcat (java) so memory intensive?
I would also be interested in some memory/performance tuning possibilities. Ok, if you do not run it standalone but with Apache the web response times should be faster, my profiling gives me the following: CPU SAMPLES BEGIN (total = 8628) Tue Dec 21 16:10:18 2004 rank self accum count trace method 1 33.68% 33.68%2906 300647 java.net.SocketInputStream.socketRead0 2 20.70% 54.38%1786 300557 java.net.PlainSocketImpl.socketAccept 3 20.17% 74.55%1740 300542 java.net.PlainSocketImpl.socketAccept 4 20.12% 94.67%1736 300551 java.net.PlainSocketImpl.socketAccept 5 1.36% 96.02% 117 300669 java.net.SocketInputStream.socketRead0 I think everybody can reproduce profiling with e.g. set JAVA_OPTS=-server -Xms500M -Xmx1000M -Xrunhprof:cpu=samples,interval=20,dept=5 in startup.bat /sh I run tapestry and castor with my web-apps and would assume that they eat most cpu, not the http transfer. You see I give enough memory to avoid Out of memory Exceptions ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Why is tomcat (java) so memory intensive?
you will need to dig deeper into jprobe or whatever profiler you are using. after that you will see where the memory goes. also, try the latest version of tomcat 5.0 Filip -Original Message- From: Philippe Deslauriers [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 21, 2004 8:53 AM To: [EMAIL PROTECTED] Subject: Why is tomcat (java) so memory intensive? I am using Tomcat 5.0.19 on Windows XP SP2, J2SDK 1.4.2_03. I have a serious memory problem with Tomcat, it just EAT memory without explanation, until OOM error occurs. The Java.exe process in the windows task manager reports using between 95Mb and 105Mb after the startup of the webapp. I do not use Xms Xmx options in dev mode. It just grows until it runs out of memory. There is not much memory available (around 150Mb), yet it should be enough for a few classes, JSP and almost not data in the database. Like a big boy, I decided to use Jprofiler demo to figure out where the memory leak was, to see that there is only 20 Mb allocated by the VM!!! So where does the rest of the memory goes? I do not use any non-java library (dll), I don't think I'm doing anything special. The app use a the Versant JDO implementation (instead of direct JDBC) using MS SQL server. But hey, the app is still in dev mode, with only the developpers using it, the DB is (almost) empty, so the amount data is not in cause. Anyways using 20Mb of heap is very reasonable (there will be at least 1gb available in production), but why is the java.exe process eating memory like a pig an the profiler is not showing where the mem goes? (by the way, I did deleted ALL the filters from Jprofiler). If the app would take 2Gb in memory I would not care, as long as I know what is using the memory. I did profile an app running on 5.0.18, and the same magic happens, the memory used by the java.exe is far from close to what the total heap size of the VM reports to be. Am I going crazy? Any ideas? Thanks Filip:) - 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]
