On Thu, Jan 26, 2012 at 5:19 PM, Jonathan Rosenberg <[email protected]> wrote: > Ok, maybe that's not a great subject. > > I'm testing my cas-server to ensure that friendly error pages are > shown on server errors. > > My first test was DB failure: > 1) I started the DB server. > 2) Started cas server. > 3) Logged in (cas/login) to be sure it's working > 4) Logged out. > 5) Stopped DB server. > 6) Tried to log in again. > > I ended up seeing the standard Tomcat error page: > > HTTP Status 500 - > type Exception report > message > description The server encountered an internal error () that > prevented it from fulfilling this request. > . . . > > Ultimate exception, as expected, was java.net.ConnectException: > Connection refused >
> I don't understand why cas didn't catch this and redirect to its error > page. Can you share your web.xml? > I see a call to SafeDispatcherServlet in the stack. It seems > like this should have handled the problem. That only catches errors that arise from deployment errors, typically caused by Spring wiring problems. It's entirely possible for a runtime exception to happen outside of the Spring dispatcher servlet and be handled by the container, which is apparently doing its default behavior of showing a Tomcat 500 page. M -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
