Too many exception stack traces related to disconnected SockJS clients [SPR-11870] #16489

spring-projects-issues · 2014-06-11T09:36:05Z

Prashant Deva opened SPR-11870 and commented

Using spring websockets, our log seem full of exceptions like these:


[stdout] 16:05:18,957 ERROR clientOutboundChannel-13 handler.ExceptionWebSocketHandlerDecorator:92 - Unhandled error for ExceptionWebSocketHandlerDecorator [delegate=LoggingWebSocketHandlerDecorator [delegate=org.springframework.web.socket.messaging.SubProtocolWebSocketHandler@315934c3]]
[stdout] java.lang.IllegalStateException: The WebSocket session has been closed and no method (apart from close()) may be called on a closed session
[stdout] 	at org.apache.tomcat.websocket.WsSession.checkState(WsSession.java:653)
[stdout] 	at org.apache.tomcat.websocket.WsSession.getUserPrincipal(WsSession.java:582)
[stdout] 	at org.springframework.web.socket.adapter.standard.StandardWebSocketSession.getPrincipal(StandardWebSocketSession.java:123)
[stdout] 	at org.springframework.web.socket.sockjs.transport.session.WebSocketServerSockJsSession.getPrincipal(WebSocketServerSockJsSession.java:73)
[stdout] 	at org.springframework.web.socket.messaging.StompSubProtocolHandler.afterSessionEnded(StompSubProtocolHandler.java:364)
[stdout] 	at org.springframework.web.socket.messaging.SubProtocolWebSocketHandler.clearSession(SubProtocolWebSocketHandler.java:352)
[stdout] 	at org.springframework.web.socket.messaging.SubProtocolWebSocketHandler.afterConnectionClosed(SubProtocolWebSocketHandler.java:347)
[stdout] 	at org.springframework.web.socket.handler.WebSocketHandlerDecorator.afterConnectionClosed(WebSocketHandlerDecorator.java:85)
[stdout] 	at org.springframework.web.socket.handler.LoggingWebSocketHandlerDecorator.afterConnectionClosed(LoggingWebSocketHandlerDecorator.java:71)
[stdout] 	at org.springframework.web.socket.handler.ExceptionWebSocketHandlerDecorator.afterConnectionClosed(ExceptionWebSocketHandlerDecorator.java:89)
[stdout] 	at org.springframework.web.socket.sockjs.transport.session.AbstractSockJsSession.close(AbstractSockJsSession.java:289)
[stdout] 	at org.springframework.web.socket.handler.WebSocketSessionDecorator.close(WebSocketSessionDecorator.java:158)
[stdout] 	at org.springframework.web.socket.messaging.StompSubProtocolHandler.handleMessageToClient(StompSubProtocolHandler.java:287)
[stdout] 	at org.springframework.web.socket.messaging.SubProtocolWebSocketHandler.handleMessage(SubProtocolWebSocketHandler.java:306)
[stdout] 	at org.springframework.messaging.support.ExecutorSubscribableChannel$1.run(ExecutorSubscribableChannel.java:70)
[stdout] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
[stdout] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
[stdout] 	at java.lang.Thread.run(Thread.java:744)

We are using tomcat.

Affects: 4.0.5

Issue Links:

Logs fill with unnecessary stack traces when using SockJS streaming transports [SPR-11438] #16064 Logs fill with unnecessary stack traces when using SockJS streaming transports

Referenced from: commits 49b872e

The text was updated successfully, but these errors were encountered:

spring-projects-issues · 2014-06-11T10:04:48Z

Rossen Stoyanchev commented

Are you sure you're using 4.0.5? This sounds like an issue that was fixed in 4.0.4. See #16244.

spring-projects-issues · 2014-06-11T10:10:30Z

Prashant Deva commented

upgraded to 4.0.5 from 4.0.3 and still seeing the exceptions en masse.

spring-projects-issues · 2014-06-11T10:16:34Z

Prashant Deva commented

updated stack trace from version 4.0.5

17:15:04,102  WARN clientOutboundChannel-23 messaging.SubProtocolWebSocketHandler:258 - Ignoring protocol in WebSocket session after failure to obtain it: java.lang.IllegalStateException: The WebSocket session has been closed and no method (apart from close()) may be called on a closed session
17:15:04,102 ERROR clientOutboundChannel-23 handler.ExceptionWebSocketHandlerDecorator:92 - Unhandled error for ExceptionWebSocketHandlerDecorator [delegate=LoggingWebSocketHandlerDecorator [delegate=org.springframework.web.socket.messaging.SubProtocolWebSocketHandler@17f20f1d]]
java.lang.IllegalStateException: The WebSocket session has been closed and no method (apart from close()) may be called on a closed session
	at org.apache.tomcat.websocket.WsSession.checkState(WsSession.java:653)
	at org.apache.tomcat.websocket.WsSession.getUserPrincipal(WsSession.java:582)
	at org.springframework.web.socket.adapter.standard.StandardWebSocketSession.getPrincipal(StandardWebSocketSession.java:123)
	at org.springframework.web.socket.sockjs.transport.session.WebSocketServerSockJsSession.getPrincipal(WebSocketServerSockJsSession.java:73)
	at org.springframework.web.socket.messaging.StompSubProtocolHandler.afterSessionEnded(StompSubProtocolHandler.java:364)
	at org.springframework.web.socket.messaging.SubProtocolWebSocketHandler.clearSession(SubProtocolWebSocketHandler.java:352)
	at org.springframework.web.socket.messaging.SubProtocolWebSocketHandler.afterConnectionClosed(SubProtocolWebSocketHandler.java:347)
	at org.springframework.web.socket.handler.WebSocketHandlerDecorator.afterConnectionClosed(WebSocketHandlerDecorator.java:85)
	at org.springframework.web.socket.handler.LoggingWebSocketHandlerDecorator.afterConnectionClosed(LoggingWebSocketHandlerDecorator.java:71)
	at org.springframework.web.socket.handler.ExceptionWebSocketHandlerDecorator.afterConnectionClosed(ExceptionWebSocketHandlerDecorator.java:89)
	at org.springframework.web.socket.sockjs.transport.session.AbstractSockJsSession.close(AbstractSockJsSession.java:289)
	at org.springframework.web.socket.handler.WebSocketSessionDecorator.close(WebSocketSessionDecorator.java:158)
	at org.springframework.web.socket.messaging.StompSubProtocolHandler.handleMessageToClient(StompSubProtocolHandler.java:287)
	at org.springframework.web.socket.messaging.SubProtocolWebSocketHandler.handleMessage(SubProtocolWebSocketHandler.java:306)
	at org.springframework.messaging.support.ExecutorSubscribableChannel$1.run(ExecutorSubscribableChannel.java:70)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

spring-projects-issues · 2014-06-11T10:19:43Z

Prashant Deva commented

oh wait, it seems there has been a mistake. Liverebel seems to be deploying the older version with 4.0.3, even though we gave it the new version which uses 4.0.5.
please wait while we correct this on our end. I will update with results

spring-projects-issues · 2014-06-11T10:22:06Z

Rossen Stoyanchev commented

Yeah the stack trace line numbers don't match. I'm pretty sure you're not on 4.0.5.

spring-projects-issues · 2014-06-13T16:37:39Z

Prashant Deva commented

ok using spring 4.0.5, i am getting the following:

