Skip to content

RabbitMQ Setup

Enable Management Plugin

To enable the RabbitMQ management plugin, run the following command:

rabbitmq-plugins enable rabbitmq_management

You can execute this command either in the RabbitMQ Command Prompt (installed with RabbitMQ) or in any command prompt/PowerShell window if RabbitMQ's sbin directory has been added to the PATH environment variable.

Troubleshooting: Command Not Found

If the rabbitmq-plugins command is not found, navigate to the RabbitMQ installation directory and execute the script directly:

  1. Navigate to the RabbitMQ installation path (typically: C:\Program Files\RabbitMQ Server\rabbitmq_server-<VERSION>\sbin)
  2. Execute the script directly:
.\rabbitmq-plugins.bat enable rabbitmq_management

After enabling the management plugin, restart the RabbitMQ service to ensure the changes take effect.

Port Configuration

To change the default ports used by RabbitMQ, you need to modify the configuration file.

Locate Configuration Directory

Navigate to the RabbitMQ configuration directory. The location depends on whether RabbitMQ was installed for the current user or system-wide:

  • User installation: C:\Users\<YOUR_USER>\AppData\Roaming\RabbitMQ\rabbitmq.conf
  • System-wide installation: C:\ProgramData\RabbitMQ\rabbitmq.conf

Edit Configuration File

Open or create the rabbitmq.conf file and add the following settings:

To change the AMQP port:

listeners.tcp.default = 5673

To change the Management UI port:

management.listener.port = 15673

After modifying the configuration, restart the RabbitMQ service for the changes to take effect.

Log Configuration

RabbitMQ's logging behavior can also be configured in the rabbitmq.conf file described above.

Setting Parameter
File log.file
Log level log.file.level
Max size log.file.rotation.size
Max number of files log.file.rotation.count
Compress rotated files log.file.rotation.compress

Example:

log.file = rabbit.log
log.file.level = info
log.file.rotation.size = 10485760
log.file.rotation.count = 5
log.file.rotation.compress = true
  • log.file.level controls the verbosity of the log file and accepts debug, info, warning, error, critical, or none.
  • log.file.rotation.size is specified in bytes (the example above rotates at 10 MB).

After modifying the configuration, restart the RabbitMQ service for the changes to take effect.

Troubleshooting: Licensing Service Fails to Start on RabbitMQ 4.0+

RabbitMQ 4.0 and later reject the declaration of a queue with durable=false, exclusive=false, and autoDelete=false, since this combination (the deprecated transient_nonexcl_queues feature) is being phased out. On versions prior to v3.1.1, this can cause the GC.Licensing service to fail on startup against a RabbitMQ 4.0+ server.

Fixed in v3.1.1

This issue is resolved starting with version 3.1.1, which uses a compatible queue declaration and automatically migrates any pre-existing queue created with the old settings. Upgrading is the recommended solution — see the v3.1.1 Release Notes.

Temporary Workaround

If upgrading is not immediately possible and you administer the RabbitMQ server, you can re-permit the deprecated feature to buy time until you upgrade:

  1. Open (or create) the rabbitmq.conf file as described above.
  2. Add the following line:
deprecated_features.permit.transient_nonexcl_queues = true
  1. Restart the RabbitMQ service for the change to take effect.

Workaround Only

This setting only postpones the problem. The transient_nonexcl_queues feature is deprecated and will be removed entirely in a future RabbitMQ version, at which point this workaround will no longer be effective. Upgrade to GroundControl VGRS v3.1.1 or later as soon as possible.