[rabbitmq-discuss] A different Processing error in logs
steve at rabbitmq.com
Wed Dec 7 12:27:28 GMT 2011
Thank you for that description. I will attempt to reproduce this locally. At
first glance it appears that the reception of messages after UNSUBSCRIBE is
counter-intuitive, and the interference with the second queue sounds suspicious.
Could we see some of your code, please, or could you break this down into a
series of STOMP frames, so we can see what the parameters are? A trace of the
STOMP frames would be best of all.
Are the subscriber and sender the same process?
Can you say exactly what type of queue you create/subscribe to?
In 2) is it necessary to SEND more than 2 messages?
In 3) how do you manage the connection when you stop reading it to unsubscribe?
Do you need to unsubscribe before ack to get the problem in 6?
In 6) is the SEND from the same process again?
If possible, a failing code sample would be helpful.
One of the trials I would perform is to try sending on queue 2 after every
interaction with queue 1. Of course, that may make it necessary to field
messages from the second subscription at the same time.
I'll keep you informed about my progress.
Steve Powell (a working bunny)
----------some more definitions from the SPD----------
avoirdupois (phr.) 'Would you like peas with that?'
distribute (v.) To denigrate an award ceremony.
definite (phr.) 'It's hard of hearing, I think.'
modest (n.) The most mod.
On 7 Dec 2011, at 01:32, Toby Corkindale wrote:
> This feels like a RabbitMQ or STOMP bug to me, but here's some more info on
> what causes it to occur so you can decide.
> 1) Create two queues, with ack=client, subscribe to both, using STOMP.
> 2) Dump a bunch of messages into first queue.
> 3) Upon receiving one message, unsubscribe from the first queue only, and
> then ack the message.
> 4) Note that you still get delivered some more messages from that first
> 5) Attempt to send a client ACK back for one of these messages, which seems
> to work fine.
> 6) Now attempt to send another message through on the second
> (still-subscribed) queue -- rabbitmq generates the Processing Error.
More information about the rabbitmq-discuss