[rabbitmq-discuss] message via stomp adapter crashes queue

[Chris]

>
> I'm particularly interested in knowing if there is something in the
> latest version of the adapter that is preventing you from moving. Fixing
> that will be a lot easier than backporting a fix to the pre-2.1.0 era code.
>
> Rob

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