近期在使用Feign开发调用其他系统的微服务接口的时候遇到了需求,需要把原来系统抛出来的状态码和异常捕捉以及原样抛出。由于使用了Hystrix熔断,发现Feign返回的异常和原来抛出的不一致,故在此做个解决记录
解决方案:
一、自定义全局异常配置
@Configuration
public class FeignGlobalConfig {
@Bean
ErrorDecoder responseErrorDecoder() {
// 调用异常处理
return new DefaultErrorDecoder();
}
}
二、自定义FeignBadRequestException
public class FeignBadRequestException extends HystrixBadRequestException {
private int code;
public FeignBadRequestException(int code, String message){
super(message);
this.code = code;
}
public int getCode(){
return code;
}
}
三、重写ErrorDecoder解码器
public class DefaultErrorDecoder implements ErrorDecoder {
@Override
public Exception decode(String s, Response response) {
Exception exception = null;
String bodyStr = null;
try {
bodyStr = Util.toString(response.body().asReader());
} catch (IOException e) {
e.printStackTrace();
}
//除了200的其余异常走FeignBadRequestException
if(response.status() != 200){
return new FeignBadRequestException(response.status(), bodyStr);
}
return new RuntimeException(bodyStr);
}
四、编写异常处理
public class RestApiExceptionHandler extends ResponseEntityExceptionHandler {
@ExceptionHandler(value = {FeignBadRequestException.class})
public ResponseEntity<Object> handleFeignException(FeignBadRequestException ex, WebRequest request) {
log.error("Feign Bad Request Error: ", ex);
return handleExceptionInternal(ex, buildFeignResponse(new FeignBadRequestException(ex.getCode(), ex.getMessage())),
new HttpHeaders(), HttpStatus.valueOf(ex.getCode()), request);
}
private String buildFeignResponse(FeignBadRequestException ae) {
return ae.getMessage();
}
}