Jun 13 16:19:53 dripcast catalina.out:  Caused by: java.io.EOFException: The client aborted the connection.
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.coyote.http11.upgrade.AprServletOutputStream.doWriteInternal(AprServletOutputStream.java:137)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.coyote.http11.upgrade.AprServletOutputStream.doWrite(AprServletOutputStream.java:69)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.coyote.http11.upgrade.AbstractServletOutputStream.writeInternal(AbstractServletOutputStream.java:125)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.coyote.http11.upgrade.AbstractServletOutputStream.write(AbstractServletOutputStream.java:92)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.onWritePossible(WsRemoteEndpointImplServer.java:94)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.doWrite(WsRemoteEndpointImplServer.java:81)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:393)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.startMessage(WsRemoteEndpointImplBase.java:287)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase$TextMessageSendHandler.write(WsRemoteEndpointImplBase.java:687)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendPartialString(WsRemoteEndpointImplBase.java:210)
Jun 13 16:19:53 dripcast catalina.out:  	... 16 more
Jun 13 16:19:53 dripcast catalina.out:  23:19:52,973 ERROR MessageBrokerSockJS-7 handler.LoggingWebSocketHandlerDecorator:61 - Transport error for SockJS session id=m8fm367p
Jun 13 16:19:53 dripcast catalina.out:  java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: The socket [140,592,588,472,480] associated with this connection has been closed.
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.startMessageBlock(WsRemoteEndpointImplBase.java:243)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsSession.sendCloseMessage(WsSession.java:487)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsSession.doClose(WsSession.java:418)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsSession.close(WsSession.java:395)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.adapter.standard.StandardWebSocketSession.closeInternal(StandardWebSocketSession.java:217)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.adapter.AbstractWebSocketSession.close(AbstractWebSocketSession.java:139)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.sockjs.transport.session.WebSocketServerSockJsSession.disconnect(WebSocketServerSockJsSession.java:202)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.sockjs.transport.session.AbstractSockJsSession.writeFrame(AbstractSockJsSession.java:337)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.sockjs.transport.session.AbstractSockJsSession.sendHeartbeat(AbstractSockJsSession.java:373)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.sockjs.transport.session.AbstractSockJsSession$2.run(AbstractSockJsSession.java:391)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
Jun 13 16:19:53 dripcast catalina.out:  	at java.lang.Thread.run(Thread.java:745)
Jun 13 16:19:53 dripcast catalina.out:  Caused by: java.util.concurrent.ExecutionException: java.io.IOException: The socket [140,592,588,472,480] associated with this connection has been closed.
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.FutureToSendHandler.get(FutureToSendHandler.java:102)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.startMessageBlock(WsRemoteEndpointImplBase.java:238)
Jun 13 16:19:53 dripcast catalina.out:  	... 17 more
Jun 13 16:19:53 dripcast catalina.out:  Caused by: java.io.IOException: The socket [140,592,588,472,480] associated with this connection has been closed.
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.coyote.http11.upgrade.AprServletOutputStream.doWrite(AprServletOutputStream.java:60)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.coyote.http11.upgrade.AbstractServletOutputStream.writeInternal(AbstractServletOutputStream.java:125)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.coyote.http11.upgrade.AbstractServletOutputStream.write(AbstractServletOutputStream.java:92)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.onWritePossible(WsRemoteEndpointImplServer.java:94)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.doWrite(WsRemoteEndpointImplServer.java:81)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:393)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.startMessage(WsRemoteEndpointImplBase.java:287)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.startMessageBlock(WsRemoteEndpointImplBase.java:233)
Jun 13 16:19:53 dripcast catalina.out:  	... 17 more
Jun 13 16:19:53 dripcast catalina.out:  23:19:53,783 ERROR MessageBrokerSockJS-3 session.WebSocketServerSockJsSession:365 - Terminating connection after failure to send message to client.
Jun 13 16:19:53 dripcast catalina.out:  java.io.IOException: java.util.concurrent.ExecutionException: java.io.EOFException: The client aborted the connection.
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendPartialString(WsRemoteEndpointImplBase.java:219)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendPartialString(WsRemoteEndpointImplBase.java:185)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointBasic.sendText(WsRemoteEndpointBasic.java:49)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.adapter.standard.StandardWebSocketSession.sendTextMessage(StandardWebSocketSession.java:197)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.adapter.AbstractWebSocketSession.sendMessage(AbstractWebSocketSession.java:104)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.sockjs.transport.session.WebSocketServerSockJsSession.writeFrameInternal(WebSocketServerSockJsSession.java:196)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.sockjs.transport.session.AbstractSockJsSession.writeFrame(AbstractSockJsSession.java:332)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.sockjs.transport.session.AbstractSockJsSession.sendHeartbeat(AbstractSockJsSession.java:373)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.sockjs.transport.session.AbstractSockJsSession$2.run(AbstractSockJsSession.java:391)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
Jun 13 16:19:53 dripcast catalina.out:  	at java.lang.Thread.run(Thread.java:745)
Jun 13 16:19:53 dripcast catalina.out:  Caused by: java.util.concurrent.ExecutionException: java.io.EOFException: The client aborted the connection.
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.FutureToSendHandler.get(FutureToSendHandler.java:102)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendPartialString(WsRemoteEndpointImplBase.java:214)
Jun 13 16:19:53 dripcast catalina.out:  	... 16 more
Jun 13 16:19:53 dripcast catalina.out:  Caused by: java.io.EOFException: The client aborted the connection.
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.coyote.http11.upgrade.AprServletOutputStream.doWriteInternal(AprServletOutputStream.java:137)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.coyote.http11.upgrade.AprServletOutputStream.doWrite(AprServletOutputStream.java:69)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.coyote.http11.upgrade.AbstractServletOutputStream.writeInternal(AbstractServletOutputStream.java:125)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.coyote.http11.upgrade.AbstractServletOutputStream.write(AbstractServletOutputStream.java:92)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.onWritePossible(WsRemoteEndpointImplServer.java:94)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.doWrite(WsRemoteEndpointImplServer.java:81)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:393)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.startMessage(WsRemoteEndpointImplBase.java:287)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase$TextMessageSendHandler.write(WsRemoteEndpointImplBase.java:687)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.sendPartialString(WsRemoteEndpointImplBase.java:210)
Jun 13 16:19:53 dripcast catalina.out:  	... 16 more
Jun 13 16:19:53 dripcast catalina.out:  23:19:53,784 ERROR MessageBrokerSockJS-3 handler.LoggingWebSocketHandlerDecorator:61 - Transport error for SockJS session id=m7ywdk6k
Jun 13 16:19:53 dripcast catalina.out:  java.io.IOException: java.util.concurrent.ExecutionException: java.io.IOException: The socket [140,592,588,095,648] associated with this connection has been closed.
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.startMessageBlock(WsRemoteEndpointImplBase.java:243)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsSession.sendCloseMessage(WsSession.java:487)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsSession.doClose(WsSession.java:418)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsSession.close(WsSession.java:395)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.adapter.standard.StandardWebSocketSession.closeInternal(StandardWebSocketSession.java:217)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.adapter.AbstractWebSocketSession.close(AbstractWebSocketSession.java:139)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.sockjs.transport.session.WebSocketServerSockJsSession.disconnect(WebSocketServerSockJsSession.java:202)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.sockjs.transport.session.AbstractSockJsSession.writeFrame(AbstractSockJsSession.java:337)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.sockjs.transport.session.AbstractSockJsSession.sendHeartbeat(AbstractSockJsSession.java:373)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.web.socket.sockjs.transport.session.AbstractSockJsSession$2.run(AbstractSockJsSession.java:391)
Jun 13 16:19:53 dripcast catalina.out:  	at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
Jun 13 16:19:53 dripcast catalina.out:  	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
Jun 13 16:19:53 dripcast catalina.out:  	at java.lang.Thread.run(Thread.java:745)
Jun 13 16:19:53 dripcast catalina.out:  Caused by: java.util.concurrent.ExecutionException: java.io.IOException: The socket [140,592,588,095,648] associated with this connection has been closed.
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.FutureToSendHandler.get(FutureToSendHandler.java:102)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.startMessageBlock(WsRemoteEndpointImplBase.java:238)
Jun 13 16:19:53 dripcast catalina.out:  	... 17 more
Jun 13 16:19:53 dripcast catalina.out:  Caused by: java.io.IOException: The socket [140,592,588,095,648] associated with this connection has been closed.
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.coyote.http11.upgrade.AprServletOutputStream.doWrite(AprServletOutputStream.java:60)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.coyote.http11.upgrade.AbstractServletOutputStream.writeInternal(AbstractServletOutputStream.java:125)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.coyote.http11.upgrade.AbstractServletOutputStream.write(AbstractServletOutputStream.java:92)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.onWritePossible(WsRemoteEndpointImplServer.java:94)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.server.WsRemoteEndpointImplServer.doWrite(WsRemoteEndpointImplServer.java:81)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.writeMessagePart(WsRemoteEndpointImplBase.java:393)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.startMessage(WsRemoteEndpointImplBase.java:287)
Jun 13 16:19:53 dripcast catalina.out:  	at org.apache.tomcat.websocket.WsRemoteEndpointImplBase.startMessageBlock(WsRemoteEndpointImplBase.java:233)
Jun 13 16:19:53 dripcast catalina.out:  	... 17 more
Jun 13 16:19:53 dripcast catalina.out:  Jun 13, 2014 11:19:53 PM org.apache.tomcat.util.net.AprEndpoint$Acceptor run

