https://bz.apache.org/bugzilla/show_bug.cgi?id=57489
--- Comment #17 from Barry Coughlan <b.coughl...@gmail.com> --- I tried creating a test for this today. It turns out that this problem only happens when a websocket is not closed with a proper closing handshake. Most Websocket clients are quite polite when closing websockets, they will send a close frame and then wait for the handshake before closing the TCP connection. This means that the problem can't be replicated by doing session.close() in a Tomcat websocket client. The reason that I can replicate this with Tyrus is that Tyrus sends a websocket close frame but then closes the TCP connection immediately without completing the handshake. The steps with the example in my previous post and Tyrus CLI are: 1. Open connection 2. Send message, breaking in the @OnMessage 3. Close connection in Tyrus (or kill -9 the process to send just a TCP RST, the result is the same) 4. Resume @OnMessage (which sends a message) Any suggestions on how to automate the test? Can I force a Tomcat client's socket to close without a handshake? -- 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
