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
