When flow control is enabled with a multicast channel, is there a particular (hard-coded) size that the message backlog needs to reach before flow control will be engaged?

When flow control is enabled with a multicast channel, is there a particular (hard-coded) size that the message backlog needs to reach before flow control will be engaged?

book

Article ID: KB0084745

calendar_today

Updated On:

Products Versions
TIBCO Enterprise Message Service -
Not Applicable -

Description

Resolution:
Description:
============  
Flow control is driven by the maxrate property of a multicast channel and the presence of a backlog due to maxrate exceeding, rather than a backlog size, enforces the flow control property.

A backlog of messages start to accumulate when the specified value for maxrate of a multicast channel has been reached. With flow_control enabled, the EMS server will check for the existence of a backlog before sending a response to message producers who are publishing to multicast-enabled topics. When a backlog exists, a delay is introduced by the server in sending this response back to messages producers, and in turn decreasing the rate at which the producers publish to the topic.

When the maxrate has been exceeded, we need a place to store the messages - hence the backlog is used. The backlog should remain small when flow control is enabled. It can grow large when flow control is disabled.

Environment:
==========  
Al

Issue/Introduction

When flow control is enabled with a multicast channel, is there a particular (hard-coded) size that the message backlog needs to reach before flow control will be engaged?