You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by cl...@apache.org on 2015/05/21 23:34:57 UTC
[1/2] activemq-artemis git commit: Doc improvements around libaio and
removing extra chapter about running server
Repository: activemq-artemis
Updated Branches:
refs/heads/master 22d54c583 -> 27cbc92a9
Doc improvements around libaio and removing extra chapter about running server
Project: http://git-wip-us.apache.org/repos/asf/activemq-artemis/repo
Commit: http://git-wip-us.apache.org/repos/asf/activemq-artemis/commit/647f6657
Tree: http://git-wip-us.apache.org/repos/asf/activemq-artemis/tree/647f6657
Diff: http://git-wip-us.apache.org/repos/asf/activemq-artemis/diff/647f6657
Branch: refs/heads/master
Commit: 647f665700ab79a7d378c7035f5eb7e63b66307d
Parents: 22d54c5
Author: Clebert Suconic <cl...@apache.org>
Authored: Thu May 21 11:51:48 2015 -0400
Committer: Clebert Suconic <cl...@apache.org>
Committed: Thu May 21 11:51:48 2015 -0400
----------------------------------------------------------------------
docs/user-manual/en/SUMMARY.md | 1 -
docs/user-manual/en/libaio.md | 28 +++-
docs/user-manual/en/running-server.md | 246 -----------------------------
docs/user-manual/en/using-server.md | 177 ++++++++++++++++++++-
4 files changed, 194 insertions(+), 258 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/activemq-artemis/blob/647f6657/docs/user-manual/en/SUMMARY.md
----------------------------------------------------------------------
diff --git a/docs/user-manual/en/SUMMARY.md b/docs/user-manual/en/SUMMARY.md
index fce7fbb..97e3ec3 100644
--- a/docs/user-manual/en/SUMMARY.md
+++ b/docs/user-manual/en/SUMMARY.md
@@ -4,7 +4,6 @@
* [Legal Notice](notice.md)
* [Preface](preface.md)
* [Project Info](project-info.md)
-* [Running the Server](running-server.md)
* [Messaging Concepts](messaging-concepts.md)
* [Architecture](architecture.md)
* [Using the Server](using-server.md)
http://git-wip-us.apache.org/repos/asf/activemq-artemis/blob/647f6657/docs/user-manual/en/libaio.md
----------------------------------------------------------------------
diff --git a/docs/user-manual/en/libaio.md b/docs/user-manual/en/libaio.md
index 8140426..787d044 100644
--- a/docs/user-manual/en/libaio.md
+++ b/docs/user-manual/en/libaio.md
@@ -1,6 +1,6 @@
# Libaio Native Libraries
-Apache ActiveMQ Artemis distributes a native library, used as a bridge between Apache ActiveMQ Artemis
+Apache ActiveMQ Artemis distributes a native library, used as a bridge for its fast journal, between Apache ActiveMQ Artemis
and Linux libaio.
`libaio` is a library, developed as part of the Linux kernel project.
@@ -18,7 +18,23 @@ These are the native libraries distributed by Apache ActiveMQ Artemis:
- libActiveMQAIO64.so - x86 64 bits
When using libaio, Apache ActiveMQ Artemis will always try loading these files as long
-as they are on the [library path](#using-server.library.path).
+as they are on the [library path](using-server.html#library-path)
+
+
+## Runtime dependencies
+
+If you just want to use the provided native binaries you need to install the required libaio dependency.
+
+You can install libaio using the following steps as the root user:
+
+Using yum, (e.g. on Fedora or Red Hat Enterprise Linux):
+
+ yum install libaio
+
+Using aptitude, (e.g. on Ubuntu or Debian system):
+
+ apt-get install libaio
+
## Compiling the native libraries
@@ -27,11 +43,11 @@ x86\_64 (for example Itanium 64 bits or IBM Power) you may need to
compile the native library, since we do not distribute binaries for
those platforms with the release.
-## Install requirements
+## Compilation dependencies
> **Note**
>
-> At the moment the native layer is only available on Linux. If you are
+> The native layer is only available on Linux. If you are
> in a platform other than Linux the native compilation will not work
These are the required linux packages to be installed for the compilation to work:
@@ -51,11 +67,11 @@ These are the required linux packages to be installed for the compilation to wor
To perform this installation on RHEL or Fedora, you can simply type this at a command line:
- sudo yum install libtool gcc-c++ gcc libaio libaio-devel make
+ sudo yum install libtool gcc-c++ gcc libaio libaio-devel
Or on Debian systems:
- sudo apt-get install libtool gcc-g++ gcc libaio libaio-dev make
+ sudo apt-get install libtool gcc-g++ gcc libaio libaio-dev
> **Note**
>
http://git-wip-us.apache.org/repos/asf/activemq-artemis/blob/647f6657/docs/user-manual/en/running-server.md
----------------------------------------------------------------------
diff --git a/docs/user-manual/en/running-server.md b/docs/user-manual/en/running-server.md
deleted file mode 100644
index c9e1e4a..0000000
--- a/docs/user-manual/en/running-server.md
+++ /dev/null
@@ -1,246 +0,0 @@
-Prerequisites
-=============
-
-> **Note**
->
-> ActiveMQ Artemis only runs on Java 7 or later.
-
-By default, ActiveMQ Artemis server runs with 1GiB of memory. If your computer
-has less memory, or you want to run it with more available RAM, modify
-the value in `bin/run.sh` accordingly.
-
-If you are on Linux you may want to enable libaio For persistence,
-ActiveMQ Artemis uses its own fast journal, which you can
-configure to use libaio (which is the default when running on Linux) or
-Java NIO. In order to use the libaio module on Linux, you'll need to
-install libaio, if it's not already installed.
-
-If you're not running on Linux then you don't need to worry about this.
-
-You can install libaio using the following steps as the root user:
-
-Using yum, (e.g. on Fedora or Red Hat Enterprise Linux):
-
- yum install libaio
-
-Using aptitude, (e.g. on Ubuntu or Debian system):
-
- apt-get install libaio
-
-Installation
-============
-
-After downloading the distribution, the following highlights some important folders on the distribution:
-
- |___ bin
- |
- |___ web
- | |___ user-manual
- | |___ api
- |
- |___ examples
- | |___ core
- | |___ javaee
- | |___ jms
- |
- |___ lib
- |
- |___ schema
-
-
-- `bin` -- binaries and scripts needed to run ActiveMQ Artemis.
-
-- `web` -- The folder where the web context is loaded when ActiveMQ Artemis runs.
-
-- `user-manual` -- The user manual is placed under the web folder.
-
-- `api` -- The api documentation is placed under the web folder
-
-- `examples` -- JMS and Java EE examples. Please refer to the 'running
- examples' chapter for details on how to run them.
-
-- `lib` -- jars and libraries needed to run ActiveMQ Artemis
-
-- `licenses` -- licenses for ActiveMQ Artemis
-
-- `schemas` -- XML Schemas used to validate ActiveMQ Artemis configuration
- files
-
-Creating a Broker Instance
-==========================
-
-
-A broker instance is the directory containing all the configuration and runtime
-data, such as logs and data files, associated with a broker process. It is recommended that
-you do *not* create the instance directory under `${ARTEMIS_HOME}`. This separation is
-encouraged so that you can more easily upgrade when the next version of ActiveMQ Artemis is released.
-
-On Unix systems, it is a common convention to store this kind of runtime data under
-the `/var/lib` directory. For example, to create an instance at '/var/lib/mybroker', run
-the following commands in your command line shell:
-
- cd /var/lib
- ${ARTEMIS_HOME}/bin/activemq create mybroker
-
-A broker instance directory will contain the following sub directories:
-
- * `bin`: holds execution scripts associated with this instance.
- * `etc`: hold the instance configuration files
- * `data`: holds the data files used for storing persistent messages
- * `log`: holds rotating log files
- * `tmp`: holds temporary files that are safe to delete between broker runs
-
-At this point you may want to adjust the default configuration located in
-the `etc` directory.
-
-Environment variables are used to provide ease of changing ports, hosts and
-data directories used and can be found in `etc/activemq.profile` on linux and
-`etc\activemq.profile.cmd` on Windows.
-
-
-Options
-=======
-
-There are several options you can use when creating an instance.
-
-For a full list of updated properties always use:
-
-```
- $./artemis help create
- NAME
- artemis create - creates a new broker instance
-
- SYNOPSIS
- artemis create [--allow-anonymous]
- [--cluster-password <clusterPassword>] [--cluster-user <clusterUser>]
- [--clustered] [--data <data>] [--encoding <encoding>] [--force]
- [--home <home>] [--host <host>] [--java-options <javaOptions>]
- [--password <password>] [--port-offset <portOffset>] [--replicated]
- [--role <role>] [--shared-store] [--silent-input] [--user <user>] [--]
- <directory>
-
- OPTIONS
- --allow-anonymous
- Enables anonymous configuration on security (Default: input)
-
- --cluster-password <clusterPassword>
- The cluster password to use for clustering. (Default: input)
-
- --cluster-user <clusterUser>
- The cluster user to use for clustering. (Default: input)
-
- --clustered
- Enable clustering
-
- --data <data>
- Directory where ActiveMQ Data is used. Path are relative to
- artemis.instance/bin
-
- --encoding <encoding>
- The encoding that text files should use
-
- --force
- Overwrite configuration at destination directory
-
- --home <home>
- Directory where ActiveMQ Artemis is installed
-
- --host <host>
- The host name of the broker (Default: 0.0.0.0 or input if clustered)
-
- --java-options <javaOptions>
- Extra java options to be passed to the profile
-
- --password <password>
- The user's password (Default: input)
-
- --port-offset <portOffset>
- Off sets the default ports
-
- --replicated
- Enable broker replication
-
- --role <role>
- The name for the role created (Default: amq)
-
- --shared-store
- Enable broker shared store
-
- --silent-input
- It will disable all the inputs, and it would make a best guess for
- any required input
-
- --user <user>
- The username (Default: input)
-
- --
- This option can be used to separate command-line options from the
- list of argument, (useful when arguments might be mistaken for
- command-line options
-
- <directory>
- The instance directory to hold the broker's configuration and data
-```
-
-Some of these properties may be mandatory in certain configurations and the system may ask you for additional input.
-
-```
- ./artemis create /usr/server
- Creating ActiveMQ Artemis instance at: /user/server
-
- --user: is mandatory with this configuration:
- Please provide the default username:
- admin
-
- --password: is mandatory with this configuration:
- Please provide the default password:
-
-
- --allow-anonymous: is mandatory with this configuration:
- Allow anonymous access? (Y/N):
- y
-
- You can now start the broker by executing:
-
- "/user/server/bin/artemis" run
-
- Or you can run the broker in the background using:
-
- "/user/server/bin/artemis-service" start
-```
-
-
-Starting and Stopping a Broker Instance
-=======================================
-
-Assuming you created the broker instance under `/var/lib/mybroker` all you need
-to do start running the broker instance is execute:
-
- /var/lib/mybroker/bin/activemq run
-
-Now that the broker is running, you can optionally run some of the included
-examples to verify the the broker is running properly.
-
-To stop the Apache ActiveMQ Artemis instance you will use the same `activemq` script, but with
-the `stop argument`. Example:
-
- /var/lib/mybroker/bin/activemq stop
-
-By default the `etc/bootstrap.xml` configuration is
-used. The configuration can be changed e.g. by running
-`./activemq run -- xml:path/to/bootstrap.xml` or another
-config of your choosing.
-
-
-Windows Server
-==============
-
-On windows you will have the option to run ActiveMQ Artemis as a service.
-Just use the following command to install it:
-
-```
- $ ./artemis-service.exe install
-```
-
-
-The create process should give you a hint of the available commands available for the artemis-service.exe
\ No newline at end of file
http://git-wip-us.apache.org/repos/asf/activemq-artemis/blob/647f6657/docs/user-manual/en/using-server.md
----------------------------------------------------------------------
diff --git a/docs/user-manual/en/using-server.md b/docs/user-manual/en/using-server.md
index 59dc3c4..2fa214d 100644
--- a/docs/user-manual/en/using-server.md
+++ b/docs/user-manual/en/using-server.md
@@ -12,6 +12,46 @@ with a JMS Service enabled.
This document will refer to the full path of the directory where the ActiveMQ
distribution has been extracted to as `${ARTEMIS_HOME}` directory.
+Installation
+============
+
+After downloading the distribution, the following highlights some important folders on the distribution:
+
+ |___ bin
+ |
+ |___ web
+ | |___ user-manual
+ | |___ api
+ |
+ |___ examples
+ | |___ core
+ | |___ javaee
+ | |___ jms
+ |
+ |___ lib
+ |
+ |___ schema
+
+
+- `bin` -- binaries and scripts needed to run ActiveMQ Artemis.
+
+- `web` -- The folder where the web context is loaded when ActiveMQ Artemis runs.
+
+- `user-manual` -- The user manual is placed under the web folder.
+
+- `api` -- The api documentation is placed under the web folder
+
+- `examples` -- JMS and Java EE examples. Please refer to the 'running
+ examples' chapter for details on how to run them.
+
+- `lib` -- jars and libraries needed to run ActiveMQ Artemis
+
+- `licenses` -- licenses for ActiveMQ Artemis
+
+- `schemas` -- XML Schemas used to validate ActiveMQ Artemis configuration
+ files
+
+
## Creating a Broker Instance
A broker instance is the directory containing all the configuration and runtime
@@ -19,7 +59,7 @@ data, such as logs and data files, associated with a broker process. It is reco
you do *not* create the instance directory under `${ARTEMIS_HOME}`. This separation is
encouraged so that you can more easily upgrade when the next version of ActiveMQ Artemis is released.
-On Unix systems, it is a common convention to store this kind of runtime data under
+On Unix systems, it is a common convention to store this kind of runtime data under
the `/var/lib` directory. For example, to create an instance at '/var/lib/mybroker', run
the following commands in your command line shell:
@@ -37,6 +77,117 @@ A broker instance directory will contain the following sub directories:
At this point you may want to adjust the default configuration located in
the `etc` directory.
+###Options
+There are several options you can use when creating an instance.
+
+For a full list of updated properties always use:
+
+```
+ $./artemis help create
+ NAME
+ artemis create - creates a new broker instance
+
+ SYNOPSIS
+ artemis create [--allow-anonymous]
+ [--cluster-password <clusterPassword>] [--cluster-user <clusterUser>]
+ [--clustered] [--data <data>] [--encoding <encoding>] [--force]
+ [--home <home>] [--host <host>] [--java-options <javaOptions>]
+ [--password <password>] [--port-offset <portOffset>] [--replicated]
+ [--role <role>] [--shared-store] [--silent-input] [--user <user>] [--]
+ <directory>
+
+ OPTIONS
+ --allow-anonymous
+ Enables anonymous configuration on security (Default: input)
+
+ --cluster-password <clusterPassword>
+ The cluster password to use for clustering. (Default: input)
+
+ --cluster-user <clusterUser>
+ The cluster user to use for clustering. (Default: input)
+
+ --clustered
+ Enable clustering
+
+ --data <data>
+ Directory where ActiveMQ Data is used. Path are relative to
+ artemis.instance/bin
+
+ --encoding <encoding>
+ The encoding that text files should use
+
+ --force
+ Overwrite configuration at destination directory
+
+ --home <home>
+ Directory where ActiveMQ Artemis is installed
+
+ --host <host>
+ The host name of the broker (Default: 0.0.0.0 or input if clustered)
+
+ --java-options <javaOptions>
+ Extra java options to be passed to the profile
+
+ --password <password>
+ The user's password (Default: input)
+
+ --port-offset <portOffset>
+ Off sets the default ports
+
+ --replicated
+ Enable broker replication
+
+ --role <role>
+ The name for the role created (Default: amq)
+
+ --shared-store
+ Enable broker shared store
+
+ --silent-input
+ It will disable all the inputs, and it would make a best guess for
+ any required input
+
+ --user <user>
+ The username (Default: input)
+
+ --
+ This option can be used to separate command-line options from the
+ list of argument, (useful when arguments might be mistaken for
+ command-line options
+
+ <directory>
+ The instance directory to hold the broker's configuration and data
+```
+
+
+Some of these properties may be mandatory in certain configurations and the system may ask you for additional input.
+
+```
+ ./artemis create /usr/server
+ Creating ActiveMQ Artemis instance at: /user/server
+
+ --user: is mandatory with this configuration:
+ Please provide the default username:
+ admin
+
+ --password: is mandatory with this configuration:
+ Please provide the default password:
+
+
+ --allow-anonymous: is mandatory with this configuration:
+ Allow anonymous access? (Y/N):
+ y
+
+ You can now start the broker by executing:
+
+ "/user/server/bin/artemis" run
+
+ Or you can run the broker in the background using:
+
+ "/user/server/bin/artemis-service" start
+```
+
+
### Starting and Stopping a Broker Instance
Assuming you created the broker instance under `/var/lib/mybroker` all you need
@@ -44,10 +195,10 @@ to do start running the broker instance is execute:
/var/lib/mybroker/bin/activemq run
-Now that the broker is running, you can optionally run some of the included
+Now that the broker is running, you can optionally run some of the included
examples to verify the the broker is running properly.
-To stop the Apache ActiveMQ Artemis instance you will use the same `activemq` script, but with
+To stop the Apache ActiveMQ Artemis instance you will use the same `activemq` script, but with
the `stop argument`. Example:
/var/lib/mybroker/bin/activemq stop
@@ -94,13 +245,16 @@ configuration when running the run script.
## Library Path
-If you're using the [Asynchronous IO Journal](#aio-journal) on Linux,
+If you're using the [Asynchronous IO Journal](libaio.md) on Linux,
you need to specify `java.library.path` as a property on your Java
options. This is done automatically in the scripts.
If you don't specify `java.library.path` at your Java options then the
JVM will use the environment variable `LD_LIBRARY_PATH`.
+You will need to make sure libaio is installed on Linux. For more information refer to the libaio chapter at
+[Runtime Dependencies](libaio.html#runtime-dependencies)
+
## System properties
Apache ActiveMQ Artemis can take a system property on the command line for configuring
@@ -164,4 +318,17 @@ cases the defaults will do fine, in fact every attribute can be
defaulted which means a file with a single empty `configuration` element
is a valid configuration file. The different configuration will be
explained throughout the manual or you can refer to the configuration
-reference [here](#configuration-index).
+reference [here](configuration-index.md).
+
+Windows Server
+==============
+
+On windows you will have the option to run ActiveMQ Artemis as a service.
+Just use the following command to install it:
+
+```
+ $ ./artemis-service.exe install
+```
+
+
+The create process should give you a hint of the available commands available for the artemis-service.exe
\ No newline at end of file
[2/2] activemq-artemis git commit: removing chapters from links
Posted by cl...@apache.org.
removing chapters from links
Project: http://git-wip-us.apache.org/repos/asf/activemq-artemis/repo
Commit: http://git-wip-us.apache.org/repos/asf/activemq-artemis/commit/27cbc92a
Tree: http://git-wip-us.apache.org/repos/asf/activemq-artemis/tree/27cbc92a
Diff: http://git-wip-us.apache.org/repos/asf/activemq-artemis/diff/27cbc92a
Branch: refs/heads/master
Commit: 27cbc92a9279b6655b6754f6ec6a2416e7e9a1e9
Parents: 647f665
Author: Clebert Suconic <cl...@apache.org>
Authored: Thu May 21 12:02:08 2015 -0400
Committer: Clebert Suconic <cl...@apache.org>
Committed: Thu May 21 12:08:11 2015 -0400
----------------------------------------------------------------------
docs/user-manual/en/configuration-index.md | 260 ++++++++++++------------
1 file changed, 130 insertions(+), 130 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/activemq-artemis/blob/27cbc92a/docs/user-manual/en/configuration-index.md
----------------------------------------------------------------------
diff --git a/docs/user-manual/en/configuration-index.md b/docs/user-manual/en/configuration-index.md
index 6ed0f2e..61c01d7 100644
--- a/docs/user-manual/en/configuration-index.md
+++ b/docs/user-manual/en/configuration-index.md
@@ -22,30 +22,30 @@ For example on the main config you will have bridges and at the [list of bridge]
Name | Description
:--- | :---
-[acceptors](configuring-transports.md "16.1. Understanding Acceptors") | a list of remoting acceptors
-[acceptors.acceptor](configuring-transports.md "16.1. Understanding Acceptors") | Each acceptor is composed for just an URL
-[address-settings](queue-attributes.md "25.3. Configuring Queues Via Address Settings") | [a list of address-setting](#address-setting-type)
-[allow-failback](ha.md "39.1.4. Failing Back to live Server") | Should stop backup on live restart. default true
-[async-connection-execution-enabled](connection-ttl.md "17.3. Configuring Asynchronous Connection Execution") | If False delivery would be always asynchronous. default true
-[bindings-directory](persistence.md "15.1. Configuring the bindings journal") | The folder in use for the bindings folder
-[bridges](core-bridges.md "Chapter 36. Core Bridges") | [a list of bridge](#bridge-type)
-[broadcast-groups](clusters.md "Chapter 38. Clusters") | [a list of broadcast-group](#broadcast-group-type)
+[acceptors](configuring-transports.md "Understanding Acceptors") | a list of remoting acceptors
+[acceptors.acceptor](configuring-transports.md "Understanding Acceptors") | Each acceptor is composed for just an URL
+[address-settings](queue-attributes.md "Configuring Queues Via Address Settings") | [a list of address-setting](#address-setting-type)
+[allow-failback](ha.md "Failing Back to live Server") | Should stop backup on live restart. default true
+[async-connection-execution-enabled](connection-ttl.md "Configuring Asynchronous Connection Execution") | If False delivery would be always asynchronous. default true
+[bindings-directory](persistence.md "Configuring the bindings journal") | The folder in use for the bindings folder
+[bridges](core-bridges.md "Core Bridges") | [a list of bridge](#bridge-type)
+[broadcast-groups](clusters.md "Clusters") | [a list of broadcast-group](#broadcast-group-type)
[check-for-live-server](ha.md) | Used for a live server to verify if there are other nodes with the same ID on the topology
-[cluster-connections](clusters.md "Chapter 38. Clusters") | [a list of cluster-connection](#cluster-connection-type)
-[cluster-password](clusters.md "Chapter 38. Clusters") | Cluster password. It applies to all cluster configurations.
-[cluster-user](clusters.md "Chapter 38. Clusters") | Cluster username. It applies to all cluster configurations.
+[cluster-connections](clusters.md "Clusters") | [a list of cluster-connection](#cluster-connection-type)
+[cluster-password](clusters.md "Clusters") | Cluster password. It applies to all cluster configurations.
+[cluster-user](clusters.md "Clusters") | Cluster username. It applies to all cluster configurations.
[connection-ttl-override](connection-ttl.md) | if set, this will override how long (in ms) to keep a connection alive without receiving a ping. -1 disables this setting. Default -1
-[connectors.connector](configuring-transports.md "16.2. Understanding Connectors") | The URL for the connector. This is a list
-[create-bindings-dir](persistence.md "15.1. Configuring the bindings journal") | true means that the server will create the bindings directory on start up. Default=true
+[connectors.connector](configuring-transports.md "Understanding Connectors") | The URL for the connector. This is a list
+[create-bindings-dir](persistence.md "Configuring the bindings journal") | true means that the server will create the bindings directory on start up. Default=true
[create-journal-dir](persistence.md) | true means that the journal directory will be created. Default=true
-[discovery-groups](clusters.md "Chapter 38. Clusters") | [a list of discovery-group](#discovery-group-type)
-[diverts](diverts.md "Chapter 35. Diverting and Splitting Message Flows") | [a list of diverts to use](#divert-type)
+[discovery-groups](clusters.md "Clusters") | [a list of discovery-group](#discovery-group-type)
+[diverts](diverts.md "Diverting and Splitting Message Flows") | [a list of diverts to use](#divert-type)
[graceful-shutdown-enabled](graceful-shutdown.md "Graceful Server Shutdown") | true means that graceful shutdown is enabled. Default=true
[graceful-shutdown-timeout](graceful-shutdown.md "Graceful Server Shutdown") | Timeout on waitin for clients to disconnect before server shutdown. Default=-1
-[grouping-handler](message-grouping.md "Chapter 28. Message Grouping") | Message Group configuration
-[id-cache-size](duplicate-detection.md "37.2. Configuring the Duplicate ID Cache") | The duplicate detection circular cache size. Default=20000
-[jmx-domain](management.md "30.2.1. Configuring JMX") | the JMX domain used to registered MBeans in the MBeanServer. Default=org.apache.activemq
-[jmx-management-enabled](management.md "30.2.1. Configuring JMX") | true means that the management API is available via JMX. Default=true
+[grouping-handler](message-grouping.md "Message Grouping") | Message Group configuration
+[id-cache-size](duplicate-detection.md "Configuring the Duplicate ID Cache") | The duplicate detection circular cache size. Default=20000
+[jmx-domain](management.md "Configuring JMX") | the JMX domain used to registered MBeans in the MBeanServer. Default=org.apache.activemq
+[jmx-management-enabled](management.md "Configuring JMX") | true means that the management API is available via JMX. Default=true
[journal-buffer-size](persistence.md) | The size of the internal buffer on the journal in KB. Default=490 KiB
[journal-buffer-timeout](persistence.md) | The Flush timeout for the journal buffer
[journal-compact-min-files](persistence.md) | The minimal number of data files before we can start compacting. Setting this to 0 means compacting is disabled. Default=10
@@ -57,166 +57,166 @@ Name | Description
[journal-sync-non-transactional](persistence.md) | if true wait for non transaction data to be synced to the journal before returning response to client. Default=true
[journal-sync-transactional](persistence.md) | if true wait for transaction data to be synchronized to the journal before returning response to client. Default=true
[journal-type](persistence.md) | the type of journal to use. Default=ASYNCIO
-[large-messages-directory](large-messages.md "23.1. Configuring the server") | the directory to store large messages. Default=data/largemessages
-[management-address](management.md "30.3.1. Configuring Core Management") | the name of the management address to send management messages to. It is prefixed with "jms.queue" so that JMS clients can send messages to it. Default=jms.queue.activemq.management
-[management-notification-address](management.md "30.5.2.1. Configuring The Core Management Notification Address") | the name of the address that consumers bind to receive management notifications. Default=activemq.notifications
-[mask-password](configuration-index.md "50.1.3. Using Masked Passwords in Configuration Files") | This option controls whether passwords in server configuration need be masked. If set to "true" the passwords are masked. Default=false
+[large-messages-directory](large-messages.md "Configuring the server") | the directory to store large messages. Default=data/largemessages
+[management-address](management.md "Configuring Core Management") | the name of the management address to send management messages to. It is prefixed with "jms.queue" so that JMS clients can send messages to it. Default=jms.queue.activemq.management
+[management-notification-address](management.md "Configuring The Core Management Notification Address") | the name of the address that consumers bind to receive management notifications. Default=activemq.notifications
+[mask-password](configuration-index.md "Using Masked Passwords in Configuration Files") | This option controls whether passwords in server configuration need be masked. If set to "true" the passwords are masked. Default=false
[max-saved-replicated-journals-size]() | This specifies how many times a replicated backup server can restart after moving its files on start. Once there are this number of backup journal files the server will stop permanently after if fails back. Default=2
[memory-measure-interval](perf-tuning.md) | frequency to sample JVM memory in ms (or -1 to disable memory sampling). Default=-1
[memory-warning-threshold](perf-tuning.md) | Percentage of available memory which will trigger a warning log. Default=25
-[message-counter-enabled](management.md "30.6.1. Configuring Message Counters") | true means that message counters are enabled. Default=false
-[message-counter-max-day-history](management.md "30.6.1. Configuring Message Counters") | how many days to keep message counter history. Default=10 (days)
-[message-counter-sample-period](management.md "30.6.1. Configuring Message Counters") | the sample period (in ms) to use for message counters. Default=10000
-[message-expiry-scan-period](message-expiry.md "22.3. Configuring The Expiry Reaper Thread") | how often (in ms) to scan for expired messages. Default=30000
-[message-expiry-thread-priority](message-expiry.md "22.3. Configuring The Expiry Reaper Thread") | the priority of the thread expiring messages. Default=3
-[page-max-concurrent-io](paging.md "24.3. Paging Mode") | The max number of concurrent reads allowed on paging. Default=5
-[paging-directory](paging.md "24.2. Configuration") | the directory to store paged messages in. Default=data/paging
-[persist-delivery-count-before-delivery](undelivered-messages.md "21.3. Delivery Count Persistence") | True means that the delivery count is persisted before delivery. False means that this only happens after a message has been cancelled. Default=false
-[persistence-enabled](persistence.md "15.6. Configuring ActiveMQ Artemis for Zero Persistence") | true means that the server will use the file based journal for persistence. Default=true
-[persist-id-cache](duplicate-detection.md "37.2. Configuring the Duplicate ID Cache") | true means that ID's are persisted to the journal. Default=true
-[queues](queue-attributes.md "25.1. Predefined Queues") | [a list of queue to be created](#queue-type)
-[remoting-incoming-interceptors](intercepting-operations.md "Chapter 47. Intercepting Operations") | A list of interceptor
+[message-counter-enabled](management.md "Configuring Message Counters") | true means that message counters are enabled. Default=false
+[message-counter-max-day-history](management.md "Configuring Message Counters") | how many days to keep message counter history. Default=10 (days)
+[message-counter-sample-period](management.md "Configuring Message Counters") | the sample period (in ms) to use for message counters. Default=10000
+[message-expiry-scan-period](message-expiry.md "Configuring The Expiry Reaper Thread") | how often (in ms) to scan for expired messages. Default=30000
+[message-expiry-thread-priority](message-expiry.md "Configuring The Expiry Reaper Thread") | the priority of the thread expiring messages. Default=3
+[page-max-concurrent-io](paging.md "Paging Mode") | The max number of concurrent reads allowed on paging. Default=5
+[paging-directory](paging.md "Configuration") | the directory to store paged messages in. Default=data/paging
+[persist-delivery-count-before-delivery](undelivered-messages.md "Delivery Count Persistence") | True means that the delivery count is persisted before delivery. False means that this only happens after a message has been cancelled. Default=false
+[persistence-enabled](persistence.md "Configuring ActiveMQ Artemis for Zero Persistence") | true means that the server will use the file based journal for persistence. Default=true
+[persist-id-cache](duplicate-detection.md "Configuring the Duplicate ID Cache") | true means that ID's are persisted to the journal. Default=true
+[queues](queue-attributes.md "Predefined Queues") | [a list of queue to be created](#queue-type)
+[remoting-incoming-interceptors](intercepting-operations.md "Intercepting Operations") | A list of interceptor
[resolveProtocols]() | Use [ServiceLoader](http://docs.oracle.com/javase/tutorial/ext/basics/spi.html) to load protocol modules. Default=true
-[scheduled-thread-pool-max-size](thread-pooling.md#server.scheduled.thread.pool "41.1.1. Server Scheduled Thread Pool")| Maximum number of threads to use for the scheduled thread pool. Default=5
-[security-enabled](security.md "Chapter 31. Security") | true means that security is enabled. Default=true
-[security-invalidation-interval](security.md "Chapter 31. Security") | how long (in ms) to wait before invalidating the security cache. Default=10000
-[security-settings](security.md "31.1. Role based security for addresses") | [a list of security-setting](#security-setting-type)
-[thread-pool-max-size](thread-pooling.md "41.1.1. Server Scheduled Thread Pool") | Maximum number of threads to use for the thread pool. -1 means 'no limits'.. Default=30
-[transaction-timeout](transaction-config.md "Chapter 18. Resource Manager Configuration") | how long (in ms) before a transaction can be removed from the resource manager after create time. Default=300000
-[transaction-timeout-scan-period](transaction-config.md "Chapter 18. Resource Manager Configuration") | how often (in ms) to scan for timeout transactions. Default=1000
-[wild-card-routing-enabled](wildcard-routing.md "Chapter 12. Routing Messages With Wild Cards") | true means that the server supports wild card routing. Default=true
+[scheduled-thread-pool-max-size](thread-pooling.md#server.scheduled.thread.pool "Server Scheduled Thread Pool")| Maximum number of threads to use for the scheduled thread pool. Default=5
+[security-enabled](security.md "Security") | true means that security is enabled. Default=true
+[security-invalidation-interval](security.md "Security") | how long (in ms) to wait before invalidating the security cache. Default=10000
+[security-settings](security.md "Role based security for addresses") | [a list of security-setting](#security-setting-type)
+[thread-pool-max-size](thread-pooling.md "Server Scheduled Thread Pool") | Maximum number of threads to use for the thread pool. -1 means 'no limits'.. Default=30
+[transaction-timeout](transaction-config.md "Resource Manager Configuration") | how long (in ms) before a transaction can be removed from the resource manager after create time. Default=300000
+[transaction-timeout-scan-period](transaction-config.md "Resource Manager Configuration") | how often (in ms) to scan for timeout transactions. Default=1000
+[wild-card-routing-enabled](wildcard-routing.md "Routing Messages With Wild Cards") | true means that the server supports wild card routing. Default=true
#address-setting type
Name | Description
:--- | :---
-[match ](queue-attributes.md "25.3. Configuring Queues Via Address Settings") | The filter to apply to the setting
-[dead-letter-address](undelivered-messages.md "21.2.1. Configuring Dead Letter Addresses") | dead letter address
-[expiry-address](message-expiry.md "22.2. Configuring Expiry Addresses") | expired messages address
-[expiry-delay](queue-attributes.md "25.3. Configuring Queues Via Address Settings") | expiration time override, -1 don't override with default=-1
-[redelivery-delay](undelivered-messages.md "21.1.1. Configuring Delayed Redelivery") | time to redeliver a message (in ms) with default=0
-[redelivery-delay-multiplier](queue-attributes.md "25.3. Configuring Queues Via Address Settings") | multiplier to apply to the "redelivery-delay"
-[max-redelivery-delay](queue-attributes.md "25.3. Configuring Queues Via Address Settings") | Max value for the redelivery-delay
-[max-delivery-attempts](undelivered-messages.md "21.2.1. Configuring Dead Letter Addresses") | Number of retries before dead letter address, default=10
-[max-size-bytes](paging.md "Chapter 24. Paging") | Limit before paging. -1 = infinite
-[page-size-bytes](paging.md "Chapter 24. Paging") | Size of each file on page, default=10485760
-[page-max-cache-size](paging.md "Chapter 24. Paging") | Maximum number of files cached from paging default=5
-[address-full-policy](queue-attributes.md "25.3. Configuring Queues Via Address Settings") | Model to chose after queue full
-[message-counter-history-day-limit](queue-attributes.md "25.3. Configuring Queues Via Address Settings") | Days to keep in history
-[last-value-queue](last-value-queues.md "Chapter 27. Last-Value Queues") | Queue is a last value queue, default=false
-[redistribution-delay](clusters.md "Chapter 38. Clusters") | Timeout before redistributing values after no consumers. default=-1
-[send-to-dla-on-no-route](queue-attributes.md "25.3. Configuring Queues Via Address Settings") | Forward messages to DLA when no queues subscribing. default=false
+[match ](queue-attributes.md "Configuring Queues Via Address Settings") | The filter to apply to the setting
+[dead-letter-address](undelivered-messages.md "Configuring Dead Letter Addresses") | dead letter address
+[expiry-address](message-expiry.md "Configuring Expiry Addresses") | expired messages address
+[expiry-delay](queue-attributes.md "Configuring Queues Via Address Settings") | expiration time override, -1 don't override with default=-1
+[redelivery-delay](undelivered-messages.md "Configuring Delayed Redelivery") | time to redeliver a message (in ms) with default=0
+[redelivery-delay-multiplier](queue-attributes.md "Configuring Queues Via Address Settings") | multiplier to apply to the "redelivery-delay"
+[max-redelivery-delay](queue-attributes.md "Configuring Queues Via Address Settings") | Max value for the redelivery-delay
+[max-delivery-attempts](undelivered-messages.md "Configuring Dead Letter Addresses") | Number of retries before dead letter address, default=10
+[max-size-bytes](paging.md "Paging") | Limit before paging. -1 = infinite
+[page-size-bytes](paging.md "Paging") | Size of each file on page, default=10485760
+[page-max-cache-size](paging.md "Paging") | Maximum number of files cached from paging default=5
+[address-full-policy](queue-attributes.md "Configuring Queues Via Address Settings") | Model to chose after queue full
+[message-counter-history-day-limit](queue-attributes.md "Configuring Queues Via Address Settings") | Days to keep in history
+[last-value-queue](last-value-queues.md "Last-Value Queues") | Queue is a last value queue, default=false
+[redistribution-delay](clusters.md "Clusters") | Timeout before redistributing values after no consumers. default=-1
+[send-to-dla-on-no-route](queue-attributes.md "Configuring Queues Via Address Settings") | Forward messages to DLA when no queues subscribing. default=false
#bridge type
Name | Description
:--- | :---
-[name ](core-bridges.md "Chapter 36. Core Bridges") | unique name
-[queue-name](core-bridges.md "Chapter 36. Core Bridges") | name of queue that this bridge consumes from
-[forwarding-address](core-bridges.md "Chapter 36. Core Bridges") | address to forward to. If omitted original address is used
-[ha](core-bridges.md "Chapter 36. Core Bridges") | whether this bridge supports fail-over
-[filter](core-bridges.md "Chapter 36. Core Bridges") | optional core filter expression
-[transformer-class-name](core-bridges.md "Chapter 36. Core Bridges") | optional name of transformer class
-[min-large-message-size](core-bridges.md "Chapter 36. Core Bridges") | Limit before message is considered large. default 100KB
-[check-period](connection-ttl.md "Chapter 17. Detecting Dead Connections") | [TTL](http://en.wikipedia.org/wiki/Time_to_live "Time to Live") check period for the bridge. -1 means disabled. default 30000 (ms)
-[connection-ttl](connection-ttl.md "Chapter 17. Detecting Dead Connections") | [TTL](http://en.wikipedia.org/wiki/Time_to_live "Time to Live") for the Bridge. This should be greater than the ping period. default 60000 (ms)
-[retry-interval](core-bridges.md "Chapter 36. Core Bridges") | period (in ms) between successive retries. default 2000
-[retry-interval-multiplier](core-bridges.md "Chapter 36. Core Bridges") | multiplier to apply to successive retry intervals. default 1
-[max-retry-interval](core-bridges.md "Chapter 36. Core Bridges") | Limit to the retry-interval growth. default 2000
-[reconnect-attempts](core-bridges.md "Chapter 36. Core Bridges") | maximum number of retry attempts, -1 means 'no limits'. default -1
-[use-duplicate-detection](core-bridges.md "Chapter 36. Core Bridges") | forward duplicate detection headers?. default true
-[confirmation-window-size](core-bridges.md "Chapter 36. Core Bridges") | number of bytes before confirmations are sent. default 1MB
-[producer-window-size](core-bridges.md "Chapter 36. Core Bridges") | Producer flow control size on the bridge. Default -1 (disabled)
-[user](core-bridges.md "Chapter 36. Core Bridges") | Username for the bridge, the default is the cluster username
-[password](core-bridges.md "Chapter 36. Core Bridges") | Password for the bridge, default is the cluster password
-[reconnect-attempts-same-node](core-bridges.md "Chapter 36. Core Bridges") | Number of retries before trying another node. default 10
+[name ](core-bridges.md "Core Bridges") | unique name
+[queue-name](core-bridges.md "Core Bridges") | name of queue that this bridge consumes from
+[forwarding-address](core-bridges.md "Core Bridges") | address to forward to. If omitted original address is used
+[ha](core-bridges.md "Core Bridges") | whether this bridge supports fail-over
+[filter](core-bridges.md "Core Bridges") | optional core filter expression
+[transformer-class-name](core-bridges.md "Core Bridges") | optional name of transformer class
+[min-large-message-size](core-bridges.md "Core Bridges") | Limit before message is considered large. default 100KB
+[check-period](connection-ttl.md "Detecting Dead Connections") | [TTL](http://en.wikipedia.org/wiki/Time_to_live "Time to Live") check period for the bridge. -1 means disabled. default 30000 (ms)
+[connection-ttl](connection-ttl.md "Detecting Dead Connections") | [TTL](http://en.wikipedia.org/wiki/Time_to_live "Time to Live") for the Bridge. This should be greater than the ping period. default 60000 (ms)
+[retry-interval](core-bridges.md "Core Bridges") | period (in ms) between successive retries. default 2000
+[retry-interval-multiplier](core-bridges.md "Core Bridges") | multiplier to apply to successive retry intervals. default 1
+[max-retry-interval](core-bridges.md "Core Bridges") | Limit to the retry-interval growth. default 2000
+[reconnect-attempts](core-bridges.md "Core Bridges") | maximum number of retry attempts, -1 means 'no limits'. default -1
+[use-duplicate-detection](core-bridges.md "Core Bridges") | forward duplicate detection headers?. default true
+[confirmation-window-size](core-bridges.md "Core Bridges") | number of bytes before confirmations are sent. default 1MB
+[producer-window-size](core-bridges.md "Core Bridges") | Producer flow control size on the bridge. Default -1 (disabled)
+[user](core-bridges.md "Core Bridges") | Username for the bridge, the default is the cluster username
+[password](core-bridges.md "Core Bridges") | Password for the bridge, default is the cluster password
+[reconnect-attempts-same-node](core-bridges.md "Core Bridges") | Number of retries before trying another node. default 10
# broadcast-group type
Name | Type
:--- | :---
-[name ](clusters.md "Chapter 38. Clusters") | unique name
-[local-bind-address](clusters.md "Chapter 38. Clusters") | local bind address that the datagram socket is bound to
-[local-bind-port](clusters.md "Chapter 38. Clusters") | local port to which the datagram socket is bound to
-[group-address](clusters.md "Chapter 38. Clusters") | multicast address to which the data will be broadcast
-[group-port](clusters.md "Chapter 38. Clusters") | UDP port number used for broadcasting
-[broadcast-period](clusters.md "Chapter 38. Clusters") | period in milliseconds between consecutive broadcasts. default 2000
+[name ](clusters.md "Clusters") | unique name
+[local-bind-address](clusters.md "Clusters") | local bind address that the datagram socket is bound to
+[local-bind-port](clusters.md "Clusters") | local port to which the datagram socket is bound to
+[group-address](clusters.md "Clusters") | multicast address to which the data will be broadcast
+[group-port](clusters.md "Clusters") | UDP port number used for broadcasting
+[broadcast-period](clusters.md "Clusters") | period in milliseconds between consecutive broadcasts. default 2000
[jgroups-file](clusters.md) | Name of JGroups configuration file
[jgroups-channel](clusters.md) | Name of JGroups Channel
-[connector-ref](clusters.md "Chapter 38. Clusters") |
+[connector-ref](clusters.md "Clusters") |
#cluster-connection type
Name | Description
:--- | :---
-[name](clusters.md "Chapter 38. Clusters") | unique name
-[address](clusters.md "Chapter 38. Clusters") | name of the address this cluster connection applies to
-[connector-ref](clusters.md "Chapter 38. Clusters") | Name of the connector reference to use.
-[check-period](connection-ttl.md "Chapter 17. Detecting Dead Connections") | The period (in milliseconds) used to check if the cluster connection has failed to receive pings from another server with default = 30000
-[connection-ttl](connection-ttl.md "Chapter 17. Detecting Dead Connections") | Timeout for TTL. Default 60000
-[min-large-message-size](large-messages.md "Chapter 23. Large Messages") | Messages larger than this are considered large-messages, default=100KB
-[call-timeout](clusters.md "Chapter 38. Clusters") | Time(ms) before giving up on blocked calls. Default=30000
-[retry-interval](clusters.md "Chapter 38. Clusters") | period (in ms) between successive retries. Default=500
-[retry-interval-multiplier](clusters.md "Chapter 38. Clusters") | multiplier to apply to the retry-interval. Default=1
-[max-retry-interval](clusters.md "Chapter 38. Clusters") | Maximum value for retry-interval. Default=2000
-[reconnect-attempts](clusters.md "Chapter 38. Clusters") | How many attempts should be made to reconnect after failure. Default=-1
-[use-duplicate-detection](clusters.md "Chapter 38. Clusters") | should duplicate detection headers be inserted in forwarded messages?. Default=true
-[forward-when-no-consumers](clusters.md "Chapter 38. Clusters") | should messages be load balanced if there are no matching consumers on target? Default=false
-[max-hops](clusters.md "Chapter 38. Clusters") | maximum number of hops cluster topology is propagated. Default=1
-[confirmation-window-size](client-reconnection.md "Chapter 34. Client Reconnection and Session Reattachment")| The size (in bytes) of the window used for confirming data from the server connected to. Default 1048576
-[producer-window-size](clusters.md "Chapter 38. Clusters") | Flow Control for the Cluster connection bridge. Default -1 (disabled)
-[call-failover-timeout](clusters.md "38.3.1. Configuring Cluster Connections") | How long to wait for a reply if in the middle of a fail-over. -1 means wait forever. Default -1
-[notification-interval](clusters.md "Chapter 38. Clusters") | how often the cluster connection will notify the cluster of its existence right after joining the cluster. Default 1000
-[notification-attempts](clusters.md "Chapter 38. Clusters") | how many times this cluster connection will notify the cluster of its existence right after joining the cluster Default 2
+[name](clusters.md "Clusters") | unique name
+[address](clusters.md "Clusters") | name of the address this cluster connection applies to
+[connector-ref](clusters.md "Clusters") | Name of the connector reference to use.
+[check-period](connection-ttl.md "Detecting Dead Connections") | The period (in milliseconds) used to check if the cluster connection has failed to receive pings from another server with default = 30000
+[connection-ttl](connection-ttl.md "Detecting Dead Connections") | Timeout for TTL. Default 60000
+[min-large-message-size](large-messages.md "Large Messages") | Messages larger than this are considered large-messages, default=100KB
+[call-timeout](clusters.md "Clusters") | Time(ms) before giving up on blocked calls. Default=30000
+[retry-interval](clusters.md "Clusters") | period (in ms) between successive retries. Default=500
+[retry-interval-multiplier](clusters.md "Clusters") | multiplier to apply to the retry-interval. Default=1
+[max-retry-interval](clusters.md "Clusters") | Maximum value for retry-interval. Default=2000
+[reconnect-attempts](clusters.md "Clusters") | How many attempts should be made to reconnect after failure. Default=-1
+[use-duplicate-detection](clusters.md "Clusters") | should duplicate detection headers be inserted in forwarded messages?. Default=true
+[forward-when-no-consumers](clusters.md "Clusters") | should messages be load balanced if there are no matching consumers on target? Default=false
+[max-hops](clusters.md "Clusters") | maximum number of hops cluster topology is propagated. Default=1
+[confirmation-window-size](client-reconnection.md "Client Reconnection and Session Reattachment")| The size (in bytes) of the window used for confirming data from the server connected to. Default 1048576
+[producer-window-size](clusters.md "Clusters") | Flow Control for the Cluster connection bridge. Default -1 (disabled)
+[call-failover-timeout](clusters.md "Configuring Cluster Connections") | How long to wait for a reply if in the middle of a fail-over. -1 means wait forever. Default -1
+[notification-interval](clusters.md "Clusters") | how often the cluster connection will notify the cluster of its existence right after joining the cluster. Default 1000
+[notification-attempts](clusters.md "Clusters") | how many times this cluster connection will notify the cluster of its existence right after joining the cluster Default 2
#discovery-group type
Name | Description
:--- | :---
-[name](clusters.md "Chapter 38. Clusters") | unique name
-[group-address](clusters.md "Chapter 38. Clusters") | Multicast IP address of the group to listen on
-[group-port](clusters.md "Chapter 38. Clusters") | UDP port number of the multi cast group
+[name](clusters.md "Clusters") | unique name
+[group-address](clusters.md "Clusters") | Multicast IP address of the group to listen on
+[group-port](clusters.md "Clusters") | UDP port number of the multi cast group
[jgroups-file](clusters.md) | Name of a JGroups configuration file. If specified, the server uses JGroups for discovery.
[jgroups-channel](clusters.md) | Name of a JGroups Channel. If specified, the server uses the named channel for discovery.
[refresh-timeout]() | Period the discovery group waits after receiving the last broadcast from a particular server before removing that servers connector pair entry from its list. Default=10000
-[local-bind-address](clusters.md "Chapter 38. Clusters") | local bind address that the datagram socket is bound to
-[local-bind-port](clusters.md "Chapter 38. Clusters") | local port to which the datagram socket is bound to. Default=-1
+[local-bind-address](clusters.md "Clusters") | local bind address that the datagram socket is bound to
+[local-bind-port](clusters.md "Clusters") | local port to which the datagram socket is bound to. Default=-1
[initial-wait-timeout]() | time to wait for an initial broadcast to give us at least one node in the cluster. Default=10000
#divert type
Name | Description
:--- | :---
-[name](diverts.md "Chapter 35. Diverting and Splitting Message Flows") | unique name
-[transformer-class-name](diverts.md "Chapter 35. Diverting and Splitting Message Flows") | an optional class name of a transformer
-[exclusive](diverts.md "Chapter 35. Diverting and Splitting Message Flows") | whether this is an exclusive divert. Default=false
-[routing-name](diverts.md "Chapter 35. Diverting and Splitting Message Flows") | the routing name for the divert
-[address](diverts.md "Chapter 35. Diverting and Splitting Message Flows") | the address this divert will divert from
-[forwarding-address](diverts.md "Chapter 35. Diverting and Splitting Message Flows") | the forwarding address for the divert
-[filter](diverts.md "Chapter 35. Diverting and Splitting Message Flows")| optional core filter expression
+[name](diverts.md "Diverting and Splitting Message Flows") | unique name
+[transformer-class-name](diverts.md "Diverting and Splitting Message Flows") | an optional class name of a transformer
+[exclusive](diverts.md "Diverting and Splitting Message Flows") | whether this is an exclusive divert. Default=false
+[routing-name](diverts.md "Diverting and Splitting Message Flows") | the routing name for the divert
+[address](diverts.md "Diverting and Splitting Message Flows") | the address this divert will divert from
+[forwarding-address](diverts.md "Diverting and Splitting Message Flows") | the forwarding address for the divert
+[filter](diverts.md "Diverting and Splitting Message Flows")| optional core filter expression
#queue type
Name | Description
:--- | :---
-[name ](queue-attributes.md "25.1. Predefined Queues") | unique name
-[address](queue-attributes.md "25.1. Predefined Queues") | address for the queue
-[filter](queue-attributes.md "25.1. Predefined Queues") | optional core filter expression
-[durable](queue-attributes.md "25.1. Predefined Queues") | whether the queue is durable (persistent). Default=true
+[name ](queue-attributes.md "Predefined Queues") | unique name
+[address](queue-attributes.md "Predefined Queues") | address for the queue
+[filter](queue-attributes.md "Predefined Queues") | optional core filter expression
+[durable](queue-attributes.md "Predefined Queues") | whether the queue is durable (persistent). Default=true
#security-setting type
Name | Description
:--- | :---
-[match ](security.md "31.1. Role based security for addresses") | [address expression](wildcard-syntax.md)
-[permission](security.md "31.1. Role based security for addresses") |
-[permission.type ](security.md "31.1. Role based security for addresses") | the type of permission
-[permission.roles ](security.md "31.1. Role based security for addresses") | a comma-separated list of roles to apply the permission to
+[match ](security.md "Role based security for addresses") | [address expression](wildcard-syntax.md)
+[permission](security.md "Role based security for addresses") |
+[permission.type ](security.md "Role based security for addresses") | the type of permission
+[permission.roles ](security.md "Role based security for addresses") | a comma-separated list of roles to apply the permission to
----------------------------
@@ -224,12 +224,12 @@ Name | Description
Name | Type | Description
:--- | :--- | :---
-[queue](using-jms.md "7.2. JMS Server Configuration") | Queue | a queue
-[queue.name (attribute)](using-jms.md "7.2. JMS Server Configuration") | String | unique name of the queue
-[queue.durable](using-jms.md "7.2. JMS Server Configuration") | Boolean | is the queue durable?. Default=true
-[queue.filter](using-jms.md "7.2. JMS Server Configuration") | String | optional filter expression for the queue
-[topic](using-jms.md "7.2. JMS Server Configuration") | Topic | a topic
-[topic.name (attribute)](using-jms.md "7.2. JMS Server Configuration") | String | unique name of the topic
+[queue](using-jms.md "JMS Server Configuration") | Queue | a queue
+[queue.name (attribute)](using-jms.md "JMS Server Configuration") | String | unique name of the queue
+[queue.durable](using-jms.md "JMS Server Configuration") | Boolean | is the queue durable?. Default=true
+[queue.filter](using-jms.md "JMS Server Configuration") | String | optional filter expression for the queue
+[topic](using-jms.md "JMS Server Configuration") | Topic | a topic
+[topic.name (attribute)](using-jms.md "JMS Server Configuration") | String | unique name of the topic
Using Masked Passwords in Configuration Files