rabbitmq_delayed_message_exchange plugin issue #13789
-
Community Support Policy
RabbitMQ version used4.0.3 Erlang version used26.2.x Operating system (distribution) usedlinux How is RabbitMQ deployed?Community Docker image rabbitmq-diagnostics status outputSee https://www.rabbitmq.com/docs/cli to learn how to use rabbitmq-diagnostics
Logs from node 1 (with sensitive values edited out)See https://www.rabbitmq.com/docs/logging to learn how to collect logs
Logs from node 2 (if applicable, with sensitive values edited out)See https://www.rabbitmq.com/docs/logging to learn how to collect logs
Logs from node 3 (if applicable, with sensitive values edited out)See https://www.rabbitmq.com/docs/logging to learn how to collect logs
rabbitmq.confSee https://www.rabbitmq.com/docs/configure#config-location to learn how to find rabbitmq.conf file location
Steps to deploy RabbitMQ clusterNA Steps to reproduce the behavior in questionNA advanced.configSee https://www.rabbitmq.com/docs/configure#config-location to learn how to find advanced.config file location
Application code# PASTE CODE HERE, BETWEEN BACKTICKS Kubernetes deployment file# Relevant parts of K8S deployment that demonstrate how RabbitMQ is deployed
# PASTE YAML HERE, BETWEEN BACKTICKS What problem are you trying to solve?We have successfully installed the rabbitmq_delayed_message_exchange plugin; however, it does not appear in the Exchange Type dropdown from Console UI page. That said, the plugin is listed as installed when we run the rabbitmq-plugins list command. Could you please help us understand why it's not visible in the dropdown?[Questions] |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
@bsanthanam-equinix you must enable the plugin, not just put it into the plugins directory with sufficient permissions for the node to load it. The README mentions that. While at it, please move to RabbitMQ |
Beta Was this translation helpful? Give feedback.
@bsanthanam-equinix you must enable the plugin, not just put it into the plugins directory with sufficient permissions for the node to load it.
The README mentions that.
While at it, please move to RabbitMQ
4.1.0
or at the very least4.0.9
and the plugin release for those respective versions.