JAVAutil。同时发生的TimeoutException:状态200后为null OK？

Question

我目前正在开发一个Java11 Spring Boot应用程序。在一个完全的未来中，我向网络服务发射了一大堆REST请求。其中只有一个（似乎是随机的）会导致TimeoutExc0019，尽管它后面跟着一个成功的状态200 OK在日志中收到响应。以下（匿名）日志条目：

[Thread-6] INFO  n.d.b.a.b.i.RESTInterceptor - Request              : <url value>?code=abcd&begindatum=2018-10-01&einddatum=2018-10-02
[http-nio-8080-exec-1] ERROR o.a.c.c.C.[.[.[.[dispatcherServlet] - Servlet.service() for servlet [dispatcherServlet] in context with path [/xxx] threw exception [Request processing failed; nested exception is java.util.concurrent.CompletionException: java.util.concurrent.TimeoutException] with root cause
java.util.concurrent.TimeoutException: null
    at java.base/java.util.concurrent.CompletableFuture$Timeout.run(CompletableFuture.java:2792)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base/java.lang.Thread.run(Thread.java:834)
[Thread-6] DEBUG n.d.b.a.b.i.RESTInterceptor - Response statuscode  : 200 OK
[Thread-6] DEBUG n.d.b.a.b.i.RESTInterceptor - Response headers     : [X-Application-Context:"yyyy", Cache-Control:"no-cache, no-store, max-age=0, must-revalidate", Pragma:"no-cache", Expires:"0", Server:"CD", X-Powered-By:"Unknown", Content-Type:"application/json;charset=UTF-8", Date:"Tue, 06 Apr 2021 15:23:16 GMT", Connection:"close", X-Frame-Options:"SAMEORIGIN", X-XSS-Protection:"1;mode=block", X-Content-Type-Options:"nosniff"]
[Thread-6] INFO  n.d.b.a.b.i.RESTInterceptor - Response             : [{"begindatum":"1993-01-01","id":"aaaaa","vanInstellingserkenningId":"bbbbb","naarInstellingserkenningId":"ccccc","soort":"HIERARCHISCH","naarInstellingserkenning":{"id":"ddddd","type":"ERKENDE_ONDERWIJSINSTELLING","code":"abcd"},"vanInstellingserkenning":{"id":"kkkk","type":"BEVOEGD_GEZAG","code":"12345"}}]

有人有同样的经历吗？我看不出成功完成的请求和“失败”的请求有什么不同。

Answer 1

在对问题进行深入分析之后，我最终发现TimeoutException是从应用程序中其他地方的另一个未来处理中抛出的。我感到困惑的是，未来（异步任务，每个任务都在自己的线程中）的处理与日志文件中的情况不同。日志片段中显示的TimeoutException不会在显示的请求-响应交互中引发。很抱歉给你带来困惑，但是这个答案可能会对其他人有所帮助。