are you seeing the same behavior in 4.1.10? or is it just 4.1.12?
I've performed some moderate load testing with 4.1.10 and in two cases where memory consumption went up, it was my own code that caused it. Once I profiled my webapp and looked at gc, it was obvious the culprit was my code. you can run tomcat with the following options to see in greater detail what is happening. JAVA_OPTS='-verbosegc' JAVA_OPTS='-Xloggc:/temp/log.log' peter lin Raj Saini wrote: > > I am experiencing the same problem with tomcat 4.0.3. I have my JVM memory > setting as -Xms=32 -Xmx=384 and running the tomcat on Sun Solaris 2.7, > integrated with Apache 1.3.x through warp connector. > > I have a JSP page monitoring the memory consumption at > http://www.emerging-trade.pt/servlets/memory.jsp, The memory consumption > pattern of the JSP shows the GC runs as you can see the increase/decerece in > the free memory of the current heap size. > > Raj Saini > > Raj Saini > > ----- Original Message ----- > From: "Tim Funk" <[EMAIL PROTECTED]> > To: "Tomcat Users List" <[EMAIL PROTECTED]> > Sent: Thursday, September 26, 2002 2:29 PM > Subject: Re: Tomcat 4.1.12 memory leak > > > Each request allocates memory. (And relinquishes accordingly) The > > garbage collector runs when "it feels like it should". The JVM will > > continually suck up memory until it reaches its startup parameters. (-mx > > ...) > > > > Once a JVM takes memory from the OS - it does not release it to the OS - > > it only releases it to its own memory heap. > > > > Ing. Damiano Bolla wrote: > > > System: Linux redhat 7.2 > > > Java: /usr/local/j2sdk1.3.1 > > > Tomcat 4.1.12 > > > > > > To reproduce the behaviour you install the 4.1.12 distribution, set the > > > JAVA_HOME run startup.sh and then keep refreshing the homepage > > > http://localhost:8080/ > > > > > > If you monitor the memory usage using top and switching it into display > > > memory usage (Capital M) you sull see tipically something like > > > > > > 22824 > > > 22832 > > > 22840 > > > 23576 > > > 23676 > > > 23684 > > > 23904 > > > 23908 > > > 23934 > > > 23938 > > > ..... > > > > > > This is the SIZE field of the top command. > > > The point is that it never goes down and eventually you run very slowly. > > > > > > Any idea ? > > > > > > Ah, the same behaviour is with jdk 1.4.1 > > > > > > Damiano > > > > > > > > > -- > > > To unsubscribe, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
