]]>
Mirrored
Queues should be supported by default if they have not been
explicitly configured.
]]>
Virtual
Topics should be supported by default if they have not been
explicitly configured.
]]>
Mirrored
Queues should be supported by default if they have not been
explicitly configured.
]]>
Virtual
Topics should be supported by default if they have not been
explicitly configured.
]]>
DOT file creator plugin which
creates a DOT file showing the current connections
]]>
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.
]]>
Note: access to this clientInternalExceptionListener will not be serialized if it is associated with more than
on connection (as it will be if more than one connection is subsequently created by this connection factory)
]]>
Note: access to this exceptionLinstener will not be serialized if it is associated with more than
on connection (as it will be if more than one connection is subsequently created by this connection factory)
]]>
prefetch
policy for consumers created by this connection.
]]>
connection
URL used to connect to the ActiveMQ broker.
]]>
Note: access to this clientInternalExceptionListener will not be serialized if it is associated with more than
on connection (as it will be if more than one connection is subsequently created by this connection factory)
]]>
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.
]]>
Note: access to this exceptionLinstener will not be serialized if it is associated with more than
on connection (as it will be if more than one connection is subsequently created by this connection factory)
]]>
Message Groups
]]>
Nested
Structures of Map and List objects
]]>
prefetch
policy for consumers created by this connection.
]]>
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.
]]>
start
the connection so this option makes the default case to create a
warning if the user forgets. To disable the warning just set the value to <
0 (say -1).
]]>
sub-classing is
encouraged to override the default implementation of methods to account for differences in JDBC Driver
implementations. The JDBCAdapter inserts and extracts BLOB data using the getBytes()/setBytes() operations.
The databases/JDBC drivers that use this adapter are:
]]>
DOT
file creator plugin which creates a DOT file showing the current topic & queue hierarchies.
]]>
Sybase
MS SQL
]]>
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.
]]>
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.
]]>
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.
]]>
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.
]]>
null
if the broker name was not set.
]]>
Message
Groups functionality.
]]>
Mirrored
Queue using a prefix and postfix to define the topic name on which to mirror the queue to.
]]>
multicast://address:port
]]>
Subclassing is encouraged to override the default
implementation of methods to account for differences
in JDBC Driver implementations.
The JDBCAdapter inserts and extracts BLOB data using the
getBytes()/setBytes() operations.
The databases/JDBC drivers that use this adapter are:
]]>
Subclassing is encouraged to override the default
implementation of methods to account for differences
in JDBC Driver implementations.
]]>
Message Groups
functionality.
]]>
Message Groups
functionality.
]]>
The resourceName
property should be used along with the {@link ActiveMQResourceManager} and have
the same value than its resourceName
property. This will make sure the transaction manager
maps correctly the connection factory to the recovery process.
]]>
Subclassing is encouraged to override the default
implementation of methods to account for differences
in JDBC Driver implementations.
The JDBCAdapter inserts and extracts BLOB data using the
getBytes()/setBytes() operations.
The databases/JDBC drivers that use this adapter are:
]]>
Message Groups functionality.
]]>
Axion
]]>
Virtual Topics.
]]>
This stops the build-up of unwanted messages, especially when consumers may
disconnect from time to time when using virtual destinations.
This is influenced by code snippets developed by Maciej Rakowicz
]]>
Virtual
Topics using a prefix and postfix. The virtual destination creates a
wildcard that is then used to look up all active queue subscriptions which
match.
]]>
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.
]]>
Note: access to this clientInternalExceptionListener will not be serialized if it is associated with more than
on connection (as it will be if more than one connection is subsequently created by this connection factory)
]]>
Note: access to this exceptionLinstener will not be serialized if it is associated with more than
on connection (as it will be if more than one connection is subsequently created by this connection factory)
]]>
prefetch
policy for consumers created by this connection.
]]>
connection
URL used to connect to the ActiveMQ broker.
]]>
Note: access to this clientInternalExceptionListener will not be serialized if it is associated with more than
on connection (as it will be if more than one connection is subsequently created by this connection factory)
]]>
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.
]]>
Note: access to this exceptionLinstener will not be serialized if it is associated with more than
on connection (as it will be if more than one connection is subsequently created by this connection factory)
]]>
Message Groups
]]>
Nested
Structures of Map and List objects
]]>
prefetch
policy for consumers created by this connection.
]]>
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.
]]>
start
the connection so this option makes the default case to create a
warning if the user forgets. To disable the warning just set the value to <
0 (say -1).
]]>