Custom Jetty WebSocketPolicy with Spring6 / Spring Boot 3 Web Sockets
In older versions of Spring, a custom policy could be applied by doing the following:
Spring Boot 3.3.0 Websocket Server StompEndpointRegistry preserveReceiveOrder ConcurrentModificationException
Prior to spring boot 3.2.x I was able to “preserve receive order” by configuring the ClientInboundChannel of the WebSocket server with a single thread (not a scalable solution). I noticed that this technique stopped working with 3.2.x and 3.3.x and that the StompEndpointRegistry.preserveReceiveOrder property is now available.