Consultor Eletrônico

SUMMARY:

This Solution applies to the Dynamic Routing Architecture (DRA), a feature of SonicMQ Point-to-point domains since version 3.0. It explains what happens in the dynamic routing queue when messages are sent to a remote node that is unavailable.

EXPLANATION:

SonicMQ's Dynamic Routing Architecture allows messages to be routed through a local SonicMQ broker to a remote SonicMQ broker.
For the clients connected to the local broker, the remote destination appears to be local yet is sent through the system queue, SonicMQ.routingQueue, to get qualified by the routing table as a valid remote destination.

This discussion centers around the handling of messages in the SonicMQ.routingQueue when several remote nodes are message destinations but one or more remote node are not accessible.

SOLUTION:

When a remote node (the remote SonicMQ broker) is not available, the
messages with destinations on the unavailable remote node stay in the
SonicMQ.routingQueue. Messages for destinations on active remote nodes are routed normally and without delay.

As with all queues, the SonicMQ.routingQueue is configured to a specific size and should be large enough to handle the accumulated unexpired message volume such an incident might cause. Once the remote node is again available, the messages for queues on that node are routed normally.


References to Written Documentation:

SonicMQ V4 Deployment Guide, Chapter 10, "Implementing Multi-node Installations"

SonicMQ V4 Programming Guide, Chapter 7, "Dynamic Routing Architecture"

SonicMQ V4 Configuration and Administration Guide, Chapter 9, "Routing"