2011/2/17 Denis Laroche <dlaroc...@gmail.com>: > Hello all, > > I also posted this message to the Struts mailing list, because I'm not sure > where the problem is. The version of Tomcat is 6.0.29, and the JVM is > 1.6.0_17-b17 running on a Linux server, kernel version 2.6.18. The version > of Struts is 1.3.10. > > Once in a while, the application starts behaving erratically with huge stack > traces generated in the log file of the application. When the application > starts behaving this way, all requests fail and they all generate those huge > stack traces. The log file reaches 1 gigabyte in no time. > > I've attached one of those stack traces which I compressed with gzip. The > trace is 3756 lines long! >
A filter performs a forward which is then intercepted by the same filter, and so on in a loop. Either fix the condition that triggers the loop, or map the filter to process only incoming requests (see how it mapped in your web.xml, what <dispatcher> is specified in your <filter-mapping>). I think that you can use request.setAttribute() and then check if the attribute is present to detect looping. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
