https://issues.apache.org/bugzilla/show_bug.cgi?id=55799
--- Comment #11 from Mark Thomas <ma...@apache.org> --- OK. Getting better but maybe not quite there yet. Because WebSocket has the potential for multiple threads to be working with a socket concurrently (one read, one write) there is a world of opportunity for weird and wonderful failure modes. It is possible that that is what we are seeing here but I'd like to at least understand each class of exceptions you are seeing. The IOExceptions and ClosedChannelExceptions are expected when the client drops the connection. I'm not worried about these. The IllegalStateException (closed) might be OK but I need to confirm. The IllegalStateException (report a bug) shouldn't happen so I want to look at this some more. The "Received new data frame but previous continuous frame is unfinished." definitely shouldn't happen. Need to look into that as well. -- 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
