Specifies the JMS clientID which is used in combination with the
Should messages be dispatched synchronously or asynchronously from the producer thread for non-durable topics in the broker?
For fast consumers set this to
For slow consumers set it to
I would like to be an Exclusive Consumer on the queue.
For Slow Consumer Handling on non-durable topics by dropping old messages - we can set a maximum-pending limit, such that once a slow consumer backs up to this high water mark we begin to discard old messages.
Specifies whether or not locally sent messages should be ignored for subscriptions.
Specifies the maximum number of pending messages that will be dispatched to the client. Once this maximum is reached no more messages are dispatched until the client acknowledges a message.
Set to a low value > 1 for fair distribution of messages across consumers when processing messages can be slow
Note: if your STOMP client is implemented using a dynamic scripting language like Ruby, say, then this parameter must be set to
STOMP does not support a value of
Sets the priority of the consumer so that dispatching can be weighted in priority order.
For non-durable topics make this subscription retroactive.
For durable topic subscriptions you must specify the same
Note: the spelling
For the 5.0 release of ActiveMQ, both
Specifies a JMS Selector using SQL 92 syntax as specified in the JMS 1.1 specification. This allows a filter to be applied to each message as part of the subscription.