Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 10 Managing Rendezvous Client Queues : Configuring Client Queues

Configuring Client Queues
To configure egress client message queues or the TCP transmit queues on P-7500 systems, you enter the Client Profile CONFIG level for a named profile. The only client profile currently supported is named default.
Next, you enter queue type at the Client Profile CONFIG level to move to the Client Profile Queue CONFIG level, where type is the queue type to be configured. The only queue type currently supported is egress. Here is an example:
tibco(config)# client-profile default
tibco(config-client-profile)# queue egress
tibco(config-client-profile-queue)#
Now you are at a level where you can configure parameters for the egress queue of the default client profile. You can set the maximum queue depth and minimum burst length tolerance for the per-client message queues.
Note: For more information on clients and client profiles, refer to Chapter 2, Managing TIBCO Rendezvous Tasks.
max-depth
Each per-client message queue has an associated maximum depth. The depths are measured in work units, each work unit representing 2048 bytes of a message. The formula to convert a message size to number of work units is:
NumWorkUnits = CEILING(message.length/2048)
Before a new message is placed on the message queue, its depth in work units is checked against the maximum depth set for the queue. If the current depth is less than the maximum, the message is placed on the queue regardless of the number of work units that the message needs, even if it causes the queue to exceed its maximum depth.
Messages that are received when the depth is greater or equal to the maximum are discarded, and also get counted as a Transmit Congestion--Slow Consumer dataplane statistic.
To configure the maximum depth of the specified queue, enter:
tibco(config-client-profile-queue)# max-depth depth
where depth is the integer value representing the queue depth in KB for the number of work units for the client message queues. Valid range is 50 to 262144 for client message queues. Default is 100000 work units for the client message queues. Changing this value does not affect messages already successfully placed on the queue.
Note: The no version of this command (no max-depth) resets the queue depth to the default of 100000 work units.
min-msg-burst
Minimum burst length tolerance is used to ensure that messages are not lost when bursts of very large messages are received on a client egress queue. It specifies the number of messages per queue that are always allowed, regardless of the queue’s current maximum depth setting.
For example, in a case where there are three messages currently on a queue, and the minimum burst length tolerance of the queue is set to 4, one more message is allowed to be placed on the queue, regardless of whether the three current messages have filled the queue past its maximum depth. The minimum burst length tolerance setting of 4 allows the queue to temporarily exceed its maximum depth by always allowing the 4th message to be placed on the queue, regardless of its current depth and maximum depth setting.
To configure the minimum number of messages that must be on a client message queue before the queue’s depth is checked against the maximum depth setting, enter:
tibco(config-client-profile-queue)# min-msg-burst depth
where depth is the integer value representing the queue burst depth in messages. Valid range is 0 to 262144. The default is 4. Changing this value does not affect messages already successfully placed on the queue.
The no version of this command (no min-msg-burst) resets the minimum burst length tolerance in messages to the default of 4.
 

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved