From d2b668adf3653e3e34047d3d2a4d978ef3076250 Mon Sep 17 00:00:00 2001 From: Andy Taylor Date: Tue, 20 Jan 2015 15:54:49 +0000 Subject: [PATCH] documentation updates --- docs/user-manual/en/architecture.md | 4 +- docs/user-manual/en/client-reconnection.md | 2 +- docs/user-manual/en/configuration-index.md | 1780 +++++++++++++++++++- 3 files changed, 1775 insertions(+), 11 deletions(-) diff --git a/docs/user-manual/en/architecture.md b/docs/user-manual/en/architecture.md index 7e148ff40d..5c12cf450e 100644 --- a/docs/user-manual/en/architecture.md +++ b/docs/user-manual/en/architecture.md @@ -126,8 +126,8 @@ The standard stand-alone messaging server configuration comprises a core messaging server and a JMS service. The role of the JMS Service is to deploy any JMS Queue, Topic and -ConnectionFactory instances from any server side `activemq-jms.xml` -configuration files. It also provides a simple management API for +ConnectionFactory instances from any server side JMS +configuration. It also provides a simple management API for creating and destroying Queues and Topics which can be accessed via JMX or the connection. It is a separate service to the ActiveMQ core server, since the core server is JMS diff --git a/docs/user-manual/en/client-reconnection.md b/docs/user-manual/en/client-reconnection.md index de434b8798..e3d4720af1 100644 --- a/docs/user-manual/en/client-reconnection.md +++ b/docs/user-manual/en/client-reconnection.md @@ -36,7 +36,7 @@ to the client, and the client can then free up space in the buffer. If you are using JMS and you're using the JMS service on the server to load your JMS connection factory instances into JNDI then this parameter -can be configured in `activemq-jms.xml` using the element +can be configured in the jms configuration using the element `confirmation-window-size` a. If you're using JMS but not using JNDI then you can set these values directly on the `ActiveMQConnectionFactory` instance using the appropriate setter diff --git a/docs/user-manual/en/configuration-index.md b/docs/user-manual/en/configuration-index.md index 116bb57103..3d9d4781af 100644 --- a/docs/user-manual/en/configuration-index.md +++ b/docs/user-manual/en/configuration-index.md @@ -10,13 +10,1776 @@ Server Configuration activemq-configuration.xml -------------------------- -This is the main core server configuration file. +This is the main core server configuration file which contains to elements +'core' and 'jms'. +The 'core' element contains the main server configuration while the 'jms' +element is used by the server side JMS service to load JMS Queues, Topics -activemq-jms.xml ----------------- +# The core configuration -This is the configuration file used by the server side JMS service to -load JMS Queues, Topics and Connection Factories. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Element NameElement TypeDescriptionDefault
+ acceptors + Sequence of <acceptor/>a list of remoting acceptors to create
+ acceptors.acceptor + Complex element
+ acceptors.acceptor.name (attribute) + xsd:stringName of the acceptor
+ acceptors.acceptor.factory-class + xsd:stringName of the AcceptorFactory implementation
+ acceptors.acceptor.param + Complex elementA key-value pair used to configure the acceptor. An acceptor can have many param
+ acceptors.acceptor.param.key (required attribute) + xsd:stringKey of a configuration parameter
+ acceptors.acceptor.param.value (required attribute) + xsd:stringValue of a configuration parameter
+ address-settings + Sequence of <address-setting/>a list of address settings
+ address-settings.address-setting + Complex element
+ address-settings.address-setting.match (required + attribute) + xsd:stringXXX
+ address-settings.address-setting.dead-letter-address + xsd:stringthe address to send dead messages to
+ address-settings.address-setting.expiry-address + xsd:stringthe address to send expired messages to
+ address-settings.address-setting.expiry-delay + xsd:longOverrides the expiration time for messages using the default value for expiration time. "-1" disables this + setting. + -1
+ address-settings.address-setting.redelivery-delay + xsd:longthe time (in ms) to wait before redelivering a cancelled message.0
+ address-settings.address-setting.redelivery-delay-multiplier + xsd:doublemultipler to apply to the "redelivery-delay"
+ address-settings.address-setting.max-redelivery-delay + xsd:longMaximum value for the redelivery-delay
+ address-settings.address-setting.max-delivery-attempts + xsd:inthow many times to attempt to deliver a message before sending to dead letter address10
+ address-settings.address-setting.max-size-bytes + xsd:longthe maximum size (in bytes) to use in paging for an address (-1 means no limits)-1
+ address-settings.address-setting.page-size-bytes + xsd:longthe page size (in bytes) to use for an address10485760 (10 * 1024 * 1024)
+ address-settings.address-setting.page-max-cache-size + xsd:intNumber of paging files to cache in memory to avoid IO during paging navigation5
+ address-settings.address-setting.address-full-policy + DROP|FAIL|PAGE|BLOCKwhat happens when an address where "max-size-bytes" is specified becomes full
+ address-settings.address-setting.message-counter-history-day-limit + xsd:inthow many days to keep message counter history for this address0 (days)
+ address-settings.address-setting.last-value-queue + xsd:booleanwhether to treat the queue as a last value queuefalse
+ address-settings.address-setting.redistribution-delay + xsd:longhow long (in ms) to wait after the last consumer is closed on a queue before redistributing messages.-1
+ address-settings.address-setting.send-to-dla-on-no-route + xsd:booleanif there are no queues matching this address, whether to forward message to DLA (if it exists for this + address) +
+ allow-failback + xsd:booleanWhether a server will automatically stop when a another places a request to take over its place. The use + case is when a regular server stops and its backup takes over its duties, later the main server restarts and + requests the server (the former backup) to stop operating. + true
+ async-connection-execution-enabled + xsd:booleanShould incoming packets on the server be handed off to a thread from the thread pool for processing or + should they be handled on the remoting thread? + true
+ bindings-directory + xsd:stringthe directory to store the persisted bindings todata/bindings
+ bridges + Sequence of <bridge/>a list of bridges to create
+ bridges.bridge + Complex element
+ bridges.bridge.name (required + attribute) + xsd:IDunique name for this bridge
+ bridges.bridge.queue-name + xsd:IDREFname of queue that this bridge consumes from
+ bridges.bridge.forwarding-address + xsd:stringaddress to forward to. If omitted original address is used
+ bridges.bridge.ha + xsd:booleanwhether this bridge supports fail-overfalse
+ bridges.bridge.filter + Complex element
+ bridges.bridge.filter.string + (required attribute) + xsd:stringoptional core filter expression
+ bridges.bridge.transformer-class-name + xsd:stringoptional name of transformer class
+ bridges.bridge.min-large-message-size + xsd:intAny message larger than this size is considered a large message (to be sent in chunks)102400 (bytes)
+ bridges.bridge.check-period + xsd:longThe period (in milliseconds) a bridge's client will check if it failed to receive a ping from the server. -1 + disables this check. + 30000 (ms)
+ bridges.bridge.connection-ttl + xsd:longhow long to keep a connection alive in the absence of any data arriving from the client. This should be + greater than the ping period. + 60000 (ms)
+ bridges.bridge.retry-interval + xsd:longperiod (in ms) between successive retries2000 (in milliseconds)
+ bridges.bridge.retry-interval-multiplier + xsd:doublemultiplier to apply to successive retry intervals1
+ bridges.bridge.max-retry-interval + xsd:longLimit to the retry-interval growth (due to retry-interval-multiplier)2000
+ bridges.bridge.reconnect-attempts + xsd:intmaximum number of retry attempts, -1 means 'no limits'-1
+ bridges.bridge.use-duplicate-detection + xsd:booleanshould duplicate detection headers be inserted in forwarded messages?true
+ bridges.bridge.confirmation-window-size + xsd:intOnce the bridge has received this many bytes, it sends a confirmation(bytes, 1024 * 1024)
+ bridges.bridge.user + xsd:stringusername, if unspecified the cluster-user is used
+ bridges.bridge.password + xsd:stringpassword, if unspecified the cluster-password is used
+ bridges.bridge.reconnect-attempts-same-node + xsd:intUpon reconnection this configures the number of time the same node on the topology will be retried before + reseting the server locator and using the initial connectors + 10 (int, 10)
+ broadcast-groups + Sequence of <broadcast-group/>a list of broadcast groups to create
+ broadcast-groups.broadcast-group + Complex element
+ broadcast-groups.broadcast-group.name + (required attribute) + xsd:IDa unique name for the broadcast group
+ broadcast-groups.broadcast-group.local-bind-address + xsd:stringlocal bind address that the datagram socket is bound towildcard IP address chosen by the kernel
+ broadcast-groups.broadcast-group.local-bind-port + xsd:intlocal port to which the datagram socket is bound to-1 (anonymous port)
+ broadcast-groups.broadcast-group.group-address + xsd:stringmulticast address to which the data will be broadcast
+ broadcast-groups.broadcast-group.group-port + xsd:intUDP port number used for broadcasting
+ broadcast-groups.broadcast-group.broadcast-period + xsd:longperiod in milliseconds between consecutive broadcasts2000 (in milliseconds)
+ broadcast-groups.broadcast-group.jgroups-file + xsd:stringName of JGroups configuration file. If specified, the server uses JGroups for broadcasting.
+ broadcast-groups.broadcast-group.jgroups-channel + xsd:stringName of JGroups Channel. If specified, the server uses the named channel for broadcasting.
+ broadcast-groups.broadcast-group.connector-ref + xsd:string
+ check-for-live-server + xsd:booleanWhether to check the cluster for a (live) server using our own server ID when starting up. This option is + only necessary for performing 'fail-back' on replicating servers. Strictly speaking this setting only + applies to live servers and not to backups. + false
+ cluster-connections + Sequence of <cluster-connection/>a list of cluster connections
+ cluster-connections.cluster-connection + Complex element
+ cluster-connections.cluster-connection.name + (required attribute) + xsd:IDunique name for this cluster connection
+ cluster-connections.cluster-connection.address + xsd:stringname of the address this cluster connection applies to
+ cluster-connections.cluster-connection.connector-ref + xsd:stringName of the connector reference to use.
+ cluster-connections.cluster-connection.check-period + xsd:longThe period (in milliseconds) used to check if the cluster connection has failed to receive pings from + another server + 30000 (ms)
+ cluster-connections.cluster-connection.connection-ttl + xsd:longhow long to keep a connection alive in the absence of any data arriving from the client60000 (ms)
+ cluster-connections.cluster-connection.min-large-message-size + xsd:intMessages larger than this are considered large-messages(bytes)
+ cluster-connections.cluster-connection.call-timeout + xsd:longHow long to wait for a reply30000 (ms)
+ cluster-connections.cluster-connection.retry-interval + xsd:longperiod (in ms) between successive retries500
+ cluster-connections.cluster-connection.retry-interval-multiplier + xsd:doublemultiplier to apply to the retry-interval1
+ cluster-connections.cluster-connection.max-retry-interval + xsd:longMaximum value for retry-interval2000
+ cluster-connections.cluster-connection.reconnect-attempts + xsd:intHow many attempts should be made to reconnect after failure-1
+ cluster-connections.cluster-connection.use-duplicate-detection + xsd:booleanshould duplicate detection headers be inserted in forwarded messages?true
+ cluster-connections.cluster-connection.forward-when-no-consumers + xsd:booleanshould messages be load balanced if there are no matching consumers on target?false
+ cluster-connections.cluster-connection.max-hops + xsd:intmaximum number of hops cluster topology is propagated1
+ cluster-connections.cluster-connection.confirmation-window-size + xsd:intThe size (in bytes) of the window used for confirming data from the server connected to.1048576
+ cluster-connections.cluster-connection.call-failover-timeout + xsd:longHow long to wait for a reply if in the middle of a fail-over. -1 means wait forever.-1 (ms)
+ cluster-connections.cluster-connection.notification-interval + xsd:longhow often the cluster connection will notify the cluster of its existence right after joining the cluster + 1000 (ms)
+ cluster-connections.cluster-connection.notification-attempts + xsd:inthow many times this cluster connection will notify the cluster of its existence right after joining the + cluster + 2
+ clustered + xsd:booleanDEPRECATED. This option is deprecated and its value will be ignored (HQ221038). A HornetQ server will be + "clustered" when its configuration contain a cluster-configuration. + false
+ cluster-password + xsd:stringCluster password. It applies to all cluster configurations.CHANGE ME!!
+ cluster-user + xsd:stringCluster username. It applies to all cluster configurations.HORNETQ.CLUSTER.ADMIN.USER
+ connection-ttl-override + xsd:longif set, this will override how long (in ms) to keep a connection alive without receiving a ping. -1 disables + this setting. + -1
+ connectors + Sequence of <connector/>a list of remoting connectors configurations to create
+ connectors.connector + Complex element
+ connectors.connector.name (required attribute) + xsd:IDName of the connector
+ connectors.connector.factory-class + xsd:stringName of the ConnectorFactory implementation
+ connectors.connector.param + Complex elementA key-value pair used to configure the connector. A connector can have many param's
+ connectors.connector.param.key (required attribute) + xsd:stringKey of a configuration parameter
+ connectors.connector.param.value (required attribute) + xsd:stringValue of a configuration parameter
+ connector-services + Sequence of <connector-service/>
+ connector-services.connector-service + Complex element
+ connector-services.connector-service.name (attribute) + xsd:stringname of the connector service
+ connector-services.connector-service.factory-class + xsd:stringName of the factory class of the ConnectorService
+ connector-services.connector-service.param + Complex element
+ connector-services.connector-service.param.key (required attribute) + xsd:stringKey of a configuration parameter
+ connector-services.connector-service.param.value (required attribute) + xsd:stringValue of a configuration parameter
+ create-bindings-dir + xsd:booleantrue means that the server will create the bindings directory on start uptrue
+ create-journal-dir + xsd:booleantrue means that the journal directory will be createdtrue
+ discovery-groups + Sequence of <discovery-group/>a list of discovery groups to create
+ discovery-groups.discovery-group + Complex element
+ discovery-groups.discovery-group.name + (required attribute) + xsd:IDa unique name for the discovery group
+ discovery-groups.discovery-group.group-address + xsd:stringMulticast IP address of the group to listen on
+ discovery-groups.discovery-group.group-port + xsd:intUDP port number of the multi cast group
+ discovery-groups.discovery-group.jgroups-file + xsd:stringName of a JGroups configuration file. If specified, the server uses JGroups for discovery.
+ discovery-groups.discovery-group.jgroups-channel + xsd:stringName of a JGroups Channel. If specified, the server uses the named channel for discovery.
+ discovery-groups.discovery-group.refresh-timeout + xsd:intPeriod the discovery group waits after receiving the last broadcast from a particular server before removing + that servers connector pair entry from its list. + 10000 (in milliseconds)
+ discovery-groups.discovery-group.local-bind-address + xsd:stringlocal bind address that the datagram socket is bound towildcard IP address chosen by the kernel
+ discovery-groups.discovery-group.local-bind-port + xsd:intlocal port to which the datagram socket is bound to-1 (anonymous port)
+ discovery-groups.discovery-group.initial-wait-timeout + xsd:inttime to wait for an initial broadcast to give us at least one node in the cluster10000 (milliseconds)
+ diverts + Sequence of <divert/>a list of diverts to use
+ diverts.divert + Complex element
+ diverts.divert.name + (required attribute) + xsd:IDa unique name for the divert
+ diverts.divert.transformer-class-name + xsd:stringan optional class name of a transformer
+ diverts.divert.exclusive + xsd:booleanwhether this is an exclusive divertfalse
+ diverts.divert.routing-name + xsd:stringthe routing name for the divert
+ diverts.divert.address + xsd:stringthe address this divert will divert from
+ diverts.divert.forwarding-address + xsd:stringthe forwarding address for the divert
+ diverts.divert.filter + Complex element
+ diverts.divert.filter.string + (required attribute) + xsd:stringoptional core filter expression
+ grouping-handler + Complex elementMessage Group configuration
+ grouping-handler.name + (required attribute) + xsd:stringA name identifying this grouping-handler
+ grouping-handler.type + LOCAL|REMOTEEach cluster should choose 1 node to have a LOCAL grouping handler and all the other nodes should have + REMOTE handlers +
+ grouping-handler.address + xsd:stringA reference to a cluster connection address
+ grouping-handler.timeout + xsd:intHow long to wait for a decision5000 (ms)
+ grouping-handler.group-timeout + xsd:intHow long a group binding will be used, -1 means for ever. Bindings are removed after this wait elapses. Only + valid for LOCAL handlers + -1 (ms)
+ grouping-handler.reaper-period + xsd:longHow often the reaper will be run to check for timed out group bindings. Only valid for LOCAL handlers30000 (ms)
+ id-cache-size + xsd:intthe size of the cache for pre-creating message ID's20000
+ jmx-domain + xsd:stringthe JMX domain used to registered HornetQ MBeans in the MBeanServerorg.hornetq
+ jmx-management-enabled + xsd:booleantrue means that the management API is available via JMXtrue
+ journal-buffer-size + xsd:longThe size of the internal buffer on the journal in KiB.501760 (490 KiB)
+ journal-buffer-timeout + xsd:longThe timeout (in nanoseconds) used to flush internal buffers on the journal. The exact default value depend + on whether the journal is ASYNCIO or NIO. +
+ journal-compact-min-files + xsd:intThe minimal number of data files before we can start compacting10
+ journal-compact-percentage + xsd:intThe percentage of live data on which we consider compacting the journal30
+ journal-directory + xsd:stringthe directory to store the journal files indata/journal
+ journal-file-size + xsd:intthe size (in bytes) of each journal file10485760 (10 * 1024 * 1024 - 10 MiB)
+ journal-max-io + xsd:intthe maximum number of write requests that can be in the AIO queue at any one time. Default is 500 for AIO + and 1 for NIO. +
+ journal-min-files + xsd:inthow many journal files to pre-create2
+ journal-sync-non-transactional + xsd:booleanif true wait for non transaction data to be synced to the journal before returning response to client.true
+ journal-sync-transactional + xsd:booleanif true wait for transaction data to be synchronized to the journal before returning response to clienttrue
+ journal-type + ASYNCIO|NIOthe type of journal to useASYNCIO
+ large-messages-directory + xsd:stringthe directory to store large messagesdata/largemessages
+ log-delegate-factory-class-name + xsd:stringXXX
+ log-journal-write-rate + xsd:booleanWhether to log messages about the journal write ratefalse
+ management-address + xsd:stringthe 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. + jms.queue.hornetq.management
+ management-notification-address + xsd:stringthe name of the address that consumers bind to receive management notificationshornetq.notifications
+ mask-password + xsd:booleanThis option controls whether passwords in server configuration need be masked. If set to "true" the + passwords are masked. + false
+ max-saved-replicated-journals-size + xsd:intThis 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. + 2
+ memory-measure-interval + xsd:longfrequency to sample JVM memory in ms (or -1 to disable memory sampling)-1 (ms)
+ memory-warning-threshold + xsd:intPercentage of available memory which will trigger a warning log25
+ message-counter-enabled + xsd:booleantrue means that message counters are enabledfalse
+ message-counter-max-day-history + xsd:inthow many days to keep message counter history10 (days)
+ message-counter-sample-period + xsd:longthe sample period (in ms) to use for message counters10000
+ message-expiry-scan-period + xsd:longhow often (in ms) to scan for expired messages30000
+ message-expiry-thread-priority + xsd:intthe priority of the thread expiring messages3
+ name + xsd:stringNode name. If set, it will be used in topology notifications.
+ page-max-concurrent-io + xsd:intThe max number of concurrent reads allowed on paging5
+ paging-directory + xsd:stringthe directory to store paged messages indata/paging
+ password-codec + xsd:stringClass name and its parameters for the Decoder used to decode the masked password. Ignored if mask-password + is false. The format of this property is a full qualified class name optionally followed by key/value pairs. + org.hornetq.utils.DefaultSensitiveStringCodec
+ perf-blast-pages + xsd:intXXX Only meant to be used by project developers-1
+ persist-delivery-count-before-delivery + xsd:booleanTrue means that the delivery count is persisted before delivery. False means that this only happens after a + message has been cancelled. + false
+ persistence-enabled + xsd:booleantrue means that the server will use the file based journal for persistence.true
+ persist-id-cache + xsd:booleantrue means that ID's are persisted to the journaltrue
+ queues + Sequence of <queue/>a list of pre configured queues to create
+ queues.queue + Complex element
+ queues.queue.name + (required attribute) + xsd:IDunique name of this queue
+ queues.queue.address + xsd:stringaddress for the queue
+ queues.queue.filter + Complex element
+ queues.queue.filter.string + (required attribute) + xsd:stringoptional core filter expression
+ queues.queue.durable + xsd:booleanwhether the queue is durable (persistent)true
+ remoting-incoming-interceptors + Complex elementa list of <class-name/> elements with the names of classes to use for interceptor incoming remoting + packetsunlimited sequence of <class-name/>
+ remoting-incoming-interceptors.class-name + xsd:stringthe fully qualified name of the interceptor class
+ remoting-interceptors + Complex elementDEPRECATED. This option is deprecated, but it will still be honored. Any interceptor specified here will be + considered an "incoming" interceptor. See <remoting-incoming-interceptors> and <remoting-outgoing-interceptors>.unlimited + sequence of <class-name/>
+ remoting-interceptors.class-name + xsd:stringthe fully qualified name of the interceptor class
+ remoting-outgoing-interceptors + Complex elementa list of <class-name/> elements with the names of classes to use for interceptor outcoming remoting + packetsunlimited sequence of <class-name/>
+ remoting-outgoing-interceptors.class-name + xsd:stringthe fully qualified name of the interceptor class
+ resolveProtocols + xsd:booleanIf true then the HornetQ Server will make use of any Protocol Managers that are in available on the + classpath. If false then only the core protocol will be available, unless in Embedded mode where users can + inject their own Protocol Managers. + true
+ run-sync-speed-test + xsd:booleanXXX Only meant to be used by project developersfalse
+ scheduled-thread-pool-max-size + xsd:intMaximum number of threads to use for the scheduled thread pool5
+ security-enabled + xsd:booleantrue means that security is enabledtrue
+ security-invalidation-interval + xsd:longhow long (in ms) to wait before invalidating the security cache10000
+ security-settings + Sequence of <security-setting/>a list of security settings
+ security-settings.security-setting + Sequence of <permission/>
+ security-settings.security-setting.match (required + attribute) + xsd:stringregular expression for matching security roles against addresses
+ security-settings.security-setting.permission + Complex element
+ security-settings.security-setting.permission.type + (required attribute) + xsd:stringthe type of permission
+ security-settings.security-setting.permission.roles + (required attribute) + xsd:stringa comma-separated list of roles to apply the permission to
+ server-dump-interval + xsd:longInterval to log server specific information (e.g. memory usage etc)-1 (ms)
+ thread-pool-max-size + xsd:intMaximum number of threads to use for the thread pool. -1 means 'no limits'.30
+ transaction-timeout + xsd:longhow long (in ms) before a transaction can be removed from the resource manager after create time300000
+ transaction-timeout-scan-period + xsd:longhow often (in ms) to scan for timeout transactions1000
+ wild-card-routing-enabled + xsd:booleantrue means that the server supports wild card routingtrue
+ +##The jms configuration + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Element NameElement TypeDescriptionDefault
queue + Queuea queue to create
queue.name + (attribute)Stringunique name of the queue
queue.durable + Booleanis the queue durable?true
queue.filter + Stringoptional filter expression for the queue
topic + Topica topic to create
topic.name + (attribute)Stringunique name of the topic
Using Masked Passwords in Configuration Files --------------------------------------------- @@ -163,11 +1926,12 @@ Bridges. Example: With this configuration, both passwords in ra.xml and all of its MDBs will have to be in masked form. -### Masking passwords in activemq-users.xml +### Masking passwords in activemq-users.properties -ActiveMQ's built-in security manager uses plain configuration files +ActiveMQ's built-in security manager uses plain properties files where the user passwords are specified in plaintext forms by default. To -mask those parameters the following two properties are needed: +mask those parameters the following two properties need to be set +in the 'bootstrap.xml' file. `mask-password` -- If set to "true" all the passwords are masked. Default is false.