RE: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
Thanks a lot for your responses, I posted this query multiple times to get more and more responses. Please don’t consider this as spam, And after applying the answers(increase of memory) I got this issue resolved to some extent. Thanking you all again. Shailendra -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: Wednesday, September 05, 2012 11:49 PM To: Tomcat Users List Subject: Re: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim, On 9/5/12 1:17 PM, Tim Watts wrote: On Wed, 2012-09-05 at 12:16 -0400, PJ Delsh wrote: Shailendra, I'm not an expert, but when we had this same issue, we increased the Initial Memory Pool and Maximum Memory pool (XMS and XMX) in the Tomcat Monitor in Windows 2008.We also had a leak in some of our JSP files that was causing Tomcat to hang several times during business hours. We configured Tomcat so that VisualVM (which comes with the Java JDK) could monitor Tomcat memory usage. Then we took heap dumps, and analyzed them for leaks (Shallow Heap vs Retained Heap) using Eclipse Memory Analyzer. Once we fixed the leaks, Tomcat was stable.In the interim, if you have Tomcat running as a service in Windows, under the Recovery tab set the Tomcat service to restart automatically if it does stop. But if you have memory leaks, the Tomcat service probably will still be running but it won't be responding.You can also install more than one Tomcat on the same server, so if one goes down, the other will still be running. You would also have to configure Apache (or whatever) to work with more than one Tomcat.We also had issues with the Tomcat service crashing (eg Terminated Unsuccessfully) on Windows. After months of searching, we think the issue was having system.exit(0) in our code. System.exit(0) is the very definition of successful termination although it certainly doesn't belong in your webapp's code. +1 The truth is that Tomcat is not written well enough to run on Windows. What rot. All the problems you mention above you traced back to your application. Yet your conclusion is that Tomcat doesn't run well on Windows. Really? Tomcat runs very well on Microsoft Windows. Poorly-written applications will fail under any environment. In the OP's case, I really believe the only problem is that the heap is too small when moving from a 32-bit to a 64-bit JVM, but we can't seem to get s response from the OP so I guess we'll never know. See what you can do to move your app to Linux. You will find many more Tomcat experts on Linux than on Windows. I myself have a strong preference for Linux but for reasons unrelated to Tomcat. In reality, you'll find that most Tomcat experts don't give a rat's hiney which OS it runs under. But they may care which JVM you're using. I'm another Linux supporter and I'd hate to run Microsoft Windows as a server in general, but if you're stuck with it, Tomcat isn't going to be the problem. Tomcat is not like IIS. True. Developing for Tomcat on Windows is fine, but running production apps in Tomcat on Windows is a bad idea. I wish this was more widely known and publicized.-PJ Total BS. Agreed. PJ: care to cite any widely known and publicized references? Also, PJ, what makes you think that your experiences are anything like the OP's? You seem to be spouting solutions to problems that you do not understand. When the reported problem is we are getting OOMEs, the solution is not automatically you should switch to Linux because Tomcat sucks on Windows. It's inaccurate advice (Tomcat works find on Windows) and is very unlikely to solve the problem (whatever it is). - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBHl4MACgkQ9CaO5/Lv0PAYmACdGQidM7rMSsG/+rZaA2P/zliB ibAAoIWe4z0Ifvy9h8WrYJdbZHvdc4Fp =9H6c -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
What's the maximum heap size allocated to the JVM in both cases? you can try increasing the same where you are getting OME. you can set the heap size like this: -Xms 512m -Xmx 1024m Chinmoy On Wed, Sep 5, 2012 at 12:20 PM, Shailendra Singh shailendra.si...@pb.comwrote: Hi, We are using 64 bit Tomcat 6.0.35 with windows 2008 R2 (64 bit JVM 1.6.0_33) and facing memory leak issues(OutOfMemoryError ) after a short interval of time( ~30 minutes). We deploy a web application on this version of tomcat and while working with the GUI part of the application we face memory leak, but same application works fine on this windows server for 32 bit JVM. Please help us if this is an issue with 64 bit Tomcat version or with 64bit JVM or with its combination. kindly let us know a solution or any work around or for this. Thanks and Regards, Shailendra Singh
Re: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Shailendra, On 9/5/12 2:50 AM, Shailendra Singh wrote: We are using 64 bit Tomcat 6.0.35 with windows 2008 R2 (64 bit JVM 1.6.0_33) and facing memory leak issues(OutOfMemoryError ) after a short interval of time( ~30 minutes). We deploy a web application on this version of tomcat and while working with the GUI part of the application we face memory leak, but same application works fine on this windows server for 32 bit JVM. Please help us if this is an issue with 64 bit Tomcat version or with 64bit JVM or with its combination. kindly let us know a solution or any work around or for this. You've asked this question three times now and have apparently been ignoring every reply you get. Please stop asking if you are going to ignore our questions and advice. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBHbAUACgkQ9CaO5/Lv0PCknACeIwxou02m0hz1Y9HtZTAmzMot A/YAniXDFbzzs+ApHFFXBxL9vtIoXuoN =NjrU -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
Shailendra, I'm not an expert, but when we had this same issue, we increased the Initial Memory Pool and Maximum Memory pool (XMS and XMX) in the Tomcat Monitor in Windows 2008.We also had a leak in some of our JSP files that was causing Tomcat to hang several times during business hours. We configured Tomcat so that VisualVM (which comes with the Java JDK) could monitor Tomcat memory usage. Then we took heap dumps, and analyzed them for leaks (Shallow Heap vs Retained Heap) using Eclipse Memory Analyzer. Once we fixed the leaks, Tomcat was stable.In the interim, if you have Tomcat running as a service in Windows, under the Recovery tab set the Tomcat service to restart automatically if it does stop. But if you have memory leaks, the Tomcat service probably will still be running but it won't be responding.You can also install more than one Tomcat on the same server, so if one goes down, the other will still be running. You would also have to configure Apache (or whatever) to work with more than one Tomcat.We also had issues with the Tomcat service crashing (eg Terminated Unsuccessfully) on Windows. After months of searching, we think the issue was having system.exit(0) in our code.The truth is that Tomcat is not written well enough to run on Windows. See what you can do to move your app to Linux. You will find many more Tomcat experts on Linux than on Windows. Tomcat is not like IIS. Developing for Tomcat on Windows is fine, but running production apps in Tomcat on Windows is a bad idea. I wish this was more widely known and publicized.-PJ Date: Wed, 5 Sep 2012 11:13:09 -0400 From: ch...@christopherschultz.net To: users@tomcat.apache.org Subject: Re: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Shailendra, On 9/5/12 2:50 AM, Shailendra Singh wrote: We are using 64 bit Tomcat 6.0.35 with windows 2008 R2 (64 bit JVM 1.6.0_33) and facing memory leak issues(OutOfMemoryError ) after a short interval of time( ~30 minutes). We deploy a web application on this version of tomcat and while working with the GUI part of the application we face memory leak, but same application works fine on this windows server for 32 bit JVM. Please help us if this is an issue with 64 bit Tomcat version or with 64bit JVM or with its combination. kindly let us know a solution or any work around or for this. You've asked this question three times now and have apparently been ignoring every reply you get. Please stop asking if you are going to ignore our questions and advice. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBHbAUACgkQ9CaO5/Lv0PCknACeIwxou02m0hz1Y9HtZTAmzMot A/YAniXDFbzzs+ApHFFXBxL9vtIoXuoN =NjrU -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
On Wed, 2012-09-05 at 12:16 -0400, PJ Delsh wrote: Shailendra, I'm not an expert, but when we had this same issue, we increased the Initial Memory Pool and Maximum Memory pool (XMS and XMX) in the Tomcat Monitor in Windows 2008.We also had a leak in some of our JSP files that was causing Tomcat to hang several times during business hours. We configured Tomcat so that VisualVM (which comes with the Java JDK) could monitor Tomcat memory usage. Then we took heap dumps, and analyzed them for leaks (Shallow Heap vs Retained Heap) using Eclipse Memory Analyzer. Once we fixed the leaks, Tomcat was stable.In the interim, if you have Tomcat running as a service in Windows, under the Recovery tab set the Tomcat service to restart automatically if it does stop. But if you have memory leaks, the Tomcat service probably will still be running but it won't be responding.You can also install more than one Tomcat on the same server, so if one goes down, the other will still be running. You would also have to configure Apache (or whatever) to work with more than one Tomcat.We also had issues with the Tomcat service crashing (eg Terminated Unsuccessfully) on Windows. After months of searching, we think the issue was having system.exit(0) in our code. System.exit(0) is the very definition of successful termination although it certainly doesn't belong in your webapp's code. The truth is that Tomcat is not written well enough to run on Windows. What rot. All the problems you mention above you traced back to your application. Yet your conclusion is that Tomcat doesn't run well on Windows. Really? See what you can do to move your app to Linux. You will find many more Tomcat experts on Linux than on Windows. I myself have a strong preference for Linux but for reasons unrelated to Tomcat. In reality, you'll find that most Tomcat experts don't give a rat's hiney which OS it runs under. But they may care which JVM you're using. Tomcat is not like IIS. True. Developing for Tomcat on Windows is fine, but running production apps in Tomcat on Windows is a bad idea. I wish this was more widely known and publicized.-PJ Total BS. Date: Wed, 5 Sep 2012 11:13:09 -0400 From: ch...@christopherschultz.net To: users@tomcat.apache.org Subject: Re: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Shailendra, On 9/5/12 2:50 AM, Shailendra Singh wrote: We are using 64 bit Tomcat 6.0.35 with windows 2008 R2 (64 bit JVM 1.6.0_33) and facing memory leak issues(OutOfMemoryError ) after a short interval of time( ~30 minutes). We deploy a web application on this version of tomcat and while working with the GUI part of the application we face memory leak, but same application works fine on this windows server for 32 bit JVM. Please help us if this is an issue with 64 bit Tomcat version or with 64bit JVM or with its combination. kindly let us know a solution or any work around or for this. You've asked this question three times now and have apparently been ignoring every reply you get. Please stop asking if you are going to ignore our questions and advice. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBHbAUACgkQ9CaO5/Lv0PCknACeIwxou02m0hz1Y9HtZTAmzMot A/YAniXDFbzzs+ApHFFXBxL9vtIoXuoN =NjrU -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org signature.asc Description: This is a digitally signed message part
Re: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim, On 9/5/12 1:17 PM, Tim Watts wrote: On Wed, 2012-09-05 at 12:16 -0400, PJ Delsh wrote: Shailendra, I'm not an expert, but when we had this same issue, we increased the Initial Memory Pool and Maximum Memory pool (XMS and XMX) in the Tomcat Monitor in Windows 2008.We also had a leak in some of our JSP files that was causing Tomcat to hang several times during business hours. We configured Tomcat so that VisualVM (which comes with the Java JDK) could monitor Tomcat memory usage. Then we took heap dumps, and analyzed them for leaks (Shallow Heap vs Retained Heap) using Eclipse Memory Analyzer. Once we fixed the leaks, Tomcat was stable.In the interim, if you have Tomcat running as a service in Windows, under the Recovery tab set the Tomcat service to restart automatically if it does stop. But if you have memory leaks, the Tomcat service probably will still be running but it won't be responding.You can also install more than one Tomcat on the same server, so if one goes down, the other will still be running. You would also have to configure Apache (or whatever) to work with more than one Tomcat.We also had issues with the Tomcat service crashing (eg Terminated Unsuccessfully) on Windows. After months of searching, we think the issue was having system.exit(0) in our code. System.exit(0) is the very definition of successful termination although it certainly doesn't belong in your webapp's code. +1 The truth is that Tomcat is not written well enough to run on Windows. What rot. All the problems you mention above you traced back to your application. Yet your conclusion is that Tomcat doesn't run well on Windows. Really? Tomcat runs very well on Microsoft Windows. Poorly-written applications will fail under any environment. In the OP's case, I really believe the only problem is that the heap is too small when moving from a 32-bit to a 64-bit JVM, but we can't seem to get s response from the OP so I guess we'll never know. See what you can do to move your app to Linux. You will find many more Tomcat experts on Linux than on Windows. I myself have a strong preference for Linux but for reasons unrelated to Tomcat. In reality, you'll find that most Tomcat experts don't give a rat's hiney which OS it runs under. But they may care which JVM you're using. I'm another Linux supporter and I'd hate to run Microsoft Windows as a server in general, but if you're stuck with it, Tomcat isn't going to be the problem. Tomcat is not like IIS. True. Developing for Tomcat on Windows is fine, but running production apps in Tomcat on Windows is a bad idea. I wish this was more widely known and publicized.-PJ Total BS. Agreed. PJ: care to cite any widely known and publicized references? Also, PJ, what makes you think that your experiences are anything like the OP's? You seem to be spouting solutions to problems that you do not understand. When the reported problem is we are getting OOMEs, the solution is not automatically you should switch to Linux because Tomcat sucks on Windows. It's inaccurate advice (Tomcat works find on Windows) and is very unlikely to solve the problem (whatever it is). - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBHl4MACgkQ9CaO5/Lv0PAYmACdGQidM7rMSsG/+rZaA2P/zliB ibAAoIWe4z0Ifvy9h8WrYJdbZHvdc4Fp =9H6c -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
Chris and Tim, When we had Tomcat issues, every Tomcat professional we spoke to told us to drop Windows and move to Linux ASAP. We were told that Tomcat is more stable and less sensitive on Linux, and there are far better troubleshooting tools on Linux than there are for Windows. If this is inaccurate, then Tomcat consulting companies are spreading misinformation. -PJ
Re: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
edited for my amusement. On 5 Sep 2012, at 17:16, PJ Delsh pjdelsh...@hotmail.com wrote: Shailendra, I'm not an expert, Really? Once we fixed the leaks, Tomcat was stable. Quel surprise. After months of searching, we think the issue was having system.exit(0) in our code. A classic blunder. After which you conclude: The truth is that Tomcat is not written well enough to run on Windows. Hilarious, but unfounded inaccurate. Of course you could prove me wrong by pointing out which bits of Tomcat are not written well enough to run on Windows? Tomcat is not like IIS. Developing for Tomcat on Windows is fine, but running production apps in Tomcat on Windows is a bad idea. I am aware of substantial Tomcat deployments on Windows that run just fine under a decent amount of load. p Date: Wed, 5 Sep 2012 11:13:09 -0400 From: ch...@christopherschultz.net To: users@tomcat.apache.org Subject: Re: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Shailendra, On 9/5/12 2:50 AM, Shailendra Singh wrote: We are using 64 bit Tomcat 6.0.35 with windows 2008 R2 (64 bit JVM 1.6.0_33) and facing memory leak issues(OutOfMemoryError ) after a short interval of time( ~30 minutes). We deploy a web application on this version of tomcat and while working with the GUI part of the application we face memory leak, but same application works fine on this windows server for 32 bit JVM. Please help us if this is an issue with 64 bit Tomcat version or with 64bit JVM or with its combination. kindly let us know a solution or any work around or for this. You've asked this question three times now and have apparently been ignoring every reply you get. Please stop asking if you are going to ignore our questions and advice. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBHbAUACgkQ9CaO5/Lv0PCknACeIwxou02m0hz1Y9HtZTAmzMot A/YAniXDFbzzs+ApHFFXBxL9vtIoXuoN =NjrU -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
On 9/5/2012 3:29 PM, PJ Delsh wrote: Chris and Tim, When we had Tomcat issues, every Tomcat professional we spoke to told us to drop Windows and move to Linux ASAP. We were told that Tomcat is more stable and less sensitive on Linux, and there are far better troubleshooting tools on Linux than there are for Windows. If this is inaccurate, then Tomcat consulting companies are spreading misinformation. -PJ They're not spreading misinfomation, they're just pushing people to where they want them to go for their own purposes. We have been running TC apps on windows for about 15 years (since TC 4.x), with some of them taking more than 4 million transactions per day (up to 100 per second during peak times), and go months between restarts. And even then, those restarts are just for windows security updates. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
-Original Message- From: PJ Delsh [mailto:pjdelsh...@hotmail.com] Sent: Wednesday, September 05, 2012 2:29 PM To: Tomcat Users List Subject: RE: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33) Chris and Tim, When we had Tomcat issues, every Tomcat professional we spoke to told us to drop Windows and move to Linux ASAP. We were told that Tomcat is more stable and less sensitive on Linux, and there are far better troubleshooting tools on Linux than there are for Windows. If this is inaccurate, then Tomcat consulting companies are spreading misinformation. -PJ I would say, as always in IT, it depends. We have used Windows for years with hundreds of servers, hosting hundreds of JVMs - more than one on the same machine typically, and hundreds of distinct war files. We also use Linux. There are tools for both O/S platforms for troubleshooting/debugging. If any consulting company were to tell me what they told you, I would want specific cases explained to me - not just wide open generalizations. In my opinion, more Tomcat is better. If it needs to run on Windows due to current company knowledge/momentum, so be it. Would it be a good idea to set up some test servers using Linux too in order to do a shootout with your apps - sure! Some of this depends on how your app works and how it is used too. If you really want to know, set up both types of servers and use any one of the numerous load testing tools out there and see for yourself. - ust another Tomcat user - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
Pid * wrote: edited for my amusement. On 5 Sep 2012, at 17:16, PJ Delsh pjdelsh...@hotmail.com wrote: Shailendra, I'm not an expert, Really? Once we fixed the leaks, Tomcat was stable. Quel surprise. After months of searching, we think the issue was having system.exit(0) in our code. A classic blunder. After which you conclude: The truth is that Tomcat is not written well enough to run on Windows. Hilarious, but unfounded inaccurate. Of course you could prove me wrong by pointing out which bits of Tomcat are not written well enough to run on Windows? Tomcat is not like IIS. Developing for Tomcat on Windows is fine, but running production apps in Tomcat on Windows is a bad idea. I am aware of substantial Tomcat deployments on Windows that run just fine under a decent amount of load. And, for further amusement, another note : Tomcat doesn't run under Windows (nor under Linux). Tomcat is a Java app, and Java apps run under a Java Virtual Machine, which is supposed to provide to the Java apps that run under it, the exact same environment, no matter which platform the Java VM itself runs under. That is what makes Java applications multi-platform, after all. (Which, if you get down to it, is in fact a lie. Java apps always run under the same platform : the JVM). In other words, the Tomcat code is always one and the same. It is the JVM that is different for each platform, not Tomcat. So one could argue about the respective qualities of the undelying OSes, or the respective qualities of the OS-specific JVM's. But it is totally meaningless to write that Tomcat is not written well enough to run on Windows. As long as one says that, one might just as well save oneself some typing and just write Tomcat is not written well enough. Which is guaranteed to start another lively discussion on this list. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 PJ, On 9/5/12 3:29 PM, PJ Delsh wrote: When we had Tomcat issues, every Tomcat professional we spoke to told us to drop Windows and move to Linux ASAP. I wouldn't argue that moving away from Microsoft Windows isn't a good idea in general, but your consultants were probably not proficient with Windows and wanted you to move for /their/ sake, not yours. We were told that Tomcat is more stable and less sensitive on Linux, and there are far better troubleshooting tools on Linux than there are for Windows. The tools assertion is probably true, but doesn't actually extend to the JVM itself: the same tools are available on Linux as well as other operating systems. If Tomcat is any less stable on Microsoft Windows, it's because of Windows itself and not Tomcat. There was a time (1998?) when Sun's Linux JVM was super buggy and Microsoft Windows was the only reasonably stable OS when it came to Java deployments. Lots of things have changed, but the Sun/Oracle JVM is very stable on every environment I've used it (Linux 2.4/2.6, Win2k/XP/Vista/7, and Mac OS X). If this is inaccurate, then Tomcat consulting companies are spreading misinformation. The Apache Software Foundation doesn't control any Tomcat consulting companies, and they can spread whatever misinformation they seem appropriate. It's up to you to decide if their advice is good. If your problems went away by switching from Microsoft Windows to Linux*, then I'm glad you had success. I suspect that there was more going on and that a simple switch from Microsoft Windows to Linux wasn't a magic fix-it pill. * A tall order for most companies who have a lot of money invested in their deployment strategy, IT staff, network operations, production support, etc. It doesn't matter which way you switch: Linux - Windows would be a huge inconvenience to an ops department as well. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlBHw9YACgkQ9CaO5/Lv0PDQVwCeIcf1OZlQJDt31cK5X34wvvBn qaMAn1MmDcL1ixD14oOUMFgO5Mv4QYuA =Xd1G -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
On 9/5/2012 2:29 PM, PJ Delsh wrote: Chris and Tim, When we had Tomcat issues, every Tomcat professional we spoke to told us to drop Windows and move to Linux ASAP. We were told that Tomcat is more stable and less sensitive on Linux, and there are far better troubleshooting tools on Linux than there are for Windows. If this is inaccurate, then Tomcat consulting companies are spreading misinformation. -PJ Perhaps you should: a) stop believing everything you're told. b) stop passing on information about which you are unsure as if it were fact. -Terence Bandoian - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
On 04.09.2012 08:35, Shailendra Singh wrote: Hi, We are using 64 bit Tomcat 6.0.35 with windows 2008 R2 (64 bit JVM 1.6.0_33) and facing memory leak issues(OutOfMemoryError ) after a short interval of time( ~30 minutes). We deploy a web application on this version of tomcat and while working with the GUI part of the application we face memory leak, but same application works fine on this windows server for 32 bit JVM. Please help us if this is an issue with 64 bit Tomcat version or with 64bit JVM or with its combination. kindly let us know a solution or any work around or for this. 64 Bit JVM needs more memory than 32 Bits. The pointers are double the size. Rule of thumb says 30% additional memory, but it can vary a lot depending on the application. Try larger JVM memory settings. It is unlikely that you experience a memory leak with 64 Bit JVM but not 32 Bits running the same application. Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Shailendra, On 8/30/12 1:54 AM, Shailendra Singh wrote: We are using 64 bit Tomcat 6.0.35 with windows 2008 R2 (64 bit JVM 1.6.0_33) and facing memory leak issues(OutOfMemoryError ) after a short interval of time( ~30 minutes). We deploy a web application on this version of tomcat and while working with the GUI part of the application we face memory leak, but same application works fine on this windows server for 32 bit JVM. So you run out of memory when using 64-bit JVM but not on 32-bit JVM? Please help us if this is an issue with 64 bit Tomcat version or with 64bit JVM or with its combination. kindly let us know a solution or any work around or for this. Tomcat is almost entirely architecture-agnostic (except for the service runner and optional APR/native library which hardly consume any memory at all, and are unlikely to be the problem, here). What kind of OOME are you getting? Heap? PermGen? My knee-jerk reaction is that you simply need a bigger heap than usual when moving from 32-bit to 64-bit JVM because the word-length has doubled. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlA/dRIACgkQ9CaO5/Lv0PAyOACeIiurUcHkcLkrwtil5GlPTGlA xhoAn3uQ9FLU4/pBADHCD3j6Ul7B8HhS =fthI -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
On 30/08/2012 15:13, Christopher Schultz wrote: Shailendra, On 8/30/12 1:54 AM, Shailendra Singh wrote: We are using 64 bit Tomcat 6.0.35 with windows 2008 R2 (64 bit JVM 1.6.0_33) and facing memory leak issues(OutOfMemoryError ) after a short interval of time( ~30 minutes). We deploy a web application on this version of tomcat and while working with the GUI part of the application we face memory leak, but same application works fine on this windows server for 32 bit JVM. So you run out of memory when using 64-bit JVM but not on 32-bit JVM? Please help us if this is an issue with 64 bit Tomcat version or with 64bit JVM or with its combination. kindly let us know a solution or any work around or for this. Tomcat is almost entirely architecture-agnostic (except for the service runner and optional APR/native library which hardly consume any memory at all, and are unlikely to be the problem, here). What kind of OOME are you getting? Heap? PermGen? My knee-jerk reaction is that you simply need a bigger heap than usual when moving from 32-bit to 64-bit JVM because the word-length has doubled. Given that there is no real information about the environment (e.g. memory assigned, used, etc) that's a fair guess. p -chris - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- [key:62590808] signature.asc Description: OpenPGP digital signature
Re: Facing Memory leak - 64 bit Tomcat 6.0.35 with windows 2008 R2(64 bit JVM 1.6.0_33)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pid, On 8/30/12 5:02 PM, Pid wrote: On 30/08/2012 15:13, Christopher Schultz wrote: Shailendra, On 8/30/12 1:54 AM, Shailendra Singh wrote: We are using 64 bit Tomcat 6.0.35 with windows 2008 R2 (64 bit JVM 1.6.0_33) and facing memory leak issues(OutOfMemoryError ) after a short interval of time( ~30 minutes). We deploy a web application on this version of tomcat and while working with the GUI part of the application we face memory leak, but same application works fine on this windows server for 32 bit JVM. So you run out of memory when using 64-bit JVM but not on 32-bit JVM? Please help us if this is an issue with 64 bit Tomcat version or with 64bit JVM or with its combination. kindly let us know a solution or any work around or for this. Tomcat is almost entirely architecture-agnostic (except for the service runner and optional APR/native library which hardly consume any memory at all, and are unlikely to be the problem, here). What kind of OOME are you getting? Heap? PermGen? My knee-jerk reaction is that you simply need a bigger heap than usual when moving from 32-bit to 64-bit JVM because the word-length has doubled. Given that there is no real information about the environment (e.g. memory assigned, used, etc) that's a fair guess. I stole your crystal ball to come up with that. Bet you didn't see that coming, eh? - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlA/1v0ACgkQ9CaO5/Lv0PDYEQCZAfSmlwJ5VDmerKXsEcKUwEMd FdEAn3FMJttjgIaRtEd2KhHIkDfeIqji =tIkd -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
