The tags you describe below look almost exactly the same as those I
created myself just today, and it works OK.
Where is the 404 being generated? Are you using Apache and mod_jk? If
so, is the invalid path that you're providing one that would normally be
handled by Apache (i.e. Apache generates and handles the 404 entirely
without the knowledge of Tomcat)?
The only difference in my web.xml entries is that I defined the error-page
to be a .jsp, not a .html - I was using Tomcat as a stand-alone server. I
have a second server that's configured with Apache + mod_jserv. I don't
expect that this configuration will generate Tomcat 404s for URLs that
aren't destined for Tomcat.
On Tue, 5 Dec 2000, Catherine Jung wrote:
> I'm running Tomcat 3.2 Final (but also happens with b7) on Solaris
>
> If I use an <error-page> tag with a valid path for an erro rpage to
> display, Tomcat seems to repeatedly call that page until it gets a stack
> overflow. If I put an invalid path to an error page, this doesn't happen
> (I just get a 404 response with null returned), but obviously I still
> don't get an error page. If I try to get it to display the error page
> based on an <exception-type> rather than an <error-code> I get the same problem
