Investigate possibility of SockJS without sticky sessions [SPR-12936]

Johan Frick opened SPR-12936 and commented

(This was posted on Stackoverflow as well, before we realized that you had a Jira. Let us know if you want us to remove it from Stackoverflow.)

We are trying to use spring-websocket with STOMP using SockJS as a fallback option. We have based our solution on this guide: https://spring.io/guides/gs/messaging-stomp-websocket/.

The environment is running multiple tomcats without sticky session.

The problem we have run into is that it is not possible to use the fallback from websocket due to the xhr requests ending up on separate tomcats where the original session does not exist, causing it to retry with a websocket connection and it will continue in this loop.

Is there a preferred way of solving this issue?

We were hoping that spring-session would be an answer but it does not seem to help in this case.

Affects: 4.1.5

Reference URL: http://stackoverflow.com/questions/29743065/spring-websocket-with-fallback-over-load-balancer

Issue Links:

• #16243 Support user destinations with multiple WebSocket servers

0 votes, 8 watchers

No source file or test is named. Start by investigating spring-websocket's SockJS fallback and session handling across multiple Tomcats without sticky sessions, then review the spring-session context and linked issue #16243. Done means establishing whether this deployment is supported and documenting the preferred solution or the required change.