Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IOException when closing the browser tab #13

Closed
uyilmaz opened this issue Feb 23, 2017 · 1 comment
Closed

IOException when closing the browser tab #13

uyilmaz opened this issue Feb 23, 2017 · 1 comment

Comments

@uyilmaz
Copy link

uyilmaz commented Feb 23, 2017

After I leave a room and close the browser tab those exceptions occur:

java.io.IOException: An established connection was aborted by the software in your host machine at sun.nio.ch.SocketDispatcher.write0(Native Method) ~[na:1.8.0_121] at sun.nio.ch.SocketDispatcher.write(Unknown Source) ~[na:1.8.0_121] at sun.nio.ch.IOUtil.writeFromNativeBuffer(Unknown Source) ~[na:1.8.0_121] at sun.nio.ch.IOUtil.write(Unknown Source) ~[na:1.8.0_121] at sun.nio.ch.SocketChannelImpl.write(Unknown Source) ~[na:1.8.0_121] at org.apache.tomcat.util.net.SecureNioChannel.flush(SecureNioChannel.java:143) ~[tomcat-embed-core-8.5.4.jar!/:8.5.4] at org.apache.tomcat.util.net.SecureNioChannel.close(SecureNioChannel.java:479) ~[tomcat-embed-core-8.5.4.jar!/:8.5.4] at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.close(NioEndpoint.java:1185) ~[tomcat-embed-core-8.5.4.jar!/:8.5.4] at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.doClose(WsRemoteEndpointImplServer.java:171) ~[tomcat-embed-websocket-8.5.4.j ar!/:8.5.4] at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.close(WsRemoteEndpointImplBase.java:710) [tomcat-embed-websocket-8.5.4.jar!/:8.5.4] at org.apache.tomcat.websocket.WsSession.sendCloseMessage(WsSession.java:613) [tomcat-embed-websocket-8.5.4.jar!/:8.5.4] at org.apache.tomcat.websocket.WsSession.onClose(WsSession.java:526) [tomcat-embed-websocket-8.5.4.jar!/:8.5.4] at org.apache.tomcat.websocket.WsFrameBase.processDataControl(WsFrameBase.java:348) [tomcat-embed-websocket-8.5.4.jar!/:8.5.4] at org.apache.tomcat.websocket.WsFrameBase.processData(WsFrameBase.java:290) [tomcat-embed-websocket-8.5.4.jar!/:8.5.4] at org.apache.tomcat.websocket.WsFrameBase.processInputBuffer(WsFrameBase.java:131) [tomcat-embed-websocket-8.5.4.jar!/:8.5.4] at org.apache.tomcat.websocket.server.WsFrameServer.onDataAvailable(WsFrameServer.java:69) [tomcat-embed-websocket-8.5.4.jar!/:8.5.4] at org.apache.tomcat.websocket.server.WsHttpUpgradeHandler.upgradeDispatch(WsHttpUpgradeHandler.java:148) [tomcat-embed-websocket-8.5.4.jar!/: 8.5.4] at org.apache.coyote.http11.upgrade.UpgradeProcessorInternal.dispatch(UpgradeProcessorInternal.java:54) [tomcat-embed-core-8.5.4.jar!/:8.5.4] at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:53) [tomcat-embed-core-8.5.4.jar!/:8.5.4] at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:785) [tomcat-embed-core-8.5.4.jar!/:8.5.4] at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1425) [tomcat-embed-core-8.5.4.jar!/:8.5.4] at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) [tomcat-embed-core-8.5.4.jar!/:8.5.4] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [na:1.8.0_121] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [na:1.8.0_121] at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) [tomcat-embed-core-8.5.4.jar!/:8.5.4] at java.lang.Thread.run(Unknown Source) [na:1.8.0_121]

I'm guessing it's not a bug but it fills up the logs anyways.

@mslosarz
Copy link
Owner

This issue was fixed in 0.0.6 version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants