2016-11-16 87 views
4

我想覆盖zuul代理的默认senderorfilter,以便我可以在网关后面的服务崩溃/关闭时提供更好的响应。下面是我从答案参加了Customizing Zuul Exception覆盖zuul错误过滤器导致转发错误

public class RabbrErrorFilter extends ZuulFilter { 

private static final Logger log = LoggerFactory.getLogger(RabbrErrorFilter.class); 
protected static final String SEND_ERROR_FILTER_RAN = "sendErrorFilter.ran"; 

@Override 
public String filterType() { 
    return "post"; 
} 

@Override 
public int filterOrder() { 
    return Integer.MIN_VALUE; // 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 
    RequestContext ctx = RequestContext.getCurrentContext(); 
    return ctx.containsKey("error.status_code") && !ctx.getBoolean(SEND_ERROR_FILTER_RAN,false); 
} 
@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 
      ctx.setSendZuulResponse(false); 
     } 
    } 
    catch (Exception ex) { 
     log.error("Exception filtering in custom error filter", ex); 
     ReflectionUtils.rethrowRuntimeException(ex); 
    } 
    return null; 
} 

我再也忍受不了当zuul异常被抛出在运行的代码()被执行调试检查代码,但在控制台日志中我得到这个:

com.netflix.zuul.exception.ZuulException: Forwarding error 
    at org.springframework.cloud.netflix.zuul.filters.route.RibbonRoutingFilter.handleException(RibbonRoutingFilter.java:157) ~[spring-cloud-netflix-core-1.1.0.RC2.jar:1.1.0.RC2] 
    at org.springframework.cloud.netflix.zuul.filters.route.RibbonRoutingFilter.forward(RibbonRoutingFilter.java:132) ~[spring-cloud-netflix-core-1.1.0.RC2.jar:1.1.0.RC2] 
    at org.springframework.cloud.netflix.zuul.filters.route.RibbonRoutingFilter.run(RibbonRoutingFilter.java:78) ~[spring-cloud-netflix-core-1.1.0.RC2.jar:1.1.0.RC2] 
    at com.netflix.zuul.ZuulFilter.runFilter(ZuulFilter.java:112) ~[zuul-core-1.1.0.jar:1.1.0] 
    at com.netflix.zuul.FilterProcessor.processZuulFilter(FilterProcessor.java:197) ~[zuul-core-1.1.0.jar:1.1.0] 
    at com.netflix.zuul.FilterProcessor.runFilters(FilterProcessor.java:161) ~[zuul-core-1.1.0.jar:1.1.0] 
    at com.netflix.zuul.FilterProcessor.route(FilterProcessor.java:120) ~[zuul-core-1.1.0.jar:1.1.0] 
    at com.netflix.zuul.ZuulRunner.route(ZuulRunner.java:96) ~[zuul-core-1.1.0.jar:1.1.0] 
    at com.netflix.zuul.http.ZuulServlet.route(ZuulServlet.java:116) ~[zuul-core-1.1.0.jar:1.1.0] 
    at com.netflix.zuul.http.ZuulServlet.service(ZuulServlet.java:81) ~[zuul-core-1.1.0.jar:1.1.0] 

,并从网关后面的服务的响应与状态500

超时 - 编辑* 更新弹簧云依赖性(包含zuul 1.3.0核心)没有解决这个问题

+1

显然你只需要[keymaster](https://youtu.be/N9L7UUp0FxY?t=12s)。 –

+0

你可以为zuul添加你的application.yml吗? –

+0

Zuul的默认SendErrorFilter在1.3.0版本中发生了很大变化。它不再是后过滤器。它是1.3.0的错误过滤器,内部变化非常大。你最好检查一下新的SendErrorFilter的源代码。 –

回答

1

请检查此解决方案:Spring Cloud: Zuul error handling。它对我有用,特别适用于Zuul的转发错误。

Zuul错误处理正在通过RibbonRoutingFilter和SendErrorFilter处理,并将任何错误的请求转发到$ {error.path},默认为'/ error'。如果您继承Spring Boot的BasicErrorController将处理的默认值。您可以忽略此行为并实现您自己的ErrorController。

您不一定需要遵循Vnd错误样式,只需按照编写Spring的自定义实现ErrorController的一般逻辑即可。

+1

该帖子相当老,但这是我最终要做的,以解决这个问题 –

+0

请在这里包含链接页面的重要部分,以防它变为404。 – Veve

+1

@Veve我已经添加了该帖子的关键引用,其中几乎没有足够的想法,并想出了一个定制的解决方案。不确定复制粘贴整个代码块是否符合道德标准 – sainr