https://bz.apache.org/bugzilla/show_bug.cgi?id=65408
--- Comment #18 from jiangyangyang <739711...@qq.com> --- (In reply to Thomas Sartissohn from comment #17) > We face the issue with 8.5.66 and 8.5.75 1、From the perspective of this exception scenario, it only occurs when HTTP and websocket exist at the same time, only HTTP is normal. I suspect that excuteor may have a common similar request session when executing HTTP and websocket, resulting in being recycled twice. But I have no way to reproduce the trigger scene, maybe just a guess. 2、Is executor recycling asynchronous? Increasing the queue size for the executor and adding excuter recycling verification may have some effects. But It may need to reproduce the scene and trials. 3、Will there be optimization in subsequent versions? Thank for your reply !!! -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
