Apache ActiveMQ Artemis server
Creates an Apache ActiveMQ Artemis server for hosting message queues.
Each acceptor defines a way in which connections can be made to the Artemis server.
Connectors are used by a client to define how to connect to a server. Connectors are also used to create bridges between servers or create clusters of servers.
Defines a cluster of servers that share message processing load.
When match is async.example.message.onramp
for example, the settings would only be applied to any addresses which exactly matches the address async.example.message.onramp
. You can also use wildcards to apply settings against many addresses. For example, if you used the match string async.#
, the settings would be applied to all addresses that start with async.
(which would be all asynchronous queues).
Note that only the most specific match is applied for each address. Some examples from most specific to least specific: sync.example.message.onramp
(matches one queue), async.example.*.onramp
(matches all onramp flow for the example
system), async.example.#
(matches all synchronous flow for the example
system), async.#
.
Security settings which will be applied against any addresses with a name that matches a certain wildcard expression.
When match is async.example.message.onramp
for example, the settings would only be applied to any addresses which exactly matches the address async.example.message.onramp
. You can also use wildcards to apply settings against many addresses. For example, if you used the match string async.#
, the settings would be applied to all addresses that start with async.
(which would be all asynchronous queues).
Note that only the most specific match is applied for each address. Some examples from most specific to least specific: sync.example.message.onramp
(matches one queue), async.example.*.onramp
(matches all onramp flow for the example
system), async.example.#
(matches all synchronous flow for the example
system), async.#
.
When creating connections between nodes of a cluster to form a cluster connection, Artemis uses a cluster user and cluster password.
In normal use, Artemis does not update delivery count persistently until a message is rolled back (i.e. the delivery count is not updated before the message is delivered to the consumer).
In most messaging use cases, the messages are consumed, acknowledged and forgotten as soon as they are consumed. In these cases, updating the delivery count persistently before delivering the message would add an extra persistent step for each message delivered, implying a significant performance penalty.
Artemis has an extensive management API that allows a user to modify a server configuration, create new resources (e.g. addresses and queues), inspect these resources (e.g. how many messages are currently held in a queue) and interact with it (e.g. to remove messages from a queue). Artemis also allows clients to subscribe to management notifications.
Two different strategies for backing up a server are supported: shared store and replication. This configures which strategy a cluster should use to provide the backing up of a servers data. Within this configuration element a server acts either as a master (live), slave (backup).
The reaper thread will periodically inspect the queues to check if messages have expired.
You may configure one more addresses that are part of your network topology, that will be pinged through the life cycle of the server. The server will stop itself until the network is back on such case.
_id
Reference to a (custom) security manager implementation that can validate user credentials (authentication) and user roles (authorization).
Note that the cluster user of the ActiveMQ Artemis server always has full privileges and the validation of his credentials is done internally (never even reaching the security manager).
_id
Reference to a (custom) security manager implementation that can validate user credentials (authentication) and user roles (authorization).
Note that the cluster user of the ActiveMQ Artemis server always has full privileges and the validation of his credentials is done internally (never even reaching the security manager).