Closed darshanmehta10 closed 8 years ago
This has nothing to do with the sample here.
I'm not going to answer any further questions here but in case you post elsewhere keep in mind you've too many open questions or inaccuracies in your report:
Client goes into re-connection loop
Re-connection is not built-in so you have to explain what's trying to reconnect and show some evidence if needed.
com.rabbitmq.client.ConnectionFactory
Spring WebSocket does not use the RabbitMQ client so this part seems irrelevant.
Spring boot (Jetty) needs to keep HTTP Session alive if Websocket session is active.
From the stacktrace this looks like a SockJS (HTTP transport) and not an actual WebSocket connection.
Spring boot : 1.2.7
You should upgrade to 1.2.8 at least.
RabbitMQ : 3.6.0 Spring WebSocket : 4.1.8 Spring boot : 1.2.7
Snippet of client code:
This tries to connect to an existing queue (durable subscription), it gets connected initially, however, after 5 seconds, the connection drops and following gets printed:
Server logs show the following:
And then, this gets logged repeatedly:
Client goes into re-connection loop and no message is retrieved. It seems the HTTP Session gets closed even if Websocket connection is active.
I have tried tweaking the following parameters:
However, session still keeps getting closed. Spring boot (Jetty) needs to keep HTTP Session alive if Websocket session is active.