That "forwarding to itself" behavior has to be triggered under special circumstances because the application can work ok for long periods of time. But you're probably pointing me in the right direction because I have a base action class from which all other actions derive and in the base there is code to detect session timeouts (by comparing the requested session id with the current session id) and that code redirects to the home page action when a timeout is detected. That's probably when the looping is triggered somehow.
I'll modify that base class and see what happens. Thanks for the reply. -- DL I have a base action class from which all other action classes derive. 2011/2/17 Caldarale, Charles R <chuck.caldar...@unisys.com> > > From: Denis Laroche [mailto:dlaroc...@gmail.com] > > Subject: Re: requests die with a stack overflow > > > I have no such thing as filters in my configuration. > > No, but you have struts rules configured that are effectively the same > thing. Something in your struts config keeps forwarding to itself. > > - 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 > >
