Skip to main content
Version: Release 25.1

Switching From MQ To Simple Event Publisher

In Release 25.1.x, JMS remains the default event publisher. You can, however, configure Release to use the simple event publisher, which stores webhook events directly in the database and removes the need for an external message broker.

The simple event publisher dispatches webhook events directly without requiring a message broker, which reduces deployment complexity and operational overhead.

note

Starting in Release 25.3, JMS support has been removed and only the simple event publisher is available. See External Queue Dependency Removal.

Step 1 - Disable MQ Configuration In The Custom Resource​

Depending on your setup, update the Custom Resource (dai-release_cr.yaml):

If you previously used an external MQ:

external:
  mq:
    enabled: false

If you previously installed the embedded RabbitMQ:

rabbitmq:
  install: false

Step 2 - Apply The Updated Custom Resource​

For more information, see Apply Changes from Custom Resource.

info

The MQ pod will no longer be available after this step.

Step 3 - Update The Release Configuration​

For more information about how to update Release configuration, see Customize Release Configuration.

Edit the xl-release.conf.template file to remove or comment out any JMS or RabbitMQ queue configuration, then specify the simple queue type.

  1. Remove the following configuration: 
    # Task queue
    queue {
        embedded=true
        connector="rabbitmq-jms"
        password="""mqadmin"""
        queueName="xlr-tasks-queue"
        url="amqp://localhost:61616"
        username="mqadmin"
        queueType="classic"
    }
  2. Add the following configuration: 
    queue {
        type="simple"
    }

Step 4 - Apply Configuration Changes​

After modifying the xl-release.conf.template file, patch the Release Custom Resource so the Operator applies your configuration changes.

Follow the steps in Customize Release Configuration to update the .spec.configuration.default-conf_xl-release-conf-template.content field.

The Operator will reconcile and restart the Release pods with the new configuration.