Bug 68908 - Tomcat feints death, there is no ClientPoller thread in the stack information
Summary: Tomcat feints death, there is no ClientPoller thread in the stack information
Status: RESOLVED DUPLICATE of bug 64839
Alias: None
Product: Tomcat 9
Classification: Unclassified
Component: WebSocket (show other bugs)
Version: 9.0.39
Hardware: PC All
: P2 normal (vote)
Target Milestone: -----
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
: 68878 (view as bug list)
Depends on:
Blocks:
 
Reported: 2024-04-17 01:50 UTC by huangzeling
Modified: 2024-04-17 08:49 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description huangzeling 2024-04-17 01:50:06 UTC 
springboot Tomcat 9.0.39  feints death, there is no ClientPoller thread in the stack information,The error is as follows
[http-nio-18080-exec-146] o.s.web.servlet.HandlerExecutionChain    : HandlerInterceptor.afterCompletion threw exception
java.lang.NullPointerException: null
org.springframework.boot.actuate.metrics.web.servlet.LongTaskTimingHandlerInterceptor.stopLongTaskTimers(LongTaskTimingHandlerInterceptor.java:123) ~[spring-boot-actuator-2.3.5.RELEASE.jar!/:2.3.5.RELEASE]
org.springframework.boot.actuate.metrics.web.servlet.LongTaskTimingHandlerInterceptor.afterCompletion(LongTaskTimingHandlerInterceptor.java:79) ~[spring-boot-actuator-2.3.5.RELEASE.jar!/:2.3.5.RELEASE]
Upon checking the stack information, it was found that the thread of ClientPoller in Tomcat was missing. Tomcat experienced a fake death situation without any access log. I suspect it may be related to websocket, as a websocket client disconnected and experienced the following situation
Comment 1 Mark Thomas 2024-04-17 08:44:37 UTC 

*** This bug has been marked as a duplicate of bug 64839 ***
Comment 2 Mark Thomas 2024-04-17 08:49:38 UTC 
*** Bug 68878 has been marked as a duplicate of this bug. ***