Wierd behaviour of QOS=2 with RabbitMQ

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Select detailed perspective
2. Send a message with QOS=2 to RabbitMQ
3. Watch it disconnect!

What is the expected output? What do you see instead?
I would expect, if I am subscribed to the message I send, to see it come back, 
instead the MQTT-spy momentarily disconnects from the server-  the message 
never goes anywhere.

What version of the product are you using? On what operating system?
Latest of just a couple of days ago - on a Windows 7 PC. MQTT works beautifully 
otherwise.

Please provide any additional information below.
On another tab talking to MOSQUITTO the unit does not disconnect - but QOS=2 
appears to have no effect - just seems to act like QOS=0. I'd assumed that the 
message would get through even if the subscription came through after the 
message was sent. Could be me - could be RabbitMQ but I thought I'd better 
bring this to your attention.

Original issue reported on code.google.com by petersca...@googlemail.com on 1 Jan 2015 at 6:29

[GoogleCodeExporter]

Many thanks for raising this. Any chance you could check if there is anything 
in the diagnostic log (mqtt-spy.log or similar)?

Original comment by kamil.ba...@gmail.com on 2 Jan 2015 at 9:46

[GoogleCodeExporter]

I tried this with mosquitto and it seems OK.

Original comment by kamil.ba...@gmail.com on 3 Jan 2015 at 8:35

• Changed title: Wierd behaviour of QOS=2 with RabbitMQ

[GoogleCodeExporter]

As reported by Pete, it turns out this is an issue with RabbitMQ.

Original comment by kamil.ba...@gmail.com on 7 Jan 2015 at 2:58

• Changed state: Invalid