What you observe is what I would expect to see on pretty much any container, on any JVM, if you are measuring memory allocated to the JVM process.
The reason this happens is that the JVM expands its heap dynamically as necessary, but most JVMs are *not* programmed to return memory to the OS. Instead, the memory will be available in Java's heap, for the creation of new Java objects as needed. What you really want to check for, when looking for memory leaks, is repeated accesses to the same URLs. If memory goes up continuously, you probably have a leak. If not, you're probably OK. Doing just one or two requests tells you basically nothing useful. Craig On Tue, 10 Sep 2002, Billy Ng wrote: > Date: Tue, 10 Sep 2002 18:53:08 -0700 > From: Billy Ng <[EMAIL PROTECTED]> > Reply-To: Struts Users Mailing List <[EMAIL PROTECTED]> > To: Struts Users Mailing List <[EMAIL PROTECTED]> > Subject: Possible memory leak in Tomcat 4.1.10 > > Hi folks, > > I am trying to find what is causing the memory leak in my app. I > changed to use the Tomcat 4.1.10. By only hitting the Tomcat's servlet > and jsp exampes, the free memory is already going down and never back > up. I heard the Tomcat 4.0.4 has memory leak problem, but I do not hear > anything about the 4.1.10. I am wondering if anyone experienced the > same problem before. If you are using any version of Tomcat that you > feel it is stable, please let me know. > > Thanks! > > Billy Ng > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
