Site > Old Links > Previous Versions > ActiveMQ 3 Transport Configurations
Some of the transports support configuration, such as timeout values, maximum retry count and so forth. To configure the transports you can use the URI query syntax. e.g.
If you are using a list of URLs like above with the list and reliable protocols you can wrap the list in parens to be able to configure the list. e.g.
Option Name | Default Value | Type |
---|---|---|
brokerXmlConfig | null | String |
cachingEnabled | true | boolean |
clientID | null | String |
copyMessageOnSend | true | boolean |
disableTimeStampsByDefault | false | boolean |
doMessageCompression | true | boolean |
doMessageFragmentation | true | boolean |
messageCompressionLimit | 32768 | int |
messageCompressionStrategy | 0 | int |
messageFragmentationLimit | 65536 | int |
optimizedMessageDispatch | false | boolean |
password | null | String |
prepareMessageBodyOnSend | true | boolean |
turboBoost | true | boolean |
useAsyncSend | true | boolean |
useEmbeddedBroker | false | boolean |
userName | null | String |
wireFormat | default | String |
noDelay | false | boolean |
Sets the Xml Configuration file used to configure the ActiveMQ broker via Spring if using embedded mode. The filename is assumed to be on the classpath unless a URL is specified. So a value of
foo/bar.xml
would be assumed to be on the classpath whereas
file:dir/file.xml
would use the file system. Any valid URL string is supported.
Provides optimisations on the wire format (caching data at each end and using references to it to minmise the message size
Used to set the JMS clientID of connection.
Use to avoid the overhead of doing a deep copy of the JMS message everytime the message is sent.
Use to avoid the overhead of setting a timestamp on each message produced.
If messages should be compressed.
If messages should be chunked into smaller fragments on the clients side.
Data size above which compression will be used
The compression strategy to use when compressing messages. Defaults to the value of java.util.zip.Deflater.DEFAULT_STRATEGY (0).
Data size above which message fragmentation will be used
The user password used to authenticate with the broker.
Causes pre-serialization of messages before send.
Enables a number of performance enhancements which are disabled by default to ensure J2EE certification. turboBoost turns on a bunch of optimisations: disableTimeStampsByDefault, useAsyncSend, cachingEnabled, and optimizedMessageDispatch and then disables copyMessageOnSend and prepareMessageBodyOnSend
Used to enable asynchronous sending, which boost performance by using another thread to handle sending of messages to the socket.
Set to true if you want start an embeded broker when the first connection is created.
The user name used to authenticate with the broker.
Allows a custom wire format to be used; otherwise the default Java wire format is used which is designed for minimum size and maximum speed on the Java platform.
Used to indicate whether messages are dispatched as quickly as possible or not. (The latency versus throughput trade off). When using TCP based transport this option is a means of disabling Nagles which can often improve performance on synchronous sends.
Same as TCP. SSL certificates are configured at the VM level. See How do I use SSL
Same as the List configuration options above - plus