Rabbitmq_delayed_message_exchange Plugin Download

0 views

Skip to first unread message

Sylvia Heidemann

unread,

Jan 3, 2024, 7:18:52 AM1/3/24

to dhonchimderi

Binary downloads of plugins, which are contributed by authors in thecommunity are available. These plugins do not ship with the RabbitMQserver. Refer to Installing Additional Plugins for information on how to install the plugins. Note, the latestbuild of the plugin is compiled against the latest feature release of RabbitMQ.

I deployed a rabbitmq instance using the rabbitmq operator in kubernetes. And I'm trying to enable the rabbitmq plugin: rabbitmq_delayed_message_exchange.

rabbitmq_delayed_message_exchange plugin download

Download File https://onsowinmu.blogspot.com/?um=2x1PLF

Notice: For immutable results or in case you can't depend on external changes, download the plugin to your machine and use COPY instead of using RUN curl... Make sure to have the rabbitmq_delayed_message_exchange .ez file in your machine.

I have a RabbitMQ hosted in Amazon MQ, but im finding it difficult to find any documentation or guides to how to install this plugin -delayed-message-exchange/. In the documentation it does not state how to remotely(Since Amazon MQ does not allow direct CLI access). I tried this command: rabbitmqadmin --base-uri=@url --vhost=/ --ssl --username=@user --password=@pass rabbitmq-plugins enable rabbitmq_delayed_message_exchange

At -plugins.html, select rabbitmq-delayed-message-exchange and download the rabbitmq-delayed-message-exchange-.ez file. Place the rabbitmq-delayed-message-exchange-.ez file in the /usr/lib/rabbitmq/plugins directory.

For a while people have looked for ways of implementing delayedmessaging with RabbitMQ. So far the accepted solution was to use a mixof message TTL andDead Letter Exchanges as proposedby James Carrhere. Sincea while we have thought to offer an out-of-the-box solution for this,and these past month we had the time to implement it as aplugin. EnterRabbitMQ Delayed Message Plugin.

Once we receive a message on the consumer side, how can we tell if themessage was delayed or not? The plugin will keep the x-delay messageheader, but will negate the passed value. So if you published amessage with a 5000 milliseconds delay, the consumer receiving saidmessage will find the x-delay header set to -5000

FWIW we finally made this work - the issue is that the management plugin listens to IPv4 only by default, so was unreachable via IPv6. Adding management.tcp.ip = :: to the RabbitMQ configuration gets everything working as intended.