Connection to STOMP broker closed after a few successful messages are read [SPR-11088]

[spring-projects-issues]

Rossen Stoyanchev opened SPR-11088 and commented

StompDecoder is throwing a variety of exceptions after having successfully read a few messages from an external message broker. All cases seem to point to not having any more data read from the input ByteBuffer while the message hasn't yet been fully received.

For example it may fail to read a STOMP header like this:

org.springframework.messaging.simp.stomp.StompConversionException: Illegal header: 'content-leng'. A header must be of the form <name>:<value>\n

Or it may succeed to read the headers but fail to read the STOMP message payload with a BufferUnderflowException (if there is a content-length header) or "Frame must be terminated with a null octet" if there is no content-length header and it was expecting a '0' byte.

---

Affects: 4.0 RC1

Referenced from: commits e84885c, 6802f81