activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r961521 - in /websites/production/activemq/content: activemq-4-connection-uris.html auto.html cache/main.pageCache configuring-transports.html configuring-version-5-transports.html
Date Tue, 11 Aug 2015 19:21:57 GMT
Author: buildbot
Date: Tue Aug 11 19:21:57 2015
New Revision: 961521

Log:
Production update by buildbot for activemq

Modified:
    websites/production/activemq/content/activemq-4-connection-uris.html
    websites/production/activemq/content/auto.html
    websites/production/activemq/content/cache/main.pageCache
    websites/production/activemq/content/configuring-transports.html
    websites/production/activemq/content/configuring-version-5-transports.html

Modified: websites/production/activemq/content/activemq-4-connection-uris.html
==============================================================================
--- websites/production/activemq/content/activemq-4-connection-uris.html (original)
+++ websites/production/activemq/content/activemq-4-connection-uris.html Tue Aug 11 19:21:57
2015
@@ -82,7 +82,7 @@
   <tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="ActiveMQ4ConnectionURIs-Transportconfigurationoptions">Transport
configuration options</h2><p>One of the first kinds of URI you are likely to use
is a transport URI to connect to a broker using a kind of transport. Generally TCP or VM are
the first transports you'll use.</p><div class="confluence-information-macro confluence-information-macro-warning"><p
class="title">Be careful about whitespace</p><span class="aui-icon aui-icon-small
aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>All
of the following URI configurations are based on the java.net.URI class which does not allow
whitespace to be used. So if you are using <strong>failover:</strong> or <strong>static:</strong>
URIs, do not put any whitespace around the <strong>,</strong> symbol.</p></div></div><h3
id="ActiveMQ4ConnectionURIs-TheAUTOTransport">The AUTO Transport</h3><p>Starting
with 5.13.0 ActiveMQ has support for
  automatic wire protocol detection over TCP, SSL, NIO, and NIO SSL. &#160;OpenWire, STOMP,
AMQP, and MQTT are supported. &#160;For details see the <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/AUTO">AUTO
</a>Transport Reference.</p><h3 id="ActiveMQ4ConnectionURIs-TheVMTransport">The
VM Transport</h3><p>The VM transport allows clients to connect to each other inside
the VM without the overhead of the network communication. The connection used is not that
of a socket connection but instead uses direct method invocations to enable a high performance
embedded messaging system.</p><p>The first client to use the VM connection will
boot an embedded broker. Subsequent connections will attach that the same broker. Once all
VM connections to the broker have been closed, the embedded broker will automatically shutdown.</p><p>For
more information see the <a shape="rect" href="vm-transport-reference.html">VM Transport
Reference</a></p><h3 id="ActiveMQ4ConnectionURIs-
 TheAMQPTransport">The AMQP Transport</h3><p>As of 5.8.0 ActiveMQ has support
for AMQP. For details see the <a shape="rect" href="amqp.html">AMQP</a> Transport
Reference.</p><h3 id="ActiveMQ4ConnectionURIs-TheMQTTTransport">The MQTT Transport</h3><p>Starting
with 5.6.0 ActiveMQ also supports <a shape="rect" class="external-link" href="http://mqtt.org/"
rel="nofollow">MQTT</a>. Its a light weight publish/subscribe messaging transport.
See the <a shape="rect" href="mqtt.html">MQTT</a> Transport Reference for details.</p><h3
id="ActiveMQ4ConnectionURIs-TheTCPTransport">The TCP Transport</h3><p>The TCP
transport allows clients to connect a remote ActiveMQ using a a TCP socket.</p><p>For
more information see the <a shape="rect" href="tcp-transport-reference.html">TCP Transport
Reference</a></p><h3 id="ActiveMQ4ConnectionURIs-TheNIOTransport">The NIO
Transport</h3><p>Same as the TCP transport, except that the <a shape="rect"
class="external-link" href="http://en.wikipedia.org/wiki/New_I/O"
  rel="nofollow">New I/O (NIO)</a> package is used, which may provide better performance.
