- client
An application that uses the message broker to communicate with other applications. These applications use one of the broker's client API to connect to and interact with the broker.
- consumer
An application that consumes messages from a messaging destination.
- connection factory
An object that a client uses to create a connection to a broker. A factory supports attributes that configure the quality of service for the connections it creates.
- destination
A logical holding area for messages in a message broker. Clients publish messages to and consume messages from destinations.
- durable subscriber
A message consumer that receives all messages published on a topic, including those published while the subscriber is inactive.
- message
An atomic unit of data that is passed between two or more clients. A message consists of three components:
headers—contain a predefined set of metadata that is used to communicate information about a message between the different parties that handle the message
properties—contain application defined metadata about a message to the different parties that handle the message
body—contains the messages payload
- message selector
A string containing a boolean SQL statement using SQL 92 syntax that is used to select messages based on JMS message header properties.
- message group
A collection of JMS messages that are assigned the same JMSXGroupID.
When used in conjunction with the JMSXGroupSeq message groups can be used to ensure that messages are processed in the proper sequence.
- master/slave
A topology in which a single instance, the master, is active and one or more instances, the slaves, are ready to resume when the active instance stops.
- producer
An application that creates messages and posts them to a messaging destination.
- point-to-point messaging
A messaging style where messages are sent between two known endpoints. This messaging style is typically implemented using queues.
- publish and subscribe messaging, pub/sub
A messaging style where message producers send(publish) messages to a destination and interested consumers can register(subscribe) to receive messages from the destination. This style of messaging is implemented using topics.
- queue
A destination that uses first in/first out semantics.
- request-reply pattern
A messaging pattern in which a message producer receives a message and returns a correlated message.
- Session
A JMS object that provides a single-threaded context for producing and consuming messages. JMS clients use the Session object to create producers, consumers, messages, and other artifacts used to work with messages.
- Streaming Text Orientated Messaging Protocol, STOMP
A language agnostic, simple text-based protocol that allows clients to talk with any message broker supporting the protocol.
- transport
A standards-based network protocol, such as HTTP or STOMP, that defines how objects communicate over a network.
- topic
A destination that uses publish and subscribe semantics.
- advisory
- advisory message
A special type of message that contains administrative information about the message broker. They are sent by the broker to special advisory topics.
- advisory topic
A group of special topics that are created by a message broker that are used for monitoring the state of the broker. The broker sends messages about a variety of internal broker events. Clients subscribing to these topics receive advisory messages about these objects.
- Apache ActiveMQ
An open source project that provides the messaging technology for Red Hat JBoss A-MQ.
- cluster
- connection
A bridge between a client and a broker connector or between two brokers in a network of brokers.
- connector
An object that connects clients to a broker.
- composite destination
A virtual destination that serves as a proxy for multiple destinations. Producers can send messages to the composite destination an it will be automatically sent to all of the physical destinations that make up the composite destination.
- dead letter queue
A special destination used by the message broker to hold undeliverable messages.
- dynamic discovery
A mechanism for clients to become aware of the existence of brokers through the use of a discovery agent.
- discovery agent
A mechanism that advertises the list of available message brokers to message clients and other message brokers.
- exclusive consumer
A mechanism that ensures that only one consumer connected to a queue can consume messages.
- failover
A transport that automatically moves to a new connection in the event that its current connection fails.
A cluster architecture where clients are able to migrate from a failed broker to a running broker.
- network of brokers
A group of brokers that are linked together to operate as a single logical unit.
- network connector
A configuration entity used to link brokers together to form a network of brokers.
- network bridge
A runtime directional link between brokers that is used to forward messages. Network bridges are created by network connectors.
- retroactive consumer
A consumer that indicates to the topic that every attempt is to be made to send messages that the consumer may have missed.
- store and forward
A paradigm in which brokers receive messages, store them locally, and forwards the message to a recipient when it is able to do so. The message is only deleted once it has been successfully delivered.
- transport connector
An address at which a message broker accepts client connections.
- virtual destination
A logical destination that represents one or more physical destinations.
- virtual topic
A logical topic that allows consumers to use a physical queue to consume messages from the destination.
- Java Message Service, JMS
A Java API implementing a messaging standard that allows application components based on J2EE to create, send, receive, and read messages. It enables distributed communication that is loosely coupled, reliable, and asynchronous.
