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

Websocket session has been closed #25

Open
Ogniute opened this issue Feb 17, 2014 · 0 comments
Open

Websocket session has been closed #25

Ogniute opened this issue Feb 17, 2014 · 0 comments

Comments

@Ogniute
Copy link

Ogniute commented Feb 17, 2014

Hi Rossen,

i am trying to implement websockets in our project and with the your simple message broker it works realy fine. But when i switch to a relay broker (RabbitMq) i get the following exception when i want to connect a stompclient:

Information: CONNECT: [id: 0xa3023e5e, /127.0.0.1:51969 => /127.0.0.1:61613]
Feb 17, 2014 5:56:38 PM org.springframework.web.socket.handler.ExceptionWebSocketHandlerDecorator afterConnectionClosed
Schwerwiegend: Unhandled error for ExceptionWebSocketHandlerDecorator [delegate=LoggingWebSocketHandlerDecorator [delegate=org.springframework.web.socket.messaging.SubProtocolWebSocketHandler@78be921d]]
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:652)
at org.apache.tomcat.websocket.WsSession.getNegotiatedSubprotocol(WsSession.java:298)
at org.springframework.web.socket.adapter.standard.StandardWebSocketSession.getAcceptedProtocol(StandardWebSocketSession.java:138)
at org.springframework.web.socket.sockjs.transport.session.WebSocketServerSockJsSession.getAcceptedProtocol(WebSocketServerSockJsSession.java:91)
at org.springframework.web.socket.messaging.SubProtocolWebSocketHandler.findProtocolHandler(SubProtocolWebSocketHandler.java:207)
at org.springframework.web.socket.messaging.SubProtocolWebSocketHandler.afterConnectionClosed(SubProtocolWebSocketHandler.java:282)
at org.springframework.web.socket.handler.WebSocketHandlerDecorator.afterConnectionClosed(WebSocketHandlerDecorator.java:69)
at org.springframework.web.socket.handler.LoggingWebSocketHandlerDecorator.afterConnectionClosed(LoggingWebSocketHandlerDecorator.java:74)
at org.springframework.web.socket.handler.ExceptionWebSocketHandlerDecorator.afterConnectionClosed(ExceptionWebSocketHandlerDecorator.java:89)
at org.springframework.web.socket.sockjs.transport.session.AbstractSockJsSession.close(AbstractSockJsSession.java:234)
at org.springframework.web.socket.messaging.StompSubProtocolHandler.handleMessageToClient(StompSubProtocolHandler.java:208)
at org.springframework.web.socket.messaging.SubProtocolWebSocketHandler.handleMessage(SubProtocolWebSocketHandler.java:252)
at org.springframework.messaging.support.ExecutorSubscribableChannel$1.run(ExecutorSubscribableChannel.java:70)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)

Feb 17, 2014 5:56:38 PM reactor.tcp.netty.NettyTcpClient$4$1 operationComplete
Information: CLOSED: [id: 0xa3023e5e, /127.0.0.1:51969 :> /127.0.0.1:61613]

Maybe you have an idea how to solve that problem.

With Regards

Ogniute

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

1 participant