快捷導(dǎo)航

記一次線上SpringCloud Feign請求服務(wù)超時(shí)異常排查問題

更新時(shí)間：2022年01月13日 15:17:05 作者：小鄧學(xué)長

這篇文章主要介紹了記一次線上SpringCloud Feign請求服務(wù)超時(shí)異常排查問題,本項(xiàng)目與下游項(xiàng)目均注冊在Eureka上面，對這個(gè)1秒就超時(shí)感到很迷惑，于是開始查閱底層源碼之旅。需要的朋友可以參考下

由于近期線上單量暴漲，第三方反饋部分工單業(yè)務(wù)存在查詢處理失敗現(xiàn)象，經(jīng)排查是當(dāng)前系統(tǒng)通過FeignClient調(diào)用下游系統(tǒng)出現(xiàn)部分超時(shí)失?。ó惓４a貼在下方）。

Caused by: feign.RetryableException: Read timed out executing POST http://xxxx
at feign.FeignException.errorExecuting(FeignException.java:84) ~[feign-core-10.1.0.jar!/:na]
at feign.SynchronousMethodHandler.executeAndDecode(SynchronousMethodHandler.java:113) ~[feign-core-10.1.0.jar!/:na]
at feign.SynchronousMethodHandler.invoke(SynchronousMethodHandler.java:78) ~[feign-core-10.1.0.jar!/:na]
at feign.ReflectiveFeign$FeignInvocationHandler.invoke(ReflectiveFeign.java:103) ~[feign-core-10.1.0.jar!/:na]
at com.sun.proxy.$Proxy141.creditReportConvert(Unknown Source) ~[na:na]
Caused by: java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method) ~[na:1.8.0_121]
at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) ~[na:1.8.0_121]
at java.net.SocketInputStream.read(SocketInputStream.java:171) ~[na:1.8.0_121]
at java.net.SocketInputStream.read(SocketInputStream.java:141) ~[na:1.8.0_121]
at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) ~[na:1.8.0_121]
at java.io.BufferedInputStream.read1(BufferedInputStream.java:286) ~[na:1.8.0_121]
at java.io.BufferedInputStream.read(BufferedInputStream.java:345) ~[na:1.8.0_121]
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:704) ~[na:1.8.0_121]
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:647) ~[na:1.8.0_121]
at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1569) ~[na:1.8.0_121]
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) ~[na:1.8.0_121]
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) ~[na:1.8.0_121]
at feign.Client$Default.convertResponse(Client.java:143) ~[feign-core-10.1.0.jar!/:na]
at feign.Client$Default.execute(Client.java:68) ~[feign-core-10.1.0.jar!/:na]
at org.springframework.cloud.openfeign.ribbon.FeignLoadBalancer.execute(FeignLoadBalancer.java:93) ~[spring-cloud-openfeign-core-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
at org.springframework.cloud.openfeign.ribbon.FeignLoadBalancer.execute(FeignLoadBalancer.java:56) ~[spring-cloud-openfeign-core-2.1.1.RELEASE.jar!/:2.1.1.RELEASE]
at com.netflix.client.AbstractLoadBalancerAwareClient$1.call(AbstractLoadBalancerAwareClient.java:104) ~[ribbon-loadbalancer-2.3.0.jar!/:2.3.0]
at com.netflix.loadbalancer.reactive.LoadBalancerCommand$3$1.call(LoadBalancerCommand.java:303) ~[ribbon-loadbalancer-2.3.0.jar!/:2.3.0]

通過系統(tǒng)慢請求捕捉攔截，發(fā)現(xiàn)當(dāng)前請求僅耗時(shí)1031毫秒，就觸發(fā)Read timed out超時(shí)錯(cuò)誤，本項(xiàng)目與下游項(xiàng)目均注冊在Eureka上面，對這個(gè)1秒就超時(shí)感到很迷惑，于是開始查閱底層源碼之旅。

通過跟蹤代碼可以在feign.Request內(nèi)部類Options構(gòu)造函數(shù)默認(rèn)配置連接超時(shí)10秒，讀超時(shí)60秒。然而本次調(diào)用請求僅耗時(shí)1秒左右就被掐斷連接提示超時(shí)錯(cuò)誤，初步判斷默認(rèn)這個(gè)超時(shí)配置并未生效導(dǎo)致。

寫到這，咱們先回顧下Feign鏈路完整調(diào)用流程步驟。

可以看出Feign調(diào)用分為Hystrix、Ribbon兩層，一般高版本的Hystrix默認(rèn)是關(guān)閉的（本項(xiàng)目Hystrix默認(rèn)是關(guān)閉的，那么現(xiàn)在需要去分析Ribbon層調(diào)用配置信息）

可以看到RibbonClientConfiguration默認(rèn)配置的讀超時(shí)和連接超時(shí)時(shí)間1000毫秒=1秒，在沒有配置超時(shí)情況下當(dāng)前這個(gè)超時(shí)是符合本次調(diào)用超時(shí)錯(cuò)誤觸發(fā)。

我們可以在FeignLoadBalancer的execute方法中看到當(dāng)IClientConfig為空的時(shí)候進(jìn)行覆蓋超時(shí)時(shí)間，默認(rèn)是取Ribbon的超時(shí)時(shí)間，并不是Feign Options默認(rèn)的超時(shí)時(shí)間。

public FeignLoadBalancer(ILoadBalancer lb, IClientConfig clientConfig,
            ServerIntrospector serverIntrospector) {
        super(lb, clientConfig);
        this.setRetryHandler(RetryHandler.DEFAULT);
        this.clientConfig = clientConfig;
        this.ribbon = RibbonProperties.from(clientConfig);
        RibbonProperties ribbon = this.ribbon;
        this.connectTimeout = ribbon.getConnectTimeout();
        this.readTimeout = ribbon.getReadTimeout();
        this.serverIntrospector = serverIntrospector;
    }

如果application.properties文件中有配置超時(shí)時(shí)間，則使用配置的超時(shí)時(shí)間。否則是取Ribbon默認(rèn)的超時(shí)時(shí)間，也就是網(wǎng)上所說的Feign調(diào)用服務(wù)的默認(rèn)時(shí)長是1秒鐘，也就是如果超過1秒沒連接上或者超過1秒沒響應(yīng)，那么會(huì)相應(yīng)的報(bào)錯(cuò)。

實(shí)際業(yè)務(wù)中服務(wù)如果響應(yīng)時(shí)間超過1秒，咱們可以按照實(shí)際響應(yīng)情況給予配置相對應(yīng)的超時(shí)時(shí)間，下面分別貼出properties和yml版本的配置

#properties版本
feign.client.config.default.connectTimeout=60000
feign.client.config.default.readTimeout=60000
#yml版本
feign:
  client:
    config:
      default:
        connectTimeout: 60000
        readTimeout: 60000

到此這篇關(guān)于記一次線上SpringCloud Feign請求服務(wù)超時(shí)異常排查的文章就介紹到這了,更多相關(guān)SpringCloud Feign請求服務(wù)超時(shí)內(nèi)容請搜索腳本之家以前的文章或繼續(xù)瀏覽下面的相關(guān)文章希望大家以后多多支持腳本之家！

您可能感興趣的文章: