

For queues, maxbytes defines the maximum size that the queue can store. We can specify maxbytes in the same format as flowControl. i.e this property is required only if we are routing the message to another EMS server. Messages destined for a topic or queue with the global property set are routed to the other servers that are participating in routing with this server. We can set the size in KB, MB or GB. The flow_control parameter in nf file must be set to enabled before the value in this property is enforced by the server. The best part of flowControl is that it never discards messages or generates errors back to the producer. If the size exceeds the maximum, the server will slow down the producers to the rate required by the message consumers. The flowControl property specifies the maximum size of pending messages for the destination. When a message expires it is either destroyed or if the JMS_TIBCO_PRESERVE_UNDELIVERED property on the message is set to true, the message is placed on the undelivered queue so it can be handled by a special consumer. We can set the expiration property for any queue and any topic using below command. Also, the server overrides the JMSExpiration value set by the producer in the message header with the value 0. If an expiration property is set for a destination, the server retains the message for the length of time specified by the expiration property. if the primary consumer fails, the server selects one of the standby consumers as the new primary and begins delivering messages to it. Instead, these additional consumers act as standby. No other consumers can receive messages from the queue. Only one consumer can read the message from this queue. We use this property to limit the consumer count.

But we can add this property to a global queue. This property is only available for the queue. can set the properties directly in the nf or nf file or by means of the setprop or addprop command in the EMS Administration Tool. In this post, we are going to discuss different destination properties available in TIBCO EMS server for queues and topic. TIBCO ActiveMatrix BusinessWorks is a robust and highly scalable platform that can be used to develop new services, automate business processes, and integrate applications – minimal code required.Destination Properties, EMS, QUEUE and TOPIC, TIBCO
