Hi, Please try with Tomcat 8.5.11. There were some improvements lately. What I find strange in the stacktrace is that the server is notified that the client closed the connection and still it tries to write a close frame back to it. I have two recommendations: 1) switch temporarily to English locale so that the error messages are more clear to non-German people. Google Translate helps but the message doesn't directly map to any of the error messages I know of in English 2) ask this question in Tomcat forums (us...@tomcat.apache.org)
Martin Grigorov Wicket Training and Consulting https://twitter.com/mtgrigorov On Sat, Jan 28, 2017 at 8:40 PM, Marc <marcgiff...@web.de> wrote: > It seems that this exception only occurs in Google Chrome... > > -- > View this message in context: http://apache-wicket.1842946. > n4.nabble.com/Wicket-Websocket-Exception-is-logged- > in-WicketEndpoint-if-the-user-is-closing-the-browser- > tp4676886p4676889.html > Sent from the Users forum mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
