Well, I am using the valve indeed! I will check if it is showing the size of the responses. I guess I can find the huge pages easily there. I'm not using the trimSpaces flag. If I find it, I wont need to limit the buffer. That would be more elegant than having to do it.
:-) But the other issue is that I still have to find the reason of the leak. I'm exploring YourKit for that. I guess I will find how to do it soon. > -----Original Message----- > From: Caldarale, Charles R [mailto:chuck.caldar...@unisys.com] > Sent: Tuesday, November 16, 2010 12:00 AM > To: Tomcat Users List > Subject: RE: Tomcat 6.0.29 using more and more RAM until it collapses? > > > From: Brian [mailto:bbprefix-m...@yahoo.com] > > Subject: RE: Tomcat 6.0.29 using more and more RAM until it collapses? > > > Isn't there a log of all the requests? > > Not by default, but you can enable the AccessLogValve in server.xml, that will > display the request URI and the response size. However, if you have > trimSpaces on for the JSP servlet, the size shown in the log will be the one > after white space is removed - and odds are that it's white space eating up > the > buffer. > > - 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