spring-projects-issues · 2014-09-03T04:40:38Z

Max Posner commented

In my app I often lost websocket connection. And my logs exactly the same

spring-projects-issues · 2014-09-03T06:26:25Z

Rossen Stoyanchev commented

Is your stack trace like the one in the original or the last comment? If you could please provide a current stack trace and specify your Spring Framework version. Thanks.

spring-projects-issues · 2014-09-03T06:30:13Z

Rossen Stoyanchev commented

Note that in 4.0.3 smart logging was added for stack traces related to clients that have gone away (see #16064). However, we may need some further tightening.

spring-projects-issues · 2014-09-03T21:24:55Z

Rossen Stoyanchev commented

See commit 49b872.

spring-projects-issues · 2014-09-15T22:10:12Z

Max Posner commented

sory for late comment, i have stack trace like in description, version 4.0.2,
i try to update, may be it helps

spring-projects-issues · 2014-09-16T18:58:44Z

Rossen Stoyanchev commented

Okay also have a look at the latest comments under #16769.

spring-projects-issues closed this as completed Sep 16, 2014

spring-projects-issues added type: enhancement A general enhancement in: web Issues in web modules (web, webmvc, webflux, websocket) labels Jan 11, 2019

spring-projects-issues added this to the 4.1 GA milestone Jan 11, 2019

spring-projects-issues assigned rstoyanchev Jan 11, 2019

spring-projects-issues mentioned this issue Jan 11, 2019

Logs fill with unnecessary stack traces when using SockJS streaming transports [SPR-11438] #16064

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Too many exception stack traces related to disconnected SockJS clients [SPR-11870] #16489

Too many exception stack traces related to disconnected SockJS clients [SPR-11870] #16489

spring-projects-issues commented Jun 11, 2014 •

edited

spring-projects-issues commented Jun 11, 2014 •

edited

spring-projects-issues commented Jun 11, 2014

spring-projects-issues commented Jun 11, 2014

spring-projects-issues commented Jun 11, 2014

spring-projects-issues commented Jun 11, 2014

spring-projects-issues commented Jun 13, 2014

spring-projects-issues commented Sep 3, 2014

spring-projects-issues commented Sep 3, 2014

spring-projects-issues commented Sep 3, 2014 •

edited

spring-projects-issues commented Sep 3, 2014

spring-projects-issues commented Sep 15, 2014

spring-projects-issues commented Sep 16, 2014 •

edited

Too many exception stack traces related to disconnected SockJS clients [SPR-11870] #16489

Too many exception stack traces related to disconnected SockJS clients [SPR-11870] #16489

Comments

spring-projects-issues commented Jun 11, 2014 • edited

spring-projects-issues commented Jun 11, 2014 • edited

spring-projects-issues commented Jun 11, 2014

spring-projects-issues commented Jun 11, 2014

spring-projects-issues commented Jun 11, 2014

spring-projects-issues commented Jun 11, 2014

spring-projects-issues commented Jun 13, 2014

spring-projects-issues commented Sep 3, 2014

spring-projects-issues commented Sep 3, 2014

spring-projects-issues commented Sep 3, 2014 • edited

spring-projects-issues commented Sep 3, 2014

spring-projects-issues commented Sep 15, 2014

spring-projects-issues commented Sep 16, 2014 • edited

spring-projects-issues commented Jun 11, 2014 •

edited

spring-projects-issues commented Jun 11, 2014 •

edited

spring-projects-issues commented Sep 3, 2014 •

edited

spring-projects-issues commented Sep 16, 2014 •

edited