Element Summary

Represents an entry in a {@link DefaultAuthorizationMap} for assigning
different operations (read, write, admin) of user roles to a specific
destination or a hierarchical wildcard area of destinations.

Represents a destination based configuration of policies so that individual
destinations or wildcard hierarchies of destinations can be configured using
different policies. Each entry in the map represents the authorization ACLs for each operation.

Axion specific Adapter.
Axion does not seem to support ALTER statements or sub-selects. This means:
- We cannot auto upgrade the schema was we roll out new versions of ActiveMQ
- We cannot delete durable sub messages that have be acknowledged by all consumers.

This JDBCAdapter inserts and extracts BLOB data using the
getBlob()/setBlob() operations. This is a little more involved
since to insert a blob you have to:
1: insert empty blob.
2: select the blob
3: finally update the blob with data value.
The databases/JDBC drivers that use this adapter are:

A Spring enhanced connection
factory which will automatically use the Spring bean name as the clientIDPrefix property
so that connections created have client IDs related to your Spring.xml file for
easier comprehension from JMX.

JDBC Adapter for Informix database.
Because Informix database restricts length of composite primary keys, length of
container name field and subscription id field must be reduced to 150 characters.
Therefore be sure not to use longer names for container name and subscription id than 150 characters.

A {@link PersistenceAdapter} implementation using JDBC for persistence
storage.
This persistence adapter will correctly remember prepared XA transactions,
but it will not keep track of local transaction commits so that operations
performed against the Message store are done as a single uow.

A network connector which uses some kind of multicast-like transport that
communicates with potentially many remote brokers over a single logical
{@link Transport} instance such as when using multicast.
This implementation does not depend on multicast at all; any other group
based transport could be used.

A Spring enhanced XA connection
factory which will automatically use the Spring bean name as the clientIDPrefix property
so that connections created have client IDs related to your Spring.xml file for
easier comprehension from JMX.

Allows the support of advisory messages to be disabled for performance reasons.

brokerName

xs:string

Sets the name of this broker; which must be unique in the network

brokerObjectName

xs:string

Sets the JMX ObjectName for this broker

dataDirectory

xs:string

Sets the directory in which the data files will be stored by default for
the JDBC and Journal persistence adaptors.

deleteAllMessagesOnStartup

xs:boolean

Sets whether or not all messages are deleted on startup - mostly only
useful for testing.

keepDurableSubsActive

xs:boolean

masterConnectorURI

xs:string

persistenceThreadPriority

xs:integer

persistent

xs:boolean

Sets whether or not persistence is enabled or disabled.

populateJMSXUserID

xs:boolean

Sets whether or not the broker should populate the JMSXUserID header.

shutdownOnMasterFailure

xs:boolean

start

xs:boolean

Sets whether or not the broker is started along with the ApplicationContext it is defined within.
Normally you would want the broker to start up along with the ApplicationContext but sometimes when working
with JUnit tests you may wish to start and stop the broker explicitly yourself.

tmpDataDirectory

xs:string

useJmx

xs:boolean

Sets whether or not the Broker's services should be exposed into JMX or
not.

useLoggingForShutdownErrors

xs:boolean

Sets whether or not we should use commons-logging when reporting errors
when shutting down the broker

useShutdownHook

xs:boolean

Sets whether or not we should use a shutdown handler to close down the
broker cleanly if the JVM is terminated. It is recommended you leave this
enabled.

useVirtualTopics

xs:boolean

Sets whether or not
Virtual Topics
should be supported by default if they have not been explicitly configured.

vmConnectorURI

xs:string

Element

Type

Description

adminView

<spring:bean/>

Returns the administration view of the broker; used to create and destroy resources such as queues and topics.
Note this method returns null if JMX is disabled.

If this flag is set then a separate thread is not used for dispatching
messages for each Session in the Connection. However, a separate thread
is always used if there is more than one session, or the session isn't in
auto acknowledge or duplicates ok mode

Sets the JMS clientID to use for the created connection. Note that this can only be used by one connection at once so generally its a better idea
to set the clientID on a Connection

clientIDPrefix

xs:string

Sets the prefix used by autogenerated JMS Client ID values which are
used if the JMS client does not explicitly specify on.

closeTimeout

xs:integer

Sets the timeout before a close is considered complete. Normally a
close() on a connection waits for confirmation from the broker; this
allows that operation to timeout to save the client hanging if there is
no broker

copyMessageOnSend

xs:boolean

Should a JMS message be copied to a new JMS Message object as part of the
send() method in JMS. This is enabled by default to be compliant with the
JMS specification. You can disable it if you do not mutate JMS messages
after they are sent for a performance boost

disableTimeStampsByDefault

xs:boolean

Sets whether or not timestamps on messages should be disabled or not. If
you disable them it adds a small performance boost.

dispatchAsync

xs:boolean

Enables or disables the default setting of whether or not consumers have
their messages dispatched
synchronously or asynchronously by the broker.
For non-durable topics for example we typically dispatch synchronously by
default to minimize context switches which boost performance. However
sometimes its better to go slower to ensure that a single blocked
consumer socket does not block delivery to other consumers.

nestedMapAndListEnabled

xs:boolean

Enables/disables whether or not Message properties and MapMessage entries
support Nested
Structures of Map and List objects

