All geek questions in one place

Grails (500) and Tomcat Custom Error Page

I am trying to implement a simple custom error page after any unhandled exception is thrown by Grails code. I matched 500 with my controller:

"500" ( controller: "error", action: "serverError" )

and handled the exception in the controller:

 def serverError = { try { // first check, if some exception was reported if (!request.exception) { return } // send mail with stack trace if requested if (shouldSendErrorReports) { log.debug "Mail was sent out successfully..." } } catch (Throwable e) { log.error "Error while reporting an error: " + e } // redirect to error message redirect ( action: "errorMessage" ) } // lines omitted for clarity

The errorMessage action is just a view, which by default makes a GSP page with static content - information and a click-to-redirect window. The page has (hopefully) the correct prolog:

 <%@ page contentType="text/html;charset=UTF-8" %> <%@ page isErrorPage="true" %>

Now, testing it locally through NetBeans (Jetty), everything works fine and the errorMessage page is displayed; when deployed in a TEST environment (Tomcat6), the Tomcat stack trace is displayed.

How to prevent Tomcat stack trace from showing? I have two thoughts - firstly, I'm not dumping (processing?) Correctly, an exception, so it bubbles up on Tomcat - secondly, Tomcat has a specific configuration value, so it still displays the stack trace.

Please, if you have any thoughts on this, let me know. Spend about 5 hours figuring this out ...: - /

Thanks!

+4
source share
2 answers

def error = {def exception = request ['javax.servlet.error.exception'] ?. cause? .cause if (exception) {

  } }
0
source

More than a year has passed since you asked this question, but so that others can also win ...

Have you tried the error-pages-fix plugin? http://www.grails.org/plugin/error-pages-fix

0
source

Source: https://habr.com/ru/post/1312081/

More articles:


All Articles