使用okhttp，区分连接超时和读取超时

Question

我正在使用Spring与okhttp和ribbon相关技术。 在连接超时的情况下，我希望可以重试另一个服务实例，但不包括读取超时（由于明显原因）。 这个重试操作将由一个自定义的ribbon重试处理程序来处理。但要实现以上功能，我需要区分读取超时和连接超时。 对于okhttp的行为如下：

• On read timeout:

  java.net.SocketTimeoutException: timeout
      at okio.Okio$3.newTimeoutException(Okio.java:212)
      at okio.AsyncTimeout.exit(AsyncTimeout.java:288)
      at okio.AsyncTimeout$2.read(AsyncTimeout.java:242)
      at okio.RealBufferedSource.indexOf(RealBufferedSource.java:325)
      at okio.RealBufferedSource.indexOf(RealBufferedSource.java:314)
      at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:210)
      at okhttp3.internal.http.Http1xStream.readResponse(Http1xStream.java:184)
      at okhttp3.internal.http.Http1xStream.readResponseHeaders(Http1xStream.java:125)
      at okhttp3.internal.http.HttpEngine.readNetworkResponse(HttpEngine.java:775)
      at okhttp3.internal.http.HttpEngine.access$200(HttpEngine.java:86)
      at okhttp3.internal.http.HttpEngine$NetworkInterceptorChain.proceed(HttpEngine.java:760)
      at okhttp3.internal.http.HttpEngine.readResponse(HttpEngine.java:613)
      at okhttp3.RealCall.getResponse(RealCall.java:244)
      at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:201)
      at com.bluejeans.sample.test.OkHttpConnect$1.intercept(OkHttpConnect.java:25)
      at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
      at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
      at okhttp3.RealCall.execute(RealCall.java:57)
      at com.bluejeans.sample.test.OkHttpConnect.main(OkHttpConnect.java:39)
  Caused by: java.net.SocketTimeoutException: Read timed out
      at java.net.SocketInputStream.socketRead0(Native Method)
      at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
      at java.net.SocketInputStream.read(SocketInputStream.java:170)
      at java.net.SocketInputStream.read(SocketInputStream.java:141)
      at okio.Okio$2.read(Okio.java:140)
      at okio.AsyncTimeout$2.read(AsyncTimeout.java:238)
      ... 16 more
  

• On connect timeout:

   java.net.SocketTimeoutException: connect timed out
      at java.net.PlainSocketImpl.socketConnect(Native Method)
      at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)
      at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
      at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
      at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
      at java.net.Socket.connect(Socket.java:589)
      at okhttp3.internal.Platform.connectSocket(Platform.java:121)
      at okhttp3.internal.io.RealConnection.connectSocket(RealConnection.java:185)
      at okhttp3.internal.io.RealConnection.buildConnection(RealConnection.java:170)
      at okhttp3.internal.io.RealConnection.connect(RealConnection.java:111)
      at okhttp3.internal.http.StreamAllocation.findConnection(StreamAllocation.java:187)
      at okhttp3.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:123)
      at okhttp3.internal.http.StreamAllocation.newStream(StreamAllocation.java:93)
      at okhttp3.internal.http.HttpEngine.connect(HttpEngine.java:296)
      at okhttp3.internal.http.HttpEngine.sendRequest(HttpEngine.java:248)
      at okhttp3.RealCall.getResponse(RealCall.java:243)
      at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:201)
      at com.bluejeans.sample.test.OkHttpConnect$1.intercept(OkHttpConnect.java:25)
      at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
      at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
      at okhttp3.RealCall.execute(RealCall.java:57)
      at com.bluejeans.sample.test.OkHttpConnect.main(OkHttpConnect.java:39)
  

根据异常信息做决策似乎不是一个好主意。有没有推荐的方法来实现这个功能呢？

- Tanmay

---

请提供堆栈跟踪。 - user207421

你知道你是在进行连接还是读取操作。你可以在每种情况下单独捕获异常。这并不困难。 - user207421

我只是在进行一个http调用。异常是由okhttp库抛出的。问题在于，无论哪种情况下，okhttp都会抛出相同的异常，我无法仅通过异常类来判断它是读取超时还是连接超时。 - Tanmay

Answer 1

如果您不想依赖于消息，您也可以选择以下选项。但是，这两个选项都需要 JUnit 覆盖率，因为 OkHttp 的开发人员可能会在未来更改其实现。

1. 使用异常原因来决定如何处理请求：

   try {
       ...
   } catch (SocketTimeoutException e) {
       if (e.getCause() != null && e.getCause() instanceof SocketTimeoutException) {
           // 读取超时
       } else {
           // socket 超时
       }
   }
   

2. 循环遍历堆栈跟踪：

   try {
       ...
   } catch (SocketTimeoutException e) {
       boolean isConnectException = false;
       for (StackTraceElement elem : e.getStackTrace()) {
           if ("java.net.Socket".equals(elem.getClassName()) &&
                   "connect".equals(elem.getMethodName())) {
               isConnectException = true;
               break;
           }
       }
       ...
   }

- Franz Fellner