https://bz.apache.org/bugzilla/show_bug.cgi?id=63191
--- Comment #11 from Mark Thomas <ma...@apache.org> --- Going back to the original thread dump with the "long" and the "short" stack traces... It is possible that the short stack trace is Tomcat trying to send the rest of the message sent via Async.sendText() and it blocked by the longer stack trace which is, in turn, blocked because the CometD Promise has not completed. Hence my question: what is that Promise waiting for? I don't know the CometD code well enough to trace it through to answer that question. I can see possibilities for deadlock here but it could be a complete red herring. What would be helpful at this point is an explanation of the execution path of CometD that shows what action the Promise is waiting to complete. -- 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
