Allow server-side code to send DISCONNECT messages to the broker [SPR-12288]

[spring-projects-issues]

Rob Winch opened SPR-12288 and commented

Spring Session needs the ability to disconnect a client from code on the server side (i.e. from a ChannelInterceptorAdapter) when a session expires. Ideally the solution will not require using STOMP specific APIs.

---

Affects: 4.1.1

Issue Links:

• Allow access to underlying WebSocketSession with WebSocketMessageBroker config [SPR-12314] #16919 Allow access to underlying WebSocketSession with WebSocketMessageBroker config
• StompSubProtocolHandler responds with ERROR (Session closed.) on DISCONNECT when using SimpleBrokerMessageHandler [SPR-14568] #19137 StompSubProtocolHandler responds with ERROR (Session closed.) on DISCONNECT when using SimpleBrokerMessageHandler

Referenced from: commits 01aa64c

0 votes, 6 watchers

[spring-projects-issues]

Rob Winch commented

Note that now that #16919 is resolved I am now able to perform disconnects necessary for Spring Session since I have a mapping of the HttpSession id to the WebSocketSession. This means in regards to Spring Session support this is not necessary for us to proceed at this point.

[spring-projects-issues]

Rossen Stoyanchev commented

I was wondering the same. That said I'll leave this open. Currently it works with the broker relay but should also work with the simple broker.