[rabbitmq-discuss] message via stomp adapter crashes queue

Rob Harrop rob at rabbitmq.com
Fri Jun 17 09:42:02 BST 2011

Hi Chris,

This is what you see against 2.1?

The bug you linked to is not present in 2.1, it was introduced in 2.2 
but is fixed since 2.4.1 (or maybe 2.4.0).

The log doesn't seem to be saying anything interesting about queues 
crashing, simply that the parser thinks the incoming frame is corrupted. 
In particular, it looks like the header key has a newline in it, which 
is definitely not allowed.

Do you have a few sample frames that you could send me.

The best solution to this is to find out why you can't run against 
2.5.0. The parser was much updated to support STOMP 1.1 recently and to 
handle some clarifications around handling of extraneous newlines and such.


Chris wrote:
> Thank you for the response Rob.
> Not sure exactly, but I know that if we move past 2.1.0 and the
> matching stomp plugin things get worse. I'm just the guy that has to
> keep this thing running and not the developer of the stomp client
> pushing data at the rabbit stomp adapter or the clients on the other
> side doing amqp. I'll try again to get the details on what's keeping
> us stuck at this version.
> In the meantime this is what we see when the Queue goes away:
> 10:49< arreyder> =ERROR REPORT==== 15-Jun-2011::15:46:12 ===
> 10:49< arreyder> STOMP error frame sent:
> 10:49< arreyder> Message: "Invalid frame"
> 10:49< arreyder> Detail: "Could not parse frame\n"
> 10:49< arreyder> Server private detail:
> {bad_header_key,"destinaSEND"}
> 10:49< arreyder> "detinaSEND"
> 10:51< arreyder> here's the one from just before that one:
> 10:51< arreyder> =ERROR REPORT==== 15-Jun-2011::15:31:11 ===
> 10:51< arreyder> STOMP error frame sent:
> 10:51< arreyder> Message: "Invalid frame"
> 10:51< arreyder> Detail: "Could not parse frame\n"
> 10:51< arreyder> Server private detail:
> {bad_header_key,"destinationSEND"}
> I've verified on the wire (packet captures) that the message headers
> do not look like how they are logged there. They appear correctly
> sent.
> crr
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list