Support RECEIPT frame on disconnect [SPR-11599]

[spring-projects-issues]

Sergi Almar opened SPR-11599 and commented

The STOMP specification mentions that in order to do a graceful shutdown, the client should send a DISCONNECT frame, wait for a RECEIPT frame and close the socket.

Currently, after sending a DISCONNECT no RECEIPT frame is received. RabbitMQ does send the RECEIPT frame on disconnect but it's not recevied on the client side.

Take also into account connection lingering

Additionally, the DISCONNECT frame should come with a receipt header, but stomp.js doesn't support passing headers on the disconnect method. Open issue here.

---

Affects: 4.0.2

Referenced from: commits 7da3fb4

[spring-projects-issues]

Rossen Stoyanchev commented

This should be fixed now. Theoretically you can get a RECEIPT frame back for a DISCONNECT. I say theoretically because despite this fix in stomp.js that allows sending headers on a disconnect, the client still closes the connection immediately after the DISCONNECT is sent so it won't let you wait for the receipt.

[KaisNeffati]

Hello there ! I am always unable to pass headers to the stompsession disconnect event on spring-websocket-5.1.3! Is there any solution for this issue please !! Thanks