https://bz.apache.org/bugzilla/show_bug.cgi?id=63191
--- Comment #7 from Boris Petrov <boris_pet...@live.com> --- In the GitHub thread I also explained that I tried putting try/catch around the sendText call exactly because sometimes the callback is not called but rather an exception is thrown: https://github.com/cometd/cometd/issues/820#issuecomment-457784822 And it's not the case. I even opened a bug in Tomcat about that: https://bz.apache.org/bugzilla/show_bug.cgi?id=63114 Where you explained that this was according to the spec. I'll provide the stacktrace on Monday. I would think that the "large" stacktrace/thread is the one that calls "sendText" but let's see. In the second post in this issue here I wrote about the connectors: This happens both with the APR endpoint and with the Nio one (when I'm using our site over HTTPS or over HTTP). So I guess the problem is outside the connectors themselves. About the version - I explicitly opened this issue here noting that the bug is for Tomcat 9.0.16. That was the first thing I tried when it came out - but it doesn't fix the issue unfortunately. The error happens 99% of the time after a page refresh - some messages are streamed over the websocket but then I think when CometD sends heartbeats - that's when it fails. So I don't think these are big messages, but it probably can happen with such also. Not sure about that. -- 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