The Java NIO package should not be confused with IBM's <a shape="rect" class="external-link"
href="http://java.sys-con.com/read/46658.htm" rel="nofollow">AIO4J </a> package.</p><p>To
switch from TCP to NIO, simply change the scheme portion of the URI. Here's an example as
defined within a broker's XML configuration file.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
+<div class="wiki-content maincontent"><h2 id="ActiveMQ4ConnectionURIs-Transportconfigurationoptions">Transport
configuration options</h2><p>One of the first kinds of URI you are likely to use
is a transport URI to connect to a broker using a kind of transport. Generally TCP or VM are
the first transports you'll use.</p><div class="confluence-information-macro confluence-information-macro-warning"><p
class="title">Be careful about whitespace</p><span class="aui-icon aui-icon-small
aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>All
of the following URI configurations are based on the java.net.URI class which does not allow
whitespace to be used. So if you are using <strong>failover:</strong> or <strong>static:</strong>
URIs, do not put any whitespace around the <strong>,</strong> symbol.</p></div></div><h3
id="ActiveMQ4ConnectionURIs-TheAUTOTransport">The AUTO Transport</h3><p>Starting
with 5.13.0 ActiveMQ has support for
  automatic wire protocol detection over TCP, SSL, NIO, and NIO SSL. &#160;OpenWire, STOMP,
AMQP, and MQTT are supported. &#160;For details see the <a shape="rect" href="auto.html">AUTO
</a>Transport Reference.</p><h3 id="ActiveMQ4ConnectionURIs-TheVMTransport">The
VM Transport</h3><p>The VM transport allows clients to connect to each other inside
the VM without the overhead of the network communication. The connection used is not that
of a socket connection but instead uses direct method invocations to enable a high performance
embedded messaging system.</p><p>The first client to use the VM connection will
boot an embedded broker. Subsequent connections will attach that the same broker. Once all
VM connections to the broker have been closed, the embedded broker will automatically shutdown.</p><p>For
more information see the <a shape="rect" href="vm-transport-reference.html">VM Transport
Reference</a></p><h3 id="ActiveMQ4ConnectionURIs-TheAMQPTransport">The AMQP
Transport</h3><p>As o
 f 5.8.0 ActiveMQ has support for AMQP. For details see the <a shape="rect" href="amqp.html">AMQP</a>
Transport Reference.</p><h3 id="ActiveMQ4ConnectionURIs-TheMQTTTransport">The
MQTT Transport</h3><p>Starting with 5.6.0 ActiveMQ also supports <a shape="rect"
class="external-link" href="http://mqtt.org/" rel="nofollow">MQTT</a>. Its a light
weight publish/subscribe messaging transport. See the <a shape="rect" href="mqtt.html">MQTT</a>
Transport Reference for details.</p><h3 id="ActiveMQ4ConnectionURIs-TheTCPTransport">The
TCP Transport</h3><p>The TCP transport allows clients to connect a remote ActiveMQ
using a a TCP socket.</p><p>For more information see the <a shape="rect" href="tcp-transport-reference.html">TCP
Transport Reference</a></p><h3 id="ActiveMQ4ConnectionURIs-TheNIOTransport">The
NIO Transport</h3><p>Same as the TCP transport, except that the <a shape="rect"
class="external-link" href="http://en.wikipedia.org/wiki/New_I/O" rel="nofollow">New I/O
(NIO)</a> package is use
 d, which may provide better performance. The Java NIO package should not be confused with
IBM's <a shape="rect" class="external-link" href="http://java.sys-con.com/read/46658.htm"
rel="nofollow">AIO4J </a> package.</p><p>To switch from TCP to NIO, simply
change the scheme portion of the URI. Here's an example as defined within a broker's XML configuration
file.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
 <pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">&lt;broker&gt;
   ...
   &lt;transportConnectors&gt;

Modified: websites/production/activemq/content/auto.html
==============================================================================
--- websites/production/activemq/content/auto.html (original)
+++ websites/production/activemq/content/auto.html Tue Aug 11 19:21:57 2015
@@ -90,7 +90,13 @@
 <pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">   
 &lt;transportConnector name="auto+nio" uri="auto+nio://localhost:5671"/&gt;</pre>
 </div></div><h3 id="AUTO-EnablingAUTOoverNIOSSL">Enabling AUTO over NIO
SSL</h3><p>To configure ActiveMQ auto wire format detection over an NIO SSL connection
use the&#160;<code>auto+nio+ssl</code>&#160;transport prefix. For example,
add the following transport configuration in your XML file:</p><div class="code panel
pdl" style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">   
 &lt;transportConnector name="auto+nio+ssl" uri="auto+nio+ssl://localhost:5671"/&gt;</pre>
