RabbitMQ server is sending Connection.Unkown method to the client

[poducavanje]

RabbitMQ server 3.2.0 (but reproducible with 3.2.2 also). Will try to update the ticket if I have chance to try with 3.2.3 but not yet sure. Change log for 3.2.3 is not saying anything related to this issue

Steps:
1.Have MQ hit the Memory or HDD alarm (for example, publish enough persistent messages to the queue so free disk space falls below 50 MB with default MQ settings). Expecting here is to have RabbitMQ blocking further publishing and sending blocking notification to clients
2. Try to publish additional messages to MQ

Expected:
Rabbit should notify clients with proper connection method, id should be 50 (according to docs 60 is renumbered to 50)

Actual:
Rabbit is still sending id 60 as you can see from attached wireshark traces

Note: please contact me by e-mail if you'll need some more info on the issue

[michaelklishin]

This is not connection.unknown but connection.blocked, a RabbitMQ extension to AMQP 0-9-1 which Wireshark dissector is unaware of. Your client should support it (at least it indicates so in capabilities), otherwise RabbitMQ would not send it.

[michaelklishin]

class = 10, id = 50 is connection.close. To quote AMQP 0-9-1 JSON file in rabbitmq-codegen:

{"id": 60,
                 "arguments": [{"type": "shortstr", "name": "reason", "default-value": ""}],
                 "name": "blocked"},
                {"id": 61,
                 "arguments": [],
                 "name": "unblocked"}

[poducavanje]

Hi Michael,

Thanks for pointing this out. This will narrow down our effort to trace the problem on the client side only.
Appreciate the info you provided

Cheers,
Nemanja

[poducavanje]

And thanks for quick response too!