850_update_bulletin - Progress Sonic Product Update Bulletin 8.5

What’s New in SonicMQ and Management Framework
● “Added functionality in C and C++ Clients” on page 57
● “Container log records CPU/Core Count, and ProcessID” on page 58
● “Advanced Broker Property To Check for Oversized Messages” on page 58
● “Administered Objects Tool Enables Use of Sub-contexts” on page 58
● “Enhanced Documentation: Quality of Protection settings” on page 59
● “Enhanced Documentation: Running Sonic as a Linux service” on page 59
● “Cluster-level Flow-to-disk Parameter” on page 60
● “Named Sessions” on page 60
Routing Connection (DRA) Flow Control Notifications
A routing connection provides a way for an application to dynamically route a message
through a connected broker to a destination on another broker. As the brokers involved in
a DRA routing connection could be in different management domains, the point of view
of an administrator in one of those domains will be constrained.
Flow control notifications for dynamic routing are similar in concept to cluster flow
control notifications. The outgoing side of the routing connection is monitored once per
configured interval to check whether it is flow controlled. A connection is flow-controlled
if it has messages to send, but is unable to send them because it has received a directive
from its peer to limit sending. It can only send messages higher than a certain priority
(Pub/Sub flow control) or messages that are not for blocked destinations (PTP flow
control). If the connection has been flow-controlled for a whole monitor interval, a flow
control ‘pause’ notification will be sent. Notifications will be sent once per monitor
interval as long as the connection remains flow controlled.
A resume notification is sent when the connection receives a directive to resume sending.
While the ‘pause’ notification combines pubsub and ptp data into a single notification,
resume notifications are sent when the individual resume event occurs.
To provide the data for a notification, the sending connection identifies that it is flow
controlled and the receiving broker supplies the details about blocking resources. The
receiving broker sends the notification. When brokers are in the same management
domain, the notifications are visible to administrators of both brokers.
However, for routing connections, sending broker and the receiving broker are often in
different management domains. A notification produced by the receiving broker’s domain
may not be visible in the sending broker’s domain. Furthermore, data from the receiving
broker about blocking resources (subscribers) is not meaningful in the sending broker’s
domain, and exposing the information would present a security violation. Even without
Progress Sonic Update Bulletin 8.5 51