-</div></div><p>&#160;</p><p>&#160;</p></div>
+</div></div><h3 id="AUTO-ConfiguringWireFormats">Configuring Wire Formats</h3><p>OpenWire
is the default Wire Format that ActiveMQ uses.&#160; It provides a highly efficent binary
format for high speed messaging.&#160; OpenWire options can be configured on a JMS client's
connection URI string or on a Brokers transport bind URI.</p><div class="table-wrap"><table
class="confluenceTable"><tbody><tr><th colspan="1" rowspan="1" class="confluenceTh"><p>Parameter
Prefix</p></th><th colspan="1" rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Applies the option to all wire formats.</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.default.</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Applies the option to the default
format which is OpenWire</p></td></tr><tr><td colspan="1" rowspan="1"
class="confluenceTd"><p
 >wireFormat.stomp.</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p><span>Applies
the option to the STOMP wire format</span></p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p><span>wireFormat.amqp.</span></p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><span>Applies the option to
the AMQP<span> wire format</span></span></p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>wireFormat.mqtt.</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p><span>Applies the option to
the MQTT<span> wire format</span></span></p></td></tr></tbody></table></div><p>&#160;</p><p>An
example of a property applies to all formats:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">   
 &lt;transportConnector name="auto" uri="auto://localhost:5671?wireFormat.maxFrameSize=1000"/&gt;</pre>
+</div></div><p>&#160;</p><p>An example of a property only
applied to OpenWire would be:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">   
 &lt;transportConnector name="auto" uri="auto://localhost:5671?wireFormat.default.maxFrameSize=1000"/&gt;</pre>
+</div></div><h3 id="AUTO-ConfiguringEnabledWireProtocols">Configuring Enabled
Wire Protocols</h3><p>By default all wire protocols are available. &#160;This
can be configured to only enable certain formats by setting the property &#160;<code>all.protocols.</code>&#160;</p><div
class="table-wrap"><table class="confluenceTable"><tbody><tr><th colspan="1"
rowspan="1" class="confluenceTh"><p>Value</p></th><th colspan="1"
rowspan="1" class="confluenceTh"><p>Description</p></th></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>default</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Enables OpenWire</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>amqp</p></td><td colspan="1"
rowspan="1" class="confluenceTd"><p>Enables AMQP format</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"><p>stomp</p></td><td
colspan="1" rowspan="1" class="confluenceTd"><p>Enables STOMP format</p></td></tr><tr><td
colspan="1" rowspan="1" class="confluenceTd"
 ><p>mqtt</p></td><td colspan="1" rowspan="1" class="confluenceTd"><p>Enables
MQTT format</p></td></tr></tbody></table></div><p>&#160;</p><p>An
example showing only OpenWire and STOMP enabled:</p><div class="code panel pdl" style="border-width:
1px;"><div class="codeContent panelContent pdl">
+<pre class="brush: xml; gutter: false; theme: Default" style="font-size:12px;">   
 &lt;transportConnector name="auto" uri="auto://localhost:5671?auto.protocols=default,stomp"/&gt;</pre>
+</div></div></div>
         </td>
         <td valign="top">
           <div class="navigation">

Modified: websites/production/activemq/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/activemq/content/configuring-transports.html
==============================================================================
--- websites/production/activemq/content/configuring-transports.html (original)
+++ websites/production/activemq/content/configuring-transports.html Tue Aug 11 19:21:57 2015
@@ -81,7 +81,7 @@
   <tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="ConfiguringTransports-Transportconfigurationoptions">Transport
configuration options</h2><p>One of the first kinds of URI you are likely to use
is a transport URI to connect to a broker using a kind of transport. Generally TCP or VM are
the first transports you'll use.</p><div class="confluence-information-macro confluence-information-macro-warning"><p
class="title">Be careful about whitespace</p><span class="aui-icon aui-icon-small
aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>All
of the following URI configurations are based on the java.net.URI class which does not allow
whitespace to be used. So if you are using <strong>failover:</strong> or <strong>static:</strong>
URIs, do not put any whitespace around the <strong>,</strong> symbol.</p></div></div><h3
id="ConfiguringTransports-TheAUTOTransport">The AUTO Transport</h3><p>Starting
with 5.13.0 ActiveMQ has support for aut
 omatic wire protocol detection over TCP, SSL, NIO, and NIO SSL. &#160;OpenWire, STOMP,
