您好,登錄后才能下訂單哦!
本篇內(nèi)容介紹了“Spring Cloud Gateway Hystrix fallback怎么獲取異常信息”的有關(guān)知識(shí),在實(shí)際案例的操作過(guò)程中,不少人都會(huì)遇到這樣的困境,接下來(lái)就讓小編帶領(lǐng)大家學(xué)習(xí)一下如何處理這些情況吧!希望大家仔細(xì)閱讀,能夠?qū)W有所成!
gateway fallback后,需要知道請(qǐng)求的是哪個(gè)接口以及具體的異常信息,根據(jù)不同的請(qǐng)求以及異常進(jìn)行不同的處理。一開始根據(jù)網(wǎng)上一篇博客上的做法:
pom.xml:
<dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-gateway</artifactId> </dependency> <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-netflix-hystrix</artifactId> </dependency>
application.yml:
spring: cloud: gateway: discovery: locator: enabled: false lowerCaseServiceId: true routes: - id: auth-server uri: lb://MS-OAUTH2-SERVER predicates: - Path=/** default-filters: - name: Hystrix args: name: fallbackcmd fallbackUri: forward:/fallback
然后fallback就是這樣:
@RestController @Slf4j public class FallbackController { @RequestMapping(value = "/fallback") @ResponseStatus public Mono<Map<String, Object>> fallback(ServerWebExchange exchange, Throwable throwable) { Map<String, Object> result = new HashMap<>(3); ServerHttpRequest request = exchange.getRequest(); log.error("接口調(diào)用失敗,URL={}", request.getPath().pathWithinApplication().value(), throwable); result.put("code", 60002); result.put("data", null); result.put("msg", "接口調(diào)用失敗!"); return Mono.just(result); } }
但是測(cè)試發(fā)現(xiàn),這樣取出來(lái)的接口地址只是“/fallback”本身,并且沒(méi)有異常信息:
后來(lái)我重新到HystrixGatewayFilterFactory類中去查看,發(fā)現(xiàn)了異常信息其實(shí)在exchange里:
而請(qǐng)求的接口也通過(guò)debug找到了:
所以將代碼改成如下:
@RestController @Slf4j public class FallbackController { @RequestMapping(value = "/fallback") @ResponseStatus public Mono<Map<String, Object>> fallback(ServerWebExchange exchange) { Map<String, Object> result = new HashMap<>(3); result.put("code", 60002); result.put("data", null); Exception exception = exchange.getAttribute(ServerWebExchangeUtils.HYSTRIX_EXECUTION_EXCEPTION_ATTR); ServerWebExchange delegate = ((ServerWebExchangeDecorator) exchange).getDelegate(); log.error("接口調(diào)用失敗,URL={}", delegate.getRequest().getURI(), exception); if (exception instanceof HystrixTimeoutException) { result.put("msg", "接口調(diào)用超時(shí)"); } else if (exception != null && exception.getMessage() != null) { result.put("msg", "接口調(diào)用失敗: " + exception.getMessage()); } else { result.put("msg", "接口調(diào)用失敗"); } return Mono.just(result); } }
正常取到請(qǐng)求路徑以及異常信息:
消費(fèi)者服務(wù)--service 的實(shí)現(xiàn)如下:
@Service public class BookService { @Autowired public RestTemplate restTemplate; @HystrixCommand(fallbackMethod = "addServiceFallback") public Book getBook( Integer bookId ){ return restTemplate.getForObject("http://provider-service/boot/book?bookId={bookId}",Book.class , bookId); } public String addServiceFallback(){ System.out.println("error addServiceFallback.... "); return "error" ; } }
就會(huì)出現(xiàn)如下所述的異常
Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this as a fallback.Fri May 25 14:27:51 CST 2018
There was an unexpected error (type=Internal Server Error, status=500).
fallback method wasn't found: addServiceFallback([class java.lang.Integer])
這是因?yàn)橹付ǖ?備用方法 addServiceFallback 和 原方法getBook 的參數(shù)個(gè)數(shù),參數(shù)類型 不同造成的;
修改addServiceFallback 方法:
public String addServiceFallback(Integer bookId){ System.out.println("error addServiceFallback.... "); return "error" ; }
繼續(xù)運(yùn)行,就會(huì)出現(xiàn)如下所述的異常
Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this as a fallback.Fri May 25 14:32:24 CST 2018
There was an unexpected error (type=Internal Server Error, status=500).
Incompatible return types. Command method: public com.bmcc.springboot.model.Book com.bmcc.springboot.service.BookService.getBook(java.lang.Integer); Fallback method: public java.lang.String com.bmcc.springboot.service.BookService.addServiceFallback(java.lang.Integer); Hint: Fallback method 'public java.lang.String com.bmcc.springboot.service.BookService.addServiceFallback(java.lang.Integer)' must return: class com.bmcc.springboot.model.Book or its subclass
這是因?yàn)橹付ǖ?備用方法 addServiceFallback 和 原方法getBook 雖然 參數(shù)個(gè)數(shù),參數(shù)類型 相同 ,但是 方法的返回值類型不同造成的;
修改addServiceFallback 方法:
public Book addServiceFallback(Integer bookId){ System.out.println("error addServiceFallback.... "); return new Book() ; }
繼續(xù)運(yùn)行,這樣就可以看到當(dāng)一個(gè)服務(wù)提供者異常關(guān)閉時(shí), 消費(fèi)者(消費(fèi)者采用輪詢的方式消費(fèi)服務(wù))再繼續(xù)訪問(wèn)服務(wù)時(shí),不會(huì)拋出異常頁(yè)面,而是如下:
{"bookId":0,"bookName":null,"price":null,"publisher":null}
“Spring Cloud Gateway Hystrix fallback怎么獲取異常信息”的內(nèi)容就介紹到這里了,感謝大家的閱讀。如果想了解更多行業(yè)相關(guān)的知識(shí)可以關(guān)注億速云網(wǎng)站,小編將為大家輸出更多高質(zhì)量的實(shí)用文章!
免責(zé)聲明:本站發(fā)布的內(nèi)容(圖片、視頻和文字)以原創(chuàng)、轉(zhuǎn)載和分享為主,文章觀點(diǎn)不代表本網(wǎng)站立場(chǎng),如果涉及侵權(quán)請(qǐng)聯(lián)系站長(zhǎng)郵箱:is@yisu.com進(jìn)行舉報(bào),并提供相關(guān)證據(jù),一經(jīng)查實(shí),將立刻刪除涉嫌侵權(quán)內(nèi)容。