Skip to content

Control the number of retries and delay message in case of error

This sample demonstrates how the WSO2 Micro Integrator can guarantee message delivery to an endpoint by controling the number of delivery retries during errors. You can also configure a delay in message delivery from the RabbitMQ broker.

  1. The Micro Integrator first consumes a message from RabbitMQ and attempts to deliver it to the endpoint.
  2. When there is an error in delivery, the SET_ROLLBACK_ONLY property in the Micro Integrator moves the message to the dead letter exchange (DLX) configured in RabbitMQ.
  3. The message will then be re-queued by RabbitMQ subject to a specified delay. Note that you have to configure this delay in the RabbitMQ broker itself (using the x-message-ttl property).
  4. If the message delivery to the endpoint continuous to fail, the Micro Integrator will retry for the number times specified by the rabbitmq.message.max.dead.lettered.count parameter in the proxy.
  5. When the maximum retry count is exceeded, the message will be either discarded or moved to a different queue in RabbitMQ (specified by the and rabbitmq.message.error.queue.routing.key parameters in the proxy.

Synapse configurations

See the instructions on how to build and run this example.

<?xml version="1.0" encoding="UTF-8"?>
<proxy xmlns=""
      <log level="custom">
          <property expression="$body" name="Message Received"/>
      <call blocking="true">
            <http uri-template="http://localhost:8280/enrollment"/>
      <log level="custom">
          <property name="Status" value="The message process successfully"/>
      <log level="custom">
          <property name="Status" value="Could not process the message"/>
      <property name="SET_ROLLBACK_ONLY" scope="axis2" value="true"/>
   <parameter name="rabbitmq.queue.autodeclare">false</parameter>
   <parameter name="rabbitmq.message.max.dead.lettered.count">3</parameter>
   <parameter name="">enrollment-exchange</parameter>
   <parameter name="">false</parameter>
   <parameter name="">enrollment</parameter>
   <parameter name="rabbitmq.queue.autodeclare">false</parameter>
   <parameter name="rabbitmq.connection.factory">AMQPConnectionFactory</parameter>

Build and run

  1. Make sure you have a RabbitMQ broker instance running.
  2. Declare exchange to route enrollment

    rabbitmqadmin declare exchange --vhost=/ --user=guest --password=guest name=enrollment-exchange type=direct durable=true

  3. Declare a queue to store enrollment. At the same time define DLX, DLK to control the error scenario.

    rabbitmqadmin declare queue --vhost=/ --user=guest --password=guest name=enrollment durable=true arguments='{"x-dead-letter-exchange": "enrollment-error-exchange", "x-dead-letter-routing-key": "enrollment-error"}'

  4. Bind enrollment with enrollment-exchange.

    rabbitmqadmin declare binding --vhost=/ --user=guest --password=guest source=enrollment-exchange destination=enrollment routing_key=enrollment

  5. Declare exchange to route enrollment-error.

    rabbitmqadmin declare exchange --vhost=/ --user=guest --password=guest name=enrollment-error-exchange type=direct durable=true

  6. Declare queue to store enrollment-error. Define DLX, DLK and TTL for control retries and delay message.

    rabbitmqadmin declare queue --vhost=/ --user=guest --password=guest name=enrollment-error durable=true arguments='{"x-dead-letter-exchange": "enrollment-exchange", "x-dead-letter-routing-key": "enrollment", "x-message-ttl": 60000}'

  7. Bind enrollment-error with enrollment-error-exchange.

    rabbitmqadmin declare binding --vhost=/ --user=guest --password=guest source=enrollment-error-exchange destination=enrollment-error routing_key=enrollment-error

  8. Set up WSO2 Integration Studio.

  9. Create an integration project with an ESB Configs module and an Composite Exporter.
  10. Create the proxy service with the configurations given above.
  11. Enable the RabbitMQ sender and receiver in the Micro-Integrator from the deployment.toml. Refer the configuring RabbitMQ documentation for more information.
  12. Deploy the artifacts in your Micro Integrator.
  13. Make the http://localhost:8280/enrollment endpoint unavailable temporarily.
  14. Publish a message to the enrollment queue.
  15. You will see that the failed message will be retried 3 times for delivery by the EnrollmentService proxy and then be discarded.