AMQP, and MQTT are supported. &#160;For details see the <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/AUTO">AUTO
</a>Transport Reference.</p><h3 id="ConfiguringTransports-TheVMTransport">The
VM Transport</h3><p>The VM transport allows clients to connect to each other inside
the VM without the overhead of the network communication. The connection used is not that
of a socket connection but instead uses direct method invocations to enable a high performance
embedded messaging system.</p><p>The first client to use the VM connection will
boot an embedded broker. Subsequent connections will attach that the same broker. Once all
VM connections to the broker have been closed, the embedded broker will automatically shutdown.</p><p>For
more information see the <a shape="rect" href="vm-transport-reference.html">VM Transport
Reference</a></p><h3 id="ConfiguringTransports-TheAMQPT
 ransport">The AMQP Transport</h3><p>As of 5.8.0 ActiveMQ has support for AMQP.
For details see the <a shape="rect" href="amqp.html">AMQP</a> Transport Reference.</p><h3
id="ConfiguringTransports-TheMQTTTransport">The MQTT Transport</h3><p>Starting
with 5.6.0 ActiveMQ also supports <a shape="rect" class="external-link" href="http://mqtt.org/"
rel="nofollow">MQTT</a>. Its a light weight publish/subscribe messaging transport.
See the <a shape="rect" href="mqtt.html">MQTT</a> Transport Reference for details.</p><h3
id="ConfiguringTransports-TheTCPTransport">The TCP Transport</h3><p>The TCP
transport allows clients to connect a remote ActiveMQ using a a TCP socket.</p><p>For
more information see the <a shape="rect" href="tcp-transport-reference.html">TCP Transport
Reference</a></p><h3 id="ConfiguringTransports-TheNIOTransport">The NIO
Transport</h3><p>Same as the TCP transport, except that the <a shape="rect"
class="external-link" href="http://en.wikipedia.org/wiki/New_I/O" rel="nofollow
 ">New I/O (NIO)</a> package is used, which may provide better performance. The Java
NIO package should not be confused with IBM's <a shape="rect" class="external-link" href="http://java.sys-con.com/read/46658.htm"
rel="nofollow">AIO4J </a> package.</p><p>To switch from TCP to NIO, simply
change the scheme portion of the URI. Here's an example as defined within a broker's XML configuration
file.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<div class="wiki-content maincontent"><h2 id="ConfiguringTransports-Transportconfigurationoptions">Transport
configuration options</h2><p>One of the first kinds of URI you are likely to use
is a transport URI to connect to a broker using a kind of transport. Generally TCP or VM are
the first transports you'll use.</p><div class="confluence-information-macro confluence-information-macro-warning"><p
class="title">Be careful about whitespace</p><span class="aui-icon aui-icon-small
aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>All
of the following URI configurations are based on the java.net.URI class which does not allow
whitespace to be used. So if you are using <strong>failover:</strong> or <strong>static:</strong>
URIs, do not put any whitespace around the <strong>,</strong> symbol.</p></div></div><h3
id="ConfiguringTransports-TheAUTOTransport">The AUTO Transport</h3><p>Starting
with 5.13.0 ActiveMQ has support for aut
 omatic wire protocol detection over TCP, SSL, NIO, and NIO SSL. &#160;OpenWire, STOMP,
AMQP, and MQTT are supported. &#160;For details see the <a shape="rect" href="auto.html">AUTO
</a>Transport Reference.</p><h3 id="ConfiguringTransports-TheVMTransport">The
VM Transport</h3><p>The VM transport allows clients to connect to each other inside
the VM without the overhead of the network communication. The connection used is not that
of a socket connection but instead uses direct method invocations to enable a high performance
embedded messaging system.</p><p>The first client to use the VM connection will
boot an embedded broker. Subsequent connections will attach that the same broker. Once all
VM connections to the broker have been closed, the embedded broker will automatically shutdown.</p><p>For
more information see the <a shape="rect" href="vm-transport-reference.html">VM Transport
Reference</a></p><h3 id="ConfiguringTransports-TheAMQPTransport">The AMQP
Transport</h3><p>As of 5.8.0 
 ActiveMQ has support for AMQP. For details see the <a shape="rect" href="amqp.html">AMQP</a>
