Customizing Zuul Exception

后端 未结 7 1117
说谎
说谎 2020-11-29 05:23

I have a scenario in Zuul where the service that the URL is routed too might be down . So the reponse body gets thrown with 500 HTTP Status and ZuulException in the JSON bod

相关标签:
7条回答
  • 2020-11-29 05:46

    We finally got this working [Coded by one of my colleague]:-

    public class CustomErrorFilter extends ZuulFilter {
    
        private static final Logger LOG = LoggerFactory.getLogger(CustomErrorFilter.class);
        @Override
        public String filterType() {
            return "post";
        }
    
        @Override
        public int filterOrder() {
            return -1; // Needs to run before SendErrorFilter which has filterOrder == 0
        }
    
        @Override
        public boolean shouldFilter() {
            // only forward to errorPath if it hasn't been forwarded to already
            return RequestContext.getCurrentContext().containsKey("error.status_code");
        }
    
        @Override
        public Object run() {
            try {
                RequestContext ctx = RequestContext.getCurrentContext();
                Object e = ctx.get("error.exception");
    
                if (e != null && e instanceof ZuulException) {
                    ZuulException zuulException = (ZuulException)e;
                    LOG.error("Zuul failure detected: " + zuulException.getMessage(), zuulException);
    
                    // Remove error code to prevent further error handling in follow up filters
                    ctx.remove("error.status_code");
    
                    // Populate context with new response values
                    ctx.setResponseBody(“Overriding Zuul Exception Body”);
                    ctx.getResponse().setContentType("application/json");
                    ctx.setResponseStatusCode(500); //Can set any error code as excepted
                }
            }
            catch (Exception ex) {
                LOG.error("Exception filtering in custom error filter", ex);
                ReflectionUtils.rethrowRuntimeException(ex);
            }
            return null;
        }
    }
    
    0 讨论(0)
  • 2020-11-29 05:50
        The simplest solution is to follow first 4 steps.
    
    
         1. Create your own CustomErrorController extends
            AbstractErrorController which will not allow the
            BasicErrorController to be called.
         2. Customize according to your need refer below method from
            BasicErrorController.
    
        <pre><code> 
            @RequestMapping
            public ResponseEntity<Map<String, Object>> error(HttpServletRequest request) {
                Map<String, Object> body = getErrorAttributes(request,
                        isIncludeStackTrace(request, MediaType.ALL));
                HttpStatus status = getStatus(request);
                return new ResponseEntity<>(body, status);
            }
        </pre></code> 
    
         4. You can control whether you want exception / stack trace to be printed or not can do as mentioned below:
        <pre><code>
        server.error.includeException=false
        server.error.includeStacktrace=ON_TRACE_PARAM
        </pre></code>
     ====================================================
    
        5. If you want all together different error response re-throw your custom exception from your CustomErrorController and implement the Advice class as mentioned below:
    
        <pre><code>
    
    @Controller
    @Slf4j
    public class CustomErrorController extends BasicErrorController {
    
        public CustomErrorController(ErrorAttributes errorAttributes, ServerProperties serverProperties,
                List<ErrorViewResolver> errorViewResolvers) {
    
            super(errorAttributes, serverProperties.getError(), errorViewResolvers);
            log.info("Created");
        }
    
        @Override
        public ResponseEntity<Map<String, Object>> error(HttpServletRequest request) {
            Map<String, Object> body = getErrorAttributes(request, isIncludeStackTrace(request, MediaType.ALL));
            HttpStatus status = getStatus(request);
            throw new CustomErrorException(String.valueOf(status.value()), status.getReasonPhrase(), body);
        }
    }
    
    
        @ControllerAdvice
        public class GenericExceptionHandler {
        // Exception handler annotation invokes a method when a specific exception
            // occurs. Here we have invoked Exception.class since we
            // don't have a specific exception scenario.
            @ExceptionHandler(CustomException.class)
            @ResponseBody
            public ErrorListWsDTO customExceptionHandle(
                    final HttpServletRequest request,
                    final HttpServletResponse response,
                    final CustomException exception) {
                    LOG.info("Exception Handler invoked");
                    ErrorListWsDTO errorData = null;
                    errorData = prepareResponse(response, exception);
                    response.setStatus(Integer.parseInt(exception.getCode()));
                    return errorData;
            }
    
            /**
             * Prepare error response for BAD Request
             *
             * @param response
             * @param exception
             * @return
             */
            private ErrorListWsDTO prepareResponse(final HttpServletResponse response,
                    final AbstractException exception) {
                    final ErrorListWsDTO errorListData = new ErrorListWsDTO();
                    final List<ErrorWsDTO> errorList = new ArrayList<>();
                    response.setStatus(HttpStatus.BAD_REQUEST.value());
                    final ErrorWsDTO errorData = prepareErrorData("500",
                            "FAILURE", exception.getCause().getMessage());
                    errorList.add(errorData);
                    errorListData.setErrors(errorList);
                    return errorListData;
            }
    
            /**
             * This method is used to prepare error data
             *
             * @param code
             *            error code
             * @param status
             *            status can be success or failure
             * @param exceptionMsg
             *            message description
             * @return ErrorDTO
             */
            private ErrorWsDTO prepareErrorData(final String code, final String status,
                    final String exceptionMsg) {
    
                    final ErrorWsDTO errorDTO = new ErrorWsDTO();
                    errorDTO.setReason(code);
                    errorDTO.setType(status);
                    errorDTO.setMessage(exceptionMsg);
                    return errorDTO;
            }
    
        }
        </pre></code>
    
    0 讨论(0)
  • 2020-11-29 05:52

    Forwarding is often done by a filter, in this case the request does not even reach a controller. This would explain why your @ControllerAdvice does not work.

    If you forward in the controller than the @ControllerAdvice should work. Check if spring creates an instance of the class annotated with @ControllerAdvice. For that place a breakpoint in the class and see whether it is hit.

    Add a breakpoint also in the controller method where the forwarding should happen. May be you accidently invoke another controller method than you inspect ?

    These steps should help you resolve the issue.

    In your class annotated with @ControllerAdvice add an ExceptionHandler method annotated with @ExceptionHandler(Exception.class), that should catch every Exception.

    EDIT : You can try to add your own filter that converts the error response returned by the Zuulfilter. There you can change the response as you like.

    How the error response can be customized is explained here :

    exception handling for filter in spring

    Placing the filter correctly may be a little tricky. Not exactly sure about the correct position, but you should be aware of the order of your filters and the place where you handle the exception.

    If you place it before the Zuulfilter, you have to code your error handling after calling doFilter().

    If you place it after the Zuulfilter, you have to code your error handling before calling doFilter().

    Add breakpoints in your filter before and after doFilter() may help to find the correct position.

    0 讨论(0)
  • 2020-11-29 05:55

    The Zuul RequestContext doesn't contain the error.exception as mentioned in this answer.
    Up to date the Zuul error filter:

    @Component
    public class ErrorFilter extends ZuulFilter {
        private static final Logger LOG = LoggerFactory.getLogger(ErrorFilter.class);
    
        private static final String FILTER_TYPE = "error";
        private static final String THROWABLE_KEY = "throwable";
        private static final int FILTER_ORDER = -1;
    
        @Override
        public String filterType() {
            return FILTER_TYPE;
        }
    
        @Override
        public int filterOrder() {
            return FILTER_ORDER;
        }
    
        @Override
        public boolean shouldFilter() {
            return true;
        }
    
        @Override
        public Object run() {
            final RequestContext context = RequestContext.getCurrentContext();
            final Object throwable = context.get(THROWABLE_KEY);
    
            if (throwable instanceof ZuulException) {
                final ZuulException zuulException = (ZuulException) throwable;
                LOG.error("Zuul failure detected: " + zuulException.getMessage());
    
                // remove error code to prevent further error handling in follow up filters
                context.remove(THROWABLE_KEY);
    
                // populate context with new response values
                context.setResponseBody("Overriding Zuul Exception Body");
                context.getResponse().setContentType("application/json");
                // can set any error code as excepted
                context.setResponseStatusCode(503);
            }
            return null;
        }
    }
    
    0 讨论(0)
  • 2020-11-29 05:56

    Here are the steps to do it with @ControllerAdvice:

    1. First add a filter of type error and let it be run before the SendErrorFilter in zuul itself.
    2. Make sure to remove the key associated with the exception from the RequestContext to prevent the SendErrorFilter from executing.
    3. Use RequestDispatcher to forward the request to the ErrorController -- explained below.
    4. Add a @RestController class and make it extends AbstractErrorController, and re-throw the exception again (add it in the step of executing your new error filter with (key, exception), get it from the RequestContext in your controller).

    The exception will now be caught in your @ControllerAdvice class.

    0 讨论(0)
  • 2020-11-29 06:01

    This is what worked for me. RestExceptionResponse is the class which is used within the @ControllerAdvice, so we have an identical exception response in case of internal ZuulExceptions.

    @Component
    @Log4j
    public class CustomZuulErrorFilter extends ZuulFilter {
    
        private static final String SEND_ERROR_FILTER_RAN = "sendErrorFilter.ran";
    
        @Override
        public String filterType() {
            return ERROR_TYPE;
        }
    
        @Override
        public int filterOrder() {
            return SEND_ERROR_FILTER_ORDER - 1; // Needs to run before SendErrorFilter which has filterOrder == 0
        }
    
        @Override
        public boolean shouldFilter() {
            RequestContext ctx = RequestContext.getCurrentContext();
            Throwable ex = ctx.getThrowable();
            return ex instanceof ZuulException && !ctx.getBoolean(SEND_ERROR_FILTER_RAN, false);
        }
    
        @Override
        public Object run() {
            try {
                RequestContext ctx = RequestContext.getCurrentContext();
                ZuulException ex = (ZuulException) ctx.getThrowable();
    
                // log this as error
                log.error(StackTracer.toString(ex));
    
                String requestUri = ctx.containsKey(REQUEST_URI_KEY) ? ctx.get(REQUEST_URI_KEY).toString() : "/";
                RestExceptionResponse exceptionResponse = new RestExceptionResponse(HttpStatus.INTERNAL_SERVER_ERROR, ex, requestUri);
    
                // Populate context with new response values
                ctx.setResponseStatusCode(500);
                this.writeResponseBody(ctx.getResponse(), exceptionResponse);
    
                ctx.set(SEND_ERROR_FILTER_RAN, true);
            }
            catch (Exception ex) {
                log.error(StackTracer.toString(ex));
                ReflectionUtils.rethrowRuntimeException(ex);
            }
            return null;
        }
    
    
        private void writeResponseBody(HttpServletResponse response, Object body) throws IOException {
            response.setContentType("application/json");
            try (PrintWriter writer = response.getWriter()) {
                writer.println(new JSonSerializer().toJson(body));
            }
        }
    }
    

    The output looks like this:

    {
        "timestamp": "2020-08-10 16:18:16.820",
        "status": 500,
        "error": "Internal Server Error",
        "path": "/service",
        "exception": {
            "message": "Filter threw Exception",
            "exceptionClass": "com.netflix.zuul.exception.ZuulException",
            "superClasses": [
                "com.netflix.zuul.exception.ZuulException",
                "java.lang.Exception",
                "java.lang.Throwable",
                "java.lang.Object"
            ],
            "stackTrace": null,
            "cause": {
                "message": "com.netflix.zuul.exception.ZuulException: Forwarding error",
                "exceptionClass": "org.springframework.cloud.netflix.zuul.util.ZuulRuntimeException",
                "superClasses": [
                    "org.springframework.cloud.netflix.zuul.util.ZuulRuntimeException",
                    "java.lang.RuntimeException",
                    "java.lang.Exception",
                    "java.lang.Throwable",
                    "java.lang.Object"
                ],
                "stackTrace": null,
                "cause": {
                    "message": "Forwarding error",
                    "exceptionClass": "com.netflix.zuul.exception.ZuulException",
                    "superClasses": [
                        "com.netflix.zuul.exception.ZuulException",
                        "java.lang.Exception",
                        "java.lang.Throwable",
                        "java.lang.Object"
                    ],
                    "stackTrace": null,
                    "cause": {
                        "message": "Load balancer does not have available server for client: template-scalable-service",
                        "exceptionClass": "com.netflix.client.ClientException",
                        "superClasses": [
                            "com.netflix.client.ClientException",
                            "java.lang.Exception",
                            "java.lang.Throwable",
                            "java.lang.Object"
                        ],
                        "stackTrace": null,
                        "cause": null
                    }
                }
            }
        }
    }
    
    0 讨论(0)
提交回复
热议问题