Bug 68878 - 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 68908
Alias: None
Product: Tomcat 9
Classification: Unclassified
Component: WebSocket (show other bugs)
Version: 9.0.39
Hardware: PC Linux
: P2 normal (vote)
Target Milestone: -----
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-10 03:33 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-10 03:33:17 UTC 
HandlerInterceptor.afterCompletion thread exception appears online
Java. lang. NullPointerException: null
At org. springframework. boot. actor. metrics. web. Servlet LongTaskTimingHandlerInterceptor. stopLongTaskTimers (LongTaskTimingHandlerInterceptor. java: 123)~[spring boot actor 2.3.5. RELEASE. jar!/: 2.3.5. RELEASE]
At org. springframework. boot. actor. metrics. web. Servlet LongTaskTimingHandlerInterceptor. afterCompletion (LongTaskTimingHandlerInterceptor. java: 79),
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:49:38 UTC 

*** This bug has been marked as a duplicate of bug 68908 ***