Transport Reference.</p><h3 id="ConfiguringTransports-TheMQTTTransport">The MQTT
Transport</h3><p>Starting with 5.6.0 ActiveMQ also supports <a shape="rect"
class="external-link" href="http://mqtt.org/" rel="nofollow">MQTT</a>. Its a light
weight publish/subscribe messaging transport. See the <a shape="rect" href="mqtt.html">MQTT</a>
Transport Reference for details.</p><h3 id="ConfiguringTransports-TheTCPTransport">The
TCP Transport</h3><p>The TCP transport allows clients to connect a remote ActiveMQ
using a a TCP socket.</p><p>For more information see the <a shape="rect" href="tcp-transport-reference.html">TCP
Transport Reference</a></p><h3 id="ConfiguringTransports-TheNIOTransport">The
NIO Transport</h3><p>Same as the TCP transport, except that the <a shape="rect"
class="external-link" href="http://en.wikipedia.org/wiki/New_I/O" rel="nofollow">New I/O
(NIO)</a> package is used, which may p
 rovide better performance. The Java NIO package should not be confused with IBM's <a shape="rect"
class="external-link" href="http://java.sys-con.com/read/46658.htm" rel="nofollow">AIO4J
</a> package.</p><p>To switch from TCP to NIO, simply change the scheme
portion of the URI. Here's an example as defined within a broker's XML configuration file.</p><div
class="code panel pdl" style="border-width: 1px;"><div class="codeContent panelContent
pdl">
 <pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">&lt;broker&gt;
   ...
   &lt;transportConnectors&gt;

Modified: websites/production/activemq/content/configuring-version-5-transports.html
==============================================================================
--- websites/production/activemq/content/configuring-version-5-transports.html (original)
+++ websites/production/activemq/content/configuring-version-5-transports.html Tue Aug 11
19:21:57 2015
@@ -82,7 +82,7 @@
   <tbody>
         <tr>
         <td valign="top" width="100%">
-<div class="wiki-content maincontent"><h2 id="ConfiguringVersion5Transports-Transportconfigurationoptions">Transport
configuration options</h2><p>One of the first kinds of URI you are likely to use
is a transport URI to connect to a broker using a kind of transport. Generally TCP or VM are
the first transports you'll use.</p><div class="confluence-information-macro confluence-information-macro-warning"><p
class="title">Be careful about whitespace</p><span class="aui-icon aui-icon-small
aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>All
of the following URI configurations are based on the java.net.URI class which does not allow
whitespace to be used. So if you are using <strong>failover:</strong> or <strong>static:</strong>
URIs, do not put any whitespace around the <strong>,</strong> symbol.</p></div></div><h3
id="ConfiguringVersion5Transports-TheAUTOTransport">The AUTO Transport</h3><p>Starting
with 5.13.0 ActiveMQ has
  support for automatic wire protocol detection over TCP, SSL, NIO, and NIO SSL. &#160;OpenWire,
STOMP, AMQP, and MQTT are supported. &#160;For details see the <a shape="rect" href="https://cwiki.apache.org/confluence/display/ACTIVEMQ/AUTO">AUTO
</a>Transport Reference.</p><h3 id="ConfiguringVersion5Transports-TheVMTransport">The
VM Transport</h3><p>The VM transport allows clients to connect to each other inside
the VM without the overhead of the network communication. The connection used is not that
of a socket connection but instead uses direct method invocations to enable a high performance
embedded messaging system.</p><p>The first client to use the VM connection will
boot an embedded broker. Subsequent connections will attach that the same broker. Once all
VM connections to the broker have been closed, the embedded broker will automatically shutdown.</p><p>For
more information see the <a shape="rect" href="vm-transport-reference.html">VM Transport
Reference</a></p><h3 id="Config
 uringVersion5Transports-TheAMQPTransport">The AMQP Transport</h3><p>As of
5.8.0 ActiveMQ has support for AMQP. For details see the <a shape="rect" href="amqp.html">AMQP</a>
Transport Reference.</p><h3 id="ConfiguringVersion5Transports-TheMQTTTransport">The
MQTT Transport</h3><p>Starting with 5.6.0 ActiveMQ also supports <a shape="rect"
class="external-link" href="http://mqtt.org/" rel="nofollow">MQTT</a>. Its a light
weight publish/subscribe messaging transport. See the <a shape="rect" href="mqtt.html">MQTT</a>
Transport Reference for details.</p><h3 id="ConfiguringVersion5Transports-TheTCPTransport">The
TCP Transport</h3><p>The TCP transport allows clients to connect a remote ActiveMQ
using a a TCP socket.</p><p>For more information see the <a shape="rect" href="tcp-transport-reference.html">TCP
Transport Reference</a></p><h3 id="ConfiguringVersion5Transports-TheNIOTransport">The
NIO Transport</h3><p>Same as the TCP transport, except that the <a shape="rect"
class="external-link" h
 ref="http://en.wikipedia.org/wiki/New_I/O" rel="nofollow">New I/O (NIO)</a> package
