The channel was closed: AMQP close-reason code=503, text='COMMAND_INVALID

[attiqeurrehman]

Hi,

We are using the plugin with masstransit and we are experiencing weird behavior even with plugin enabled we are unable to use it and getting the following error:

The channel was closed: AMQP close-reason, initiated by Peer, code=503, text='COMMAND_INVALID - unknown exchange type 'x-delayed-message'', classId=40, methodId=10 9

[lukebakken]

Hello, thanks for using RabbitMQ.

Unfortunately, there is very little information to work with here. Some questions:

• What is your Erlang version?
• What operating system and version are you using?
• How EXACTLY did you download and install this plugin?
• How EXACTLY did you enable this plugin?

[gomoripeti]

In the output of rabbitmq-plugins list usually there is a * after the E or e that indicates the enabled plugin is running. This suggests me that the cli can access the enabled plugins file but either cannot access the running broker or the plugins are not running. (ie something is fishy) Answering the questions of lukebakken might shed some light on what could be wrong.

[attiqeurrehman]

Hi,

Sorry for missing out on the information, here you go:

What is your Erlang version? 25.2.1
What operating system and version are you using? Windows Server 2019
How EXACTLY did you download and install this plugin?
Plugin was downloaded from here
How EXACTLY did you enable this plugin?
Copied in the plugin folder, ran the command rabbitmq-plugins enable rabbitmq_delayed_message_exchange
and it showed the above status in the question.