I see the error page just fine. But if I call some arbitrary page that doesn't exist, I get the default HTTP 404 Page Not Found that most HTTP Servers tend to throw. Not even the Tomcat specific 404. [ July 30, 2004: Message edited by: Gregg Bolinger ]

I just did a test here at home with a fresh test project that only has an index page and an error page and everything works fine. So I guess I am going to have to see what is different when I get back to work.

This is so strange though because I did everything exactly the same...

I had the same problem yesterday with my web.xml definition <error-page> <error-code>404</error-code> <location>/common/jsp/errorPage.jsp?ID=404</location> </error-page> I always received the default 404-page of the browser.

Solution: there is a minimum limit of the errorpage size. Add some more text to your errorpage and it'll work (hope so)

Originally posted by Bruno Marti: I had the same problem yesterday with my web.xml definition <error-page> <error-code>404</error-code> <location>/common/jsp/errorPage.jsp?ID=404</location> </error-page> I always received the default 404-page of the browser.

Solution: there is a minimum limit of the errorpage size. Add some more text to your errorpage and it'll work (hope so)

So here is something else interesting that is happening. Now, not matter what page I visit in my web app, my FileNotFound class is being ran. The app functions as normal, except I have a System.out.print in the FileNotFound servlet and it is printing my out statement about 3 times per page. Is this normal?

Well, after some better debugging...I have some images that I have not fixed the url on to display and appearntly for ANY resource that the server can't find you get a 404. So it was calling my error page for those images not being available. I didn't realize it did this.