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
Sergi Almar opened SPR-11599 and commented
The STOMP specification mentions that in order to do a graceful shutdown, the client should send a
DISCONNECTframe, wait for aRECEIPTframe and close the socket.Currently, after sending a
DISCONNECTnoRECEIPTframe is received. RabbitMQ does send theRECEIPTframe on disconnect but it's not recevied on the client side.Take also into account connection lingering
Additionally, the
DISCONNECTframe should come with areceiptheader, but stomp.js doesn't support passing headers on the disconnect method. Open issue here.Affects: 4.0.2
Referenced from: commits 7da3fb4