objectMessageSerializationDefered

xs:boolean

When an object is set on an ObjectMessage, the JMS spec requires the
object to be serialized by that set method. Enabling this flag causes the
object to not get serialized. The object may subsequently get serialized
if the message needs to be sent over a socket or stored to disk.

optimizeAcknowledge

xs:boolean

optimizedMessageDispatch

xs:boolean

If this flag is set then an larger prefetch limit is used - only
applicable for durable topic subscribers.

password

xs:string

Sets the JMS password used for connections created from this factory

statsEnabled

xs:boolean

useAsyncSend

xs:boolean

Forces the use of Async Sends
which adds a massive performance boost; but means that the send() method
will return immediately whether the message has been sent or not which
could lead to message loss.

useBeanNameAsClientIdPrefix

xs:boolean

useCompression

xs:boolean

Enables the use of compression of the message bodies

useRetroactiveConsumer

xs:boolean

Sets whether or not retroactive consumers are enabled. Retroactive consumers allow
non-durable topic subscribers to receive old messages that were published before the
non-durable subscriber started.

Enables or disables the auto-discovery of the login.config file for JAAS to initialize itself.
This flag is enabled by default such that if the java.security.auth.login.config system property
is not defined then it is set to the location of the login.config file on the classpath.

Enables or disables the auto-discovery of the login.config file for JAAS to initialize itself.
This flag is enabled by default such that if the java.security.auth.login.config system property
is not defined then it is set to the location of the login.config file on the classpath.

Sets whether or not an exclusive database lock should be used to enable JDBC Master/Slave. Enabled by default.

useJournal

xs:boolean

Enables or disables the use of the journal. The default is to use the journal

useQuickJournal

xs:boolean

Enables or disables the use of quick journal, which keeps messages in the journal and just
stores a reference to the messages in JDBC. Defaults to false so that messages actually reside
long term in the JDBC database.

Sets the number of hash buckets to use for the message group
functionality. This is only applicable to using message groups to
parallelize processing of a queue while preserving order across an
individual JMSXGroupID header value. This value sets the number of hash
buckets that will be used (i.e. the maximum possible concurrency).

Sets the strategy to calculate the maximum number of messages that are
allowed to be pending on consumers (in addition to their prefetch sizes).
Once the limit is reached, non-durable topics can then start discarding
old messages. This allows us to keep dispatching messages to slow
consumers while not blocking fast consumers and discarding the messages
oldest first.

Sets the server transport URI to use if there is not a
{@link TransportServer} configured via the
{@link #setServer(TransportServer)} method. This value is used to lazy
create a {@link TransportServer} instance

If this flag is set then a separate thread is not used for dispatching
messages for each Session in the Connection. However, a separate thread
is always used if there is more than one session, or the session isn't in
auto acknowledge or duplicates ok mode

Sets the JMS clientID to use for the created connection. Note that this can only be used by one connection at once so generally its a better idea
to set the clientID on a Connection

clientIDPrefix

xs:string

Sets the prefix used by autogenerated JMS Client ID values which are
used if the JMS client does not explicitly specify on.

closeTimeout

xs:integer

Sets the timeout before a close is considered complete. Normally a
close() on a connection waits for confirmation from the broker; this
allows that operation to timeout to save the client hanging if there is
no broker

copyMessageOnSend

xs:boolean

Should a JMS message be copied to a new JMS Message object as part of the
send() method in JMS. This is enabled by default to be compliant with the
JMS specification. You can disable it if you do not mutate JMS messages
after they are sent for a performance boost

disableTimeStampsByDefault

xs:boolean

Sets whether or not timestamps on messages should be disabled or not. If
you disable them it adds a small performance boost.

dispatchAsync

xs:boolean

Enables or disables the default setting of whether or not consumers have
their messages dispatched
synchronously or asynchronously by the broker.
For non-durable topics for example we typically dispatch synchronously by
default to minimize context switches which boost performance. However
sometimes its better to go slower to ensure that a single blocked
consumer socket does not block delivery to other consumers.

nestedMapAndListEnabled

xs:boolean

Enables/disables whether or not Message properties and MapMessage entries
support Nested
Structures of Map and List objects

objectMessageSerializationDefered

xs:boolean

When an object is set on an ObjectMessage, the JMS spec requires the
object to be serialized by that set method. Enabling this flag causes the
object to not get serialized. The object may subsequently get serialized
if the message needs to be sent over a socket or stored to disk.

optimizeAcknowledge

xs:boolean

optimizedMessageDispatch

xs:boolean

If this flag is set then an larger prefetch limit is used - only
applicable for durable topic subscribers.

password

xs:string

Sets the JMS password used for connections created from this factory

statsEnabled

xs:boolean

useAsyncSend

xs:boolean

Forces the use of Async Sends
which adds a massive performance boost; but means that the send() method
will return immediately whether the message has been sent or not which
could lead to message loss.

useBeanNameAsClientIdPrefix

xs:boolean

useCompression

xs:boolean

Enables the use of compression of the message bodies

useRetroactiveConsumer

xs:boolean

Sets whether or not retroactive consumers are enabled. Retroactive consumers allow
non-durable topic subscribers to receive old messages that were published before the
non-durable subscriber started.