This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • Stomp

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Verb

Header

Type

Description

CONNECT

client-id

string

Specifies the JMS clientID which is used in combination with the activemq.subcriptionName to denote a durable subscriber.

SUBSCRIBE

activemq.dispatchAsync

boolean

Should messages be dispatched synchronously or asynchronously from the producer thread for non-durable topics in the broker?

For fast consumers set this to false.

For slow consumers set it to true so that dispatching will not block fast consumers.

SUBSCRIBE

activemq.exclusive

boolean

I would like to be an Exclusive Consumer on the queue.

SUBSCRIBE

activemq.maximumPendingMessageLimit

int

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.

SUBSCRIBE

activemq.noLocal

boolean

Specifies whether or not locally sent messages should be ignored for subscriptions.

Set to true to filter out locally sent messages.

SUBSCRIBE

activemq.prefetchSize

int

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 1 as there is no notion of a client-side message size to be sized.

STOMP does not support a value of 0.

SUBSCRIBE

activemq.priority

byte

Sets the priority of the consumer so that dispatching can be weighted in priority order.

SUBSCRIBE

activemq.retroactive

boolean

For non-durable topics make this subscription retroactive.

SUBSCRIBE

activemq.subscriptionName

string

For durable topic subscriptions you must specify the same activemq.client-id on the connection and activemq.subcriptionName on the subscribe prior to v5.7.0.

Note: the spelling subcriptionName NOT subscriptionName. This is not intuitive, but it is how it is implemented in ActiveMQ 4.x.

For the 5.0 release of ActiveMQ, both subcriptionName and subscriptionName will be supported (subcriptionName was removed as of v5.6.0).

CONNECT

client-id

string

Specifies the JMS clientID which is used in combination with the activemq.subcriptionName to denote a durable subscriber.

SUBSCRIBE

selector

string

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.