is used, which may provide better performance. The Java NIO package should not be confused
with IBM's <a shape="rect" class="external-link" href="http://java.sys-con.com/read/46658.htm"
rel="nofollow">AIO4J </a> package.</p><p>To switch from TCP to NIO, simply
change the scheme portion of the URI. Here's an example as defined within a broker's XML configuration
file.</p><div class="code panel pdl" style="border-width: 1px;"><div class="codeContent
panelContent pdl">
+<div class="wiki-content maincontent"><h2 id="ConfiguringVersion5Transports-Transportconfigurationoptions">Transport
configuration options</h2><p>One of the first kinds of URI you are likely to use
is a transport URI to connect to a broker using a kind of transport. Generally TCP or VM are
the first transports you'll use.</p><div class="confluence-information-macro confluence-information-macro-warning"><p
class="title">Be careful about whitespace</p><span class="aui-icon aui-icon-small
aui-iconfont-error confluence-information-macro-icon"></span><div class="confluence-information-macro-body"><p>All
of the following URI configurations are based on the java.net.URI class which does not allow
whitespace to be used. So if you are using <strong>failover:</strong> or <strong>static:</strong>
URIs, do not put any whitespace around the <strong>,</strong> symbol.</p></div></div><h3
id="ConfiguringVersion5Transports-TheAUTOTransport">The AUTO Transport</h3><p>Starting
with 5.13.0 ActiveMQ has
  support for automatic wire protocol detection over TCP, SSL, NIO, and NIO SSL. &#160;OpenWire,
STOMP, AMQP, and MQTT are supported. &#160;For details see the <a shape="rect" href="auto.html">AUTO
</a>Transport Reference.</p><h3 id="ConfiguringVersion5Transports-TheVMTransport">The
VM Transport</h3><p>The VM transport allows clients to connect to each other inside
the VM without the overhead of the network communication. The connection used is not that
of a socket connection but instead uses direct method invocations to enable a high performance
embedded messaging system.</p><p>The first client to use the VM connection will
boot an embedded broker. Subsequent connections will attach that the same broker. Once all
VM connections to the broker have been closed, the embedded broker will automatically shutdown.</p><p>For
more information see the <a shape="rect" href="vm-transport-reference.html">VM Transport
Reference</a></p><h3 id="ConfiguringVersion5Transports-TheAMQPTransport">The
AM
 QP Transport</h3><p>As of 5.8.0 ActiveMQ has support for AMQP. For details see
the <a shape="rect" href="amqp.html">AMQP</a> Transport Reference.</p><h3
id="ConfiguringVersion5Transports-TheMQTTTransport">The MQTT Transport</h3><p>Starting
with 5.6.0 ActiveMQ also supports <a shape="rect" class="external-link" href="http://mqtt.org/"
rel="nofollow">MQTT</a>. Its a light weight publish/subscribe messaging transport.
See the <a shape="rect" href="mqtt.html">MQTT</a> Transport Reference for details.</p><h3
id="ConfiguringVersion5Transports-TheTCPTransport">The TCP Transport</h3><p>The
TCP transport allows clients to connect a remote ActiveMQ using a a TCP socket.</p><p>For
more information see the <a shape="rect" href="tcp-transport-reference.html">TCP Transport
Reference</a></p><h3 id="ConfiguringVersion5Transports-TheNIOTransport">The
NIO Transport</h3><p>Same as the TCP transport, except that the <a shape="rect"
class="external-link" href="http://en.wikipedia.org/wiki/New_I/O" rel="
 nofollow">New I/O (NIO)</a> package is used, which may provide better performance.
The Java NIO package should not be confused with IBM's <a shape="rect" class="external-link"
href="http://java.sys-con.com/read/46658.htm" rel="nofollow">AIO4J </a> package.</p><p>To
switch from TCP to NIO, simply change the scheme portion of the URI. Here's an example as
defined within a broker's XML configuration file.</p><div class="code panel pdl"
style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <pre class="brush: java; gutter: false; theme: Default" style="font-size:12px;">&lt;broker&gt;
   ...
   &lt;transportConnectors&gt;



Mime
View raw message