Exception in "inboundClientChannel" interceptor for DISCONNECT prevents broker from learning about it [SPR-12218]

[spring-projects-issues]

Rob Winch opened SPR-12218 and commented

If an exception is thrown in ChannelInterceptor.preSend on DISCONNECT, then the following error is reported when sending to destinations a user has subscribed:

SubProtocolWebSocketHandler[ERROR] - No session for ...

Even if an Exception is thrown in ChannelInterceptor.preSend on DISCONNECT the user mapping should be cleaned up. One option to clean this up would be to use a ApplicationListener<SessionDisconnectEvent>

---

Affects: 4.1 GA

Referenced from: commits ceb79c9, 371d93b

1 votes, 3 watchers

[spring-projects-issues]

Rossen Stoyanchev commented

The issue mainly affects the simple broker which does not have a heartbeat and must see the DISCONNECT message. A full features broker supports heartbeats and will notice withing a short period that the client is no longer sending messages and will close the connection.