One thing that happened on a system I was working on here, was that we saw OOMs and yet the GC stats showed we had plenty of free heap space, which didn't make sense. The problem turned out to be that there was a memory leak at the native level where the JVM couldn't see it and had no control (specifically, Apache Commons FileUpload version 1.0 used a native library function that had a leak; later versions of fileupload fixed this problem).
Pete "Caldarale, Charles R" <chuck.caldar...@unisys.com> wrote on 05/17/2010 09:10:28 AM: > > From: Ozgur Ozdemircili [mailto:ozgur.ozdemirc...@gmail.com] > > Subject: Re: MaxPermSize / Threads > > > > You can see the server giving error every 3-4 minutes until it dies. > > By "it dies", do you mean you have to restart Tomcat? > > Turn on GC logging (-verbose:gc) and use a heap profiler to see if > you have a memory leak or simply an undersized heap for the load > you're putting on it. If the heap usage returns to normal after a > heavy load, your heap is undersized; if the heap usage keeps > increasing over time regardless of the load, you have a leak in your webapps. > > - Chuck > > > THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE > PROPRIETARY MATERIAL and is thus for use only by the intended > recipient. If you received this in error, please contact the sender > and delete the e-mail and its attachments from all computers. > > > --------------------------------------------------------------------- > 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
