You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@qpid.apache.org by gm...@apache.org on 2016/04/25 20:13:25 UTC
svn commit: r1740870 [2/2] - in /qpid/site:
docs/releases/qpid-dispatch-master/ docs/releases/qpid-dispatch-master/book/
docs/releases/qpid-dispatch-master/man/ input/releases/qpid-dispatch-master/
input/releases/qpid-dispatch-master/book/ input/releas...
Modified: qpid/site/input/releases/qpid-dispatch-master/book/basic_usage.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/book/basic_usage.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/book/basic_usage.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/book/basic_usage.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="basic-usage-and-examples">
<h1>2.3. Basic Usage and Examples<a class="headerlink" href="#basic-usage-and-examples" title="Permalink to this headline">.</a></h1>
@@ -12,7 +11,7 @@ with any other routers and only routes m
endpoints.</p>
<p>If your router is running in stand-alone mode, <em>qdstat -a</em> will look
like the following:</p>
-<div class="highlight-python"><pre>$ qdstat -a
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ qdstat -a
Router Addresses
class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
===============================================================================================================
@@ -20,7 +19,8 @@ Router Addresses
local $displayname closest 1 0 0 0 0 0 0 0 0
mobile $management 0 closest 1 0 0 0 1 0 0 1 0
local $management closest 1 0 0 0 0 0 0 0 0
- local temp.1GThUllfR7N+BDP closest 0 1 0 0 0 0 0 0 0</pre>
+ local temp.1GThUllfR7N+BDP closest 0 1 0 0 0 0 0 0 0
+</pre></div>
</div>
<p>Note that there are a number of known addresses. <em>$management</em> is the address of
the router’s embedded management agent. <em>temp.1GThUllfR7N+BDP</em> is the temporary
@@ -28,7 +28,7 @@ reply-to address of the <em>qdstat</em>
<p>If you change the mode to interior and restart the processs, the same
command will yield additional addresses which are used for
inter-router communication:</p>
-<div class="highlight-python"><pre>$ qdstat -a
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ qdstat -a
Router Addresses
class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
=================================================================================================================
@@ -41,7 +41,8 @@ Router Addresses
topo qdrouter flood 1 0 0 0 0 0 0 0 1
local qdrouter.ma multicast 1 0 0 0 0 0 0 0 0
topo qdrouter.ma multicast 1 0 0 0 0 0 0 0 0
- local temp.wfx54+zf+YWQF3T closest 0 1 0 0 0 0 0 0 0</pre>
+ local temp.wfx54+zf+YWQF3T closest 0 1 0 0 0 0 0 0 0
+</pre></div>
</div>
</div>
<div class="section" id="mobile-subscribers">
@@ -53,11 +54,12 @@ attaches, the messages will be routed to
<p>To illustrate a subscription on a stand-alone router, you can use the
examples that are provided with Qpid Proton. Using the <em>simple_recv.py</em> example
receiver:</p>
-<div class="highlight-python"><pre>$ python ./simple_recv.py -a 127.0.0.1/my-address</pre>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ python ./simple_recv.py -a 127.0.0.1/my-address
+</pre></div>
</div>
<p>This command creates a receiving link subscribed to the specified
address. To verify the subscription:</p>
-<div class="highlight-python"><pre>$ qdstat -a
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ qdstat -a
Router Addresses
class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
===============================================================================================================
@@ -66,11 +68,13 @@ Router Addresses
mobile $management 0 closest 1 0 0 0 2 0 0 2 0
local $management closest 1 0 0 0 0 0 0 0 0
mobile my-address 0 closest 0 1 0 0 0 0 0 0 0
- local temp.75_d2X23x_KOT51 closest 0 1 0 0 0 0 0 0 0</pre>
+ local temp.75_d2X23x_KOT51 closest 0 1 0 0 0 0 0 0 0
+</pre></div>
</div>
<p>You can then, in a separate command window, run a sender to produce
messages to that address:</p>
-<div class="highlight-python"><pre>$ python ./simple_send.py -a 127.0.0.1/my-address</pre>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ python ./simple_send.py -a 127.0.0.1/my-address
+</pre></div>
</div>
</div>
<div class="section" id="dynamic-reply-to">
@@ -81,7 +85,7 @@ take to get there. To illustrate this fe
program (written in C++ against the qpid::messaging API) that queries
the management agent of the attached router for a list of other known
routers’ management addresses.</p>
-<div class="highlight-python"><pre>#include <qpid/messaging/Address.h>
+<div class="highlight-python"><div class="highlight"><pre><span></span>#include <qpid/messaging/Address.h>
#include <qpid/messaging/Connection.h>
#include <qpid/messaging/Message.h>
#include <qpid/messaging/Receiver.h>
@@ -95,61 +99,62 @@ using std::stringstream;
using std::string;
int main() {
- const char* url = "amqp:tcp:127.0.0.1:5672";
- std::string connectionOptions = "{protocol:amqp1.0}";
+ const char* url = "amqp:tcp:127.0.0.1:5672";
+ std::string connectionOptions = "{protocol:amqp1.0}";
Connection connection(url, connectionOptions);
connection.open();
Session session = connection.createSession();
- Sender sender = session.createSender("mgmt");
+ Sender sender = session.createSender("mgmt");
// create reply receiver and get the reply-to address
- Receiver receiver = session.createReceiver("#");
+ Receiver receiver = session.createReceiver("#");
Address responseAddress = receiver.getAddress();
Message request;
request.setReplyTo(responseAddress);
- request.setProperty("x-amqp-to", "amqp:/_local/$management");
- request.setProperty("operation", "DISCOVER-MGMT-NODES");
- request.setProperty("type", "org.amqp.management");
- request.setProperty("name, "self");
+ request.setProperty("x-amqp-to", "amqp:/_local/$management");
+ request.setProperty("operation", "DISCOVER-MGMT-NODES");
+ request.setProperty("type", "org.amqp.management");
+ request.setProperty("name, "self");
sender.send(request);
Message response = receiver.fetch();
Variant content(response.getContentObject());
- std::cout << "Response: " << content << std::endl << std::endl;
+ std::cout << "Response: " << content << std::endl << std::endl;
connection.close();
-}</pre>
+}
+</pre></div>
</div>
<p>The equivalent program written in Python against the Proton Messenger
API:</p>
-<div class="highlight-python"><div class="highlight"><pre><span class="kn">from</span> <span class="nn">proton</span> <span class="kn">import</span> <span class="n">Messenger</span><span class="p">,</span> <span class="n">Message</span>
+<div class="highlight-python"><div class="highlight"><pre><span></span><span class="kn">from</span> <span class="nn">proton</span> <span class="kn">import</span> <span class="n">Messenger</span><span class="p">,</span> <span class="n">Message</span>
<span class="k">def</span> <span class="nf">main</span><span class="p">():</span>
- <span class="n">host</span> <span class="o">=</span> <span class="s">"0.0.0.0:5672"</span>
+ <span class="n">host</span> <span class="o">=</span> <span class="s2">"0.0.0.0:5672"</span>
<span class="n">messenger</span> <span class="o">=</span> <span class="n">Messenger</span><span class="p">()</span>
<span class="n">messenger</span><span class="o">.</span><span class="n">start</span><span class="p">()</span>
- <span class="n">messenger</span><span class="o">.</span><span class="n">route</span><span class="p">(</span><span class="s">"amqp:/*"</span><span class="p">,</span> <span class="s">"amqp://</span><span class="si">%s</span><span class="s">/$1"</span> <span class="o">%</span> <span class="n">host</span><span class="p">)</span>
- <span class="n">reply_subscription</span> <span class="o">=</span> <span class="n">messenger</span><span class="o">.</span><span class="n">subscribe</span><span class="p">(</span><span class="s">"amqp:/#"</span><span class="p">)</span>
+ <span class="n">messenger</span><span class="o">.</span><span class="n">route</span><span class="p">(</span><span class="s2">"amqp:/*"</span><span class="p">,</span> <span class="s2">"amqp://</span><span class="si">%s</span><span class="s2">/$1"</span> <span class="o">%</span> <span class="n">host</span><span class="p">)</span>
+ <span class="n">reply_subscription</span> <span class="o">=</span> <span class="n">messenger</span><span class="o">.</span><span class="n">subscribe</span><span class="p">(</span><span class="s2">"amqp:/#"</span><span class="p">)</span>
<span class="n">reply_address</span> <span class="o">=</span> <span class="n">reply_subscription</span><span class="o">.</span><span class="n">address</span>
<span class="n">request</span> <span class="o">=</span> <span class="n">Message</span><span class="p">()</span>
<span class="n">response</span> <span class="o">=</span> <span class="n">Message</span><span class="p">()</span>
- <span class="n">request</span><span class="o">.</span><span class="n">address</span> <span class="o">=</span> <span class="s">"amqp:/_local/$management"</span>
+ <span class="n">request</span><span class="o">.</span><span class="n">address</span> <span class="o">=</span> <span class="s2">"amqp:/_local/$management"</span>
<span class="n">request</span><span class="o">.</span><span class="n">reply_to</span> <span class="o">=</span> <span class="n">reply_address</span>
- <span class="n">request</span><span class="o">.</span><span class="n">properties</span> <span class="o">=</span> <span class="p">{</span><span class="s">u'operation'</span> <span class="p">:</span> <span class="s">u'DISCOVER-MGMT-NODES'</span><span class="p">,</span>
- <span class="s">u'type'</span> <span class="p">:</span> <span class="s">u'org.amqp.management'</span><span class="p">,</span>
- <span class="s">u'name'</span> <span class="p">:</span> <span class="s">u'self'</span><span class="p">}</span>
+ <span class="n">request</span><span class="o">.</span><span class="n">properties</span> <span class="o">=</span> <span class="p">{</span><span class="s1">u'operation'</span> <span class="p">:</span> <span class="s1">u'DISCOVER-MGMT-NODES'</span><span class="p">,</span>
+ <span class="s1">u'type'</span> <span class="p">:</span> <span class="s1">u'org.amqp.management'</span><span class="p">,</span>
+ <span class="s1">u'name'</span> <span class="p">:</span> <span class="s1">u'self'</span><span class="p">}</span>
<span class="n">messenger</span><span class="o">.</span><span class="n">put</span><span class="p">(</span><span class="n">request</span><span class="p">)</span>
<span class="n">messenger</span><span class="o">.</span><span class="n">send</span><span class="p">()</span>
<span class="n">messenger</span><span class="o">.</span><span class="n">recv</span><span class="p">()</span>
<span class="n">messenger</span><span class="o">.</span><span class="n">get</span><span class="p">(</span><span class="n">response</span><span class="p">)</span>
- <span class="k">print</span> <span class="s">"Response: </span><span class="si">%r</span><span class="s">"</span> <span class="o">%</span> <span class="n">response</span><span class="o">.</span><span class="n">body</span>
+ <span class="k">print</span> <span class="s2">"Response: </span><span class="si">%r</span><span class="s2">"</span> <span class="o">%</span> <span class="n">response</span><span class="o">.</span><span class="n">body</span>
<span class="n">messenger</span><span class="o">.</span><span class="n">stop</span><span class="p">()</span>
Modified: qpid/site/input/releases/qpid-dispatch-master/book/book.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/book/book.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/book/book.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/book/book.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="qpid-dispatch-router-book">
<h1>Qpid Dispatch Router Book<a class="headerlink" href="#qpid-dispatch-router-book" title="Permalink to this headline">.</a></h1>
Modified: qpid/site/input/releases/qpid-dispatch-master/book/client_compatibility.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/book/client_compatibility.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/book/client_compatibility.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/book/client_compatibility.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="client-compatibility">
<h1>3.1. Client Compatibility<a class="headerlink" href="#client-compatibility" title="Permalink to this headline">.</a></h1>
Modified: qpid/site/input/releases/qpid-dispatch-master/book/console.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/book/console.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/book/console.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/book/console.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="console">
<h1>4. Console<a class="headerlink" href="#console" title="Permalink to this headline">.</a></h1>
Modified: qpid/site/input/releases/qpid-dispatch-master/book/console_installation.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/book/console_installation.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/book/console_installation.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/book/console_installation.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="console-installation">
<h1>4.2. Console installation<a class="headerlink" href="#console-installation" title="Permalink to this headline">.</a></h1>
@@ -13,31 +12,34 @@
</ul>
<p>A nodejs proxy is distributed with proton.
To start the proton’s nodejs proxy:</p>
-<div class="highlight-python"><pre>cd ~/rh-qpid-proton/examples/javascript/messenger
-node proxy.js &</pre>
+<div class="highlight-python"><div class="highlight"><pre><span></span>cd ~/rh-qpid-proton/examples/javascript/messenger
+node proxy.js &
+</pre></div>
</div>
<p>This will start the proxy listening to ws traffic on port 5673 and translating it to tcp on port 5672.
One of the routers in the network needs to have a listener configured on port 5672. That listener’s role should be ‘normal’. For example:</p>
-<div class="highlight-python"><pre>listener {
+<div class="highlight-python"><div class="highlight"><pre><span></span>listener {
addr: 0.0.0.0
role: normal
port: amqp
saslMechanisms: ANONYMOUS
-}</pre>
+}
+</pre></div>
</div>
</div>
<div class="section" id="the-console-files">
<h2>4.2.2. The console files<a class="headerlink" href="#the-console-files" title="Permalink to this headline">.</a></h2>
<p>The files for the console are located under the console directory in
the source tree.:</p>
-<div class="highlight-python"><pre>app/
+<div class="highlight-python"><div class="highlight"><pre><span></span>app/
bower_components/
css/
img/
index.html
lib/
plugin/
-vendor.js</pre>
+vendor.js
+</pre></div>
</div>
<dl class="docutils">
<dt>Copy these files to a directory under the the html or webapps directory of your web server. For example, for apache tomcat the files should be under webapps/dispatch. Then the console is available as::</dt>
Modified: qpid/site/input/releases/qpid-dispatch-master/book/console_operation.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/book/console_operation.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/book/console_operation.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/book/console_operation.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="console-operation">
<h1>4.3. Console operation<a class="headerlink" href="#console-operation" title="Permalink to this headline">.</a></h1>
Modified: qpid/site/input/releases/qpid-dispatch-master/book/console_overview.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/book/console_overview.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/book/console_overview.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/book/console_overview.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="console-overview">
<h1>4.1. Console overview<a class="headerlink" href="#console-overview" title="Permalink to this headline">.</a></h1>
Modified: qpid/site/input/releases/qpid-dispatch-master/book/default_config.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/book/default_config.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/book/default_config.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/book/default_config.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="configuration">
<h1>2.1. Configuration<a class="headerlink" href="#configuration" title="Permalink to this headline">.</a></h1>
Modified: qpid/site/input/releases/qpid-dispatch-master/book/introduction.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/book/introduction.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/book/introduction.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/book/introduction.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="introduction">
<h1>1. Introduction<a class="headerlink" href="#introduction" title="Permalink to this headline">.</a></h1>
Modified: qpid/site/input/releases/qpid-dispatch-master/book/link_routing.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/book/link_routing.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/book/link_routing.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/book/link_routing.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="link-routing">
<h1>2.4. Link Routing<a class="headerlink" href="#link-routing" title="Permalink to this headline">.</a></h1>
@@ -23,7 +22,7 @@ establish a link to a topic on a remote
filter.</p>
<p>Why would one want to do this? One reason is to provide client
isolation. A network like the following can be deployed:</p>
-<div class="highlight-python"><pre> Public Network
+<div class="highlight-python"><div class="highlight"><pre><span></span> Public Network
+-----------------+
| +-----+ |
| B1 | Rp | |
@@ -41,7 +40,8 @@ isolation. A network like the following
| +-----+ | | +-----+ |
| | | |
| | | |
-+-----------------+ +-----------------+</pre>
++-----------------+ +-----------------+
+</pre></div>
</div>
<p>The clients in Private Net B can be constrained (by firewall policy)
to only connect to the Router in their own network. Using
@@ -64,19 +64,20 @@ message-router network between them.</p>
configured to support the example described above?</p>
<p>First, router Ra needs to be told how to make a connection to the
broker B2:</p>
-<div class="highlight-python"><pre>connector {
+<div class="highlight-python"><div class="highlight"><pre><span></span>connector {
name: broker
role: route-container
addr: <B2-url>
port: <B2-port>
sasl-mechanisms: ANONYMOUS
-}</pre>
+}
+</pre></div>
</div>
<p>This <em>route-container</em> connector tells the router how to connect to an
external AMQP container when it is needed. The name “broker” will be
used later to refer to this connection.</p>
<p>Now, the router must be configured to route certain addresses to B2:</p>
-<div class="highlight-python"><pre>linkRoute {
+<div class="highlight-python"><div class="highlight"><pre><span></span>linkRoute {
prefix: b2
dir: in
connection: broker
@@ -86,7 +87,8 @@ linkRoute {
prefix: b2
dir: out
connection: broker
-}</pre>
+}
+</pre></div>
</div>
<p>The linkRoute tells router Ra that any sender or receiver that
is attached with a target or source (respectively) whos address begins
Modified: qpid/site/input/releases/qpid-dispatch-master/book/schema.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/book/schema.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/book/schema.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/book/schema.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="management-schema">
<h1>3.4. Management Schema<a class="headerlink" href="#management-schema" title="Permalink to this headline">.</a></h1>
@@ -97,7 +96,9 @@ be modified using the <cite>update</cite
<dt><em>protocolFamily</em> (One of [‘IPv4’, ‘IPv6’], <cite>CREATE</cite>)</dt>
<dd>[‘IPv4’, ‘IPv6’] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.</dd>
<dt><em>role</em> (One of [‘normal’, ‘inter-router’, ‘route-container’, ‘on-demand’], default=’normal’, <cite>CREATE</cite>)</dt>
-<dd>The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections.</dd>
+<dd>The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.</dd>
+<dt><em>cost</em> (integer, default=‘1’, <cite>CREATE</cite>)</dt>
+<dd>For the ‘inter-router’ role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.</dd>
<dt><em>certDb</em> (path, <cite>CREATE</cite>)</dt>
<dd>The path to the database that contains the public certificates of trusted certificate authorities (CA).</dd>
<dt><em>certFile</em> (path, <cite>CREATE</cite>)</dt>
@@ -124,8 +125,8 @@ be modified using the <cite>update</cite
<dd>yes: Require the use of SSL or TLS on the connection; no: Allow clients to connect without SSL or TLS.</dd>
<dt><em>trustedCerts</em> (path, <cite>CREATE</cite>)</dt>
<dd>This optional setting can be used to reduce the set of available CAs for client authentication. If used, this setting must provide a path to a PEM file that contains the trusted certificates.</dd>
-<dt><em>maxFrameSize</em> (integer, default=65536, <cite>CREATE</cite>)</dt>
-<dd>Defaults to 65536. If specified, it is the maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.</dd>
+<dt><em>maxFrameSize</em> (integer, default=16384, <cite>CREATE</cite>)</dt>
+<dd>Defaults to 16384. If specified, it is the maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.</dd>
<dt><em>idleTimeoutSeconds</em> (integer, default=16, <cite>CREATE</cite>)</dt>
<dd>The idle timeout, in seconds, for connections through this listener. If no frames are received on the connection for this time interval, the connection shall be closed.</dd>
<dt><em>requirePeerAuth</em> (boolean, <cite>CREATE</cite>)</dt>
@@ -152,7 +153,9 @@ be modified using the <cite>update</cite
<dt><em>protocolFamily</em> (One of [‘IPv4’, ‘IPv6’], <cite>CREATE</cite>)</dt>
<dd>[‘IPv4’, ‘IPv6’] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.</dd>
<dt><em>role</em> (One of [‘normal’, ‘inter-router’, ‘route-container’, ‘on-demand’], default=’normal’, <cite>CREATE</cite>)</dt>
-<dd>The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections.</dd>
+<dd>The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.</dd>
+<dt><em>cost</em> (integer, default=‘1’, <cite>CREATE</cite>)</dt>
+<dd>For the ‘inter-router’ role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.</dd>
<dt><em>certDb</em> (path, <cite>CREATE</cite>)</dt>
<dd>The path to the database that contains the public certificates of trusted certificate authorities (CA).</dd>
<dt><em>certFile</em> (path, <cite>CREATE</cite>)</dt>
@@ -279,6 +282,8 @@ be modified using the <cite>update</cite
<dd>Treatment of traffic associated with the address</dd>
<dt><em>dir</em> (One of [‘in’, ‘out’], required, <cite>CREATE</cite>)</dt>
<dd>The permitted direction of links: ‘in’ means client senders; ‘out’ means client receivers</dd>
+<dt><em>operStatus</em> (One of [‘inactive’, ‘active’])</dt>
+<dd>The operational status of this linkRoute: inactive - The remote container is not connected; active - the remote container is connected and ready to accept link routed attachments.</dd>
</dl>
</div>
<div class="section" id="router-config-autolink">
@@ -571,6 +576,8 @@ operational attributes.</p>
<dd>Address of the remote node</dd>
<dt><em>routerLink</em> (entityId)</dt>
<dd>Local link to remote node</dd>
+<dt><em>cost</em> (integer)</dt>
+<dd>Reachability cost</dd>
</dl>
</div>
<div class="section" id="connection">
@@ -644,10 +651,6 @@ operational attributes.</p>
<p><em>sessionDenied</em> (integer)</p>
<p><em>senderDenied</em> (integer)</p>
<p><em>receiverDenied</em> (integer)</p>
-<p><em>dynamicSrcDenied</em> (integer)</p>
-<p><em>anonymousSenderDenied</em> (integer)</p>
-<p><em>linkSourceDenied</em> (integer)</p>
-<p><em>linkTargetDenied</em> (integer)</p>
</div>
</div>
<div class="section" id="management-operations">
Modified: qpid/site/input/releases/qpid-dispatch-master/book/technical_details.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/book/technical_details.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/book/technical_details.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/book/technical_details.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="technical-details-and-specifications">
<h1>3. Technical Details and Specifications<a class="headerlink" href="#technical-details-and-specifications" title="Permalink to this headline">.</a></h1>
Modified: qpid/site/input/releases/qpid-dispatch-master/book/tools.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/book/tools.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/book/tools.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/book/tools.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="tools">
<h1>2.2. Tools<a class="headerlink" href="#tools" title="Permalink to this headline">.</a></h1>
@@ -52,18 +51,22 @@ are attached to other routers in a netwo
to not only view but modify the configuration of a running dispatch
router.</p>
<p>For example you can query all the connection entities in the router:</p>
-<div class="highlight-python"><pre>$ qdmanage query --type connection</pre>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ qdmanage query --type connection
+</pre></div>
</div>
<p>To enable logging debug and higher level messages by default:</p>
-<div class="highlight-python"><pre>$ qdmanage update log/DEFAULT enable=debug+</pre>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ qdmanage update log/DEFAULT enable=debug+
+</pre></div>
</div>
<p>In fact, everything that can be configured in the configuration file can
also be created in a running router via management. For example to
create a new listener in a running router:</p>
-<div class="highlight-python"><pre>$ qdmanage create type=listener port=5555</pre>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ qdmanage create type=listener port=5555
+</pre></div>
</div>
<p>Now you can connect to port 5555, for exampple:</p>
-<div class="highlight-python"><pre>$ qdmanage query -b localhost:5555 --type listener</pre>
+<div class="highlight-python"><div class="highlight"><pre><span></span>$ qdmanage query -b localhost:5555 --type listener
+</pre></div>
</div>
<p>For complete details see the <cite>qdmanage(8)</cite> man page and the output of
<cite>qdmanage –help</cite>. Also for details of what can be configured see the
Modified: qpid/site/input/releases/qpid-dispatch-master/book/using.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/book/using.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/book/using.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/book/using.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="using-qpid-dispatch">
<h1>2. Using Qpid Dispatch<a class="headerlink" href="#using-qpid-dispatch" title="Permalink to this headline">.</a></h1>
Modified: qpid/site/input/releases/qpid-dispatch-master/index.md
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/index.md?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/index.md (original)
+++ qpid/site/input/releases/qpid-dispatch-master/index.md Mon Apr 25 18:13:24 2016
@@ -27,7 +27,7 @@ Code and documentation found here may be
incomplete. For a smoother experience, see the [current stable
release]({{current_dispatch_release_url}}/index.html).
-This content was generated at 12:55 on Tuesday, 05 April 2016.
+This content was generated at 13:53 on Monday, 25 April 2016.
</div>
Modified: qpid/site/input/releases/qpid-dispatch-master/man/qdmanage.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/man/qdmanage.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/man/qdmanage.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/man/qdmanage.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="qdmanage-manual-page">
<h1>qdmanage manual page<a class="headerlink" href="#qdmanage-manual-page" title="Permalink to this headline">.</a></h1>
@@ -62,19 +61,41 @@ formatted output.</dd>
</div>
<div class="section" id="options">
<h2>Options<a class="headerlink" href="#options" title="Permalink to this headline">.</a></h2>
-<p>Command ‘[‘/tmp/ross/transom/qpid-dispatch-master/tools/qdmanage’, ‘–help’]’ returned non-zero exit status 1</p>
-<dl class="docutils">
-<dt>Traceback (most recent call last):</dt>
-<dd><dl class="first last docutils">
-<dt>File “/tmp/ross/transom/qpid-dispatch-master/tools/qdmanage”, line 24, in <module></dt>
-<dd>from qpid_dispatch.management.client import Node, Url</dd>
-<dt>File “/tmp/ross/transom/qpid-dispatch-master/python/qpid_dispatch/management/client.py”, line 25, in <module></dt>
-<dd>import proton</dd>
-</dl>
-</dd>
-</dl>
-<p>ImportError: No module named proton</p>
-<p>Run python script ‘/tmp/ross/transom/qpid-dispatch-master/doc/man/help2rst.py’:CalledProcessError: Command ‘[‘/tmp/ross/transom/qpid-dispatch-master/tools/qdmanage’, ‘–help’]’ returned non-zero exit status 1</p>
+<p>-h, –help
+: show this help message and exit</p>
+<p>–version
+: Print version and exit.</p>
+<p>–type=TYPE
+: Type of entity to operate on.</p>
+<p>–name=NAME
+: Name of entity to operate on.</p>
+<p>–identity=ID
+: Identity of entity to operate on.</p>
+<p>–indent=INDENT
+: Pretty-printing indent. -1 means don’t pretty-print</p>
+<p>–stdin
+: Read attributes as JSON map or list of maps from</p>
+<p>–body=BODY
+: JSON value to use as body of a non-standard operation</p>
+<p>–properties=PROPERTIES
+: JSON map to use as properties for a non-standard operation call.</p>
+<div class="section" id="connection-options">
+<h3>Connection Options<a class="headerlink" href="#connection-options" title="Permalink to this headline">.</a></h3>
+<p>-b URL, –bus=URL
+: URL of the messaging bus to connect to (default</p>
+<p>-r ROUTER-ID, –router=ROUTER-ID
+: Router to be queried</p>
+<p>-t SECS, –timeout=SECS
+: Maximum time to wait for connection in seconds (default 5)</p>
+<p>–ssl-certificate=CERT
+: Client SSL certificate (PEM Format)</p>
+<p>–ssl-key=KEY
+: Client SSL private key (PEM Format)</p>
+<p>–ssl-trustfile=TRUSTED-CA-DB
+: Trusted Certificate Authority Database file (PEM Format)</p>
+<p>–ssl-password=PASSWORD
+: Certificate password, will be prompted if not specifed.</p>
+</div>
</div>
<div class="section" id="files">
<h2>Files<a class="headerlink" href="#files" title="Permalink to this headline">.</a></h2>
@@ -88,20 +109,25 @@ formatted output.</dd>
<div class="section" id="examples">
<h2>Examples<a class="headerlink" href="#examples" title="Permalink to this headline">.</a></h2>
<p>Show the logging configuration</p>
-<div class="highlight-python"><pre>qdmanage query --type=log</pre>
+<div class="highlight-python"><div class="highlight"><pre><span></span>qdmanage query --type=log
+</pre></div>
</div>
<p>Enable debug and higher log messages by default:</p>
-<div class="highlight-python"><pre>qdmanage udpdate name=log/DEFAULT enable=debug+</pre>
+<div class="highlight-python"><div class="highlight"><pre><span></span>qdmanage udpdate name=log/DEFAULT enable=debug+
+</pre></div>
</div>
<p>Enable trace log messages only for the MESSAGE moudle and direct MESSAGE
logs to the file “test.log”</p>
-<div class="highlight-python"><pre>qdmanage udpdate name=log/MESSAGE enable=trace output=test.log</pre>
+<div class="highlight-python"><div class="highlight"><pre><span></span>qdmanage udpdate name=log/MESSAGE enable=trace output=test.log
+</pre></div>
</div>
<p>Set MESSAGE logging back to the default:</p>
-<div class="highlight-python"><pre>qdmanage udpdate name=log/MESSAGE enable=default</pre>
+<div class="highlight-python"><div class="highlight"><pre><span></span>qdmanage udpdate name=log/MESSAGE enable=default
+</pre></div>
</div>
<p>Disable MESSAGE logging:</p>
-<div class="highlight-python"><pre>qdmanage udpdate name=log/MESSAGE enable=none</pre>
+<div class="highlight-python"><div class="highlight"><pre><span></span>qdmanage udpdate name=log/MESSAGE enable=none
+</pre></div>
</div>
</div>
<div class="section" id="see-also">
Modified: qpid/site/input/releases/qpid-dispatch-master/man/qdrouterd.conf.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/man/qdrouterd.conf.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/man/qdrouterd.conf.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/man/qdrouterd.conf.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="qdrouterd-conf-manual-page">
<h1>qdrouterd.conf manual page<a class="headerlink" href="#qdrouterd-conf-manual-page" title="Permalink to this headline">.</a></h1>
@@ -10,11 +9,12 @@
<div class="section" id="description">
<h2>Description<a class="headerlink" href="#description" title="Permalink to this headline">.</a></h2>
<p>The configuration file is made up of sections with this syntax:</p>
-<div class="highlight-python"><pre>SECTION-NAME {
+<div class="highlight-python"><div class="highlight"><pre><span></span>SECTION-NAME {
ATTRIBUTE-NAME: ATTRIBUTE-VALUE
ATTRIBUTE-NAME: ATTRIBUTE-VALUE
...
-}</pre>
+}
+</pre></div>
</div>
<p>There are two types of sections:</p>
<p><em>Configuration sections</em> correspond to configuration entities. They can be queried and
@@ -25,7 +25,7 @@ one or more entity sections.</p>
that can be included in multiple “listener” entities. Here’s an example, note
how the ‘ssl-profile’ attribute of ‘listener’ sections references the ‘name’
attribute of ‘ssl-profile’ sections.</p>
-<div class="highlight-python"><pre>ssl-profile {
+<div class="highlight-python"><div class="highlight"><pre><span></span>ssl-profile {
name: ssl-profile-one
cert-db: ca-certificate-1.pem
cert-file: server-certificate-1.pem
@@ -37,7 +37,8 @@ listener {
addr: 0.0.0.0
port: 20102
sasl-mechanisms: ANONYMOUS
-}</pre>
+}
+</pre></div>
</div>
</div>
<div class="section" id="annotation-sections">
@@ -61,7 +62,9 @@ listener {
<p>Used by: <strong>listener</strong>, <strong>connector</strong>.</p>
<dl class="docutils">
<dt><em>role</em> (One of [‘normal’, ‘inter-router’, ‘route-container’, ‘on-demand’], default=’normal’)</dt>
-<dd>The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections.</dd>
+<dd>The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.</dd>
+<dt><em>cost</em> (integer, default=‘1’)</dt>
+<dd>For the ‘inter-router’ role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.</dd>
</dl>
</div>
<div class="section" id="sslprofile">
@@ -138,7 +141,9 @@ listener {
<dt><em>protocolFamily</em> (One of [‘IPv4’, ‘IPv6’])</dt>
<dd>[‘IPv4’, ‘IPv6’] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.</dd>
<dt><em>role</em> (One of [‘normal’, ‘inter-router’, ‘route-container’, ‘on-demand’], default=’normal’)</dt>
-<dd>The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections.</dd>
+<dd>The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.</dd>
+<dt><em>cost</em> (integer, default=‘1’)</dt>
+<dd>For the ‘inter-router’ role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.</dd>
<dt><em>certDb</em> (path)</dt>
<dd>The path to the database that contains the public certificates of trusted certificate authorities (CA).</dd>
<dt><em>certFile</em> (path)</dt>
@@ -163,8 +168,8 @@ listener {
<dd>yes: Require the use of SSL or TLS on the connection; no: Allow clients to connect without SSL or TLS.</dd>
<dt><em>trustedCerts</em> (path)</dt>
<dd>This optional setting can be used to reduce the set of available CAs for client authentication. If used, this setting must provide a path to a PEM file that contains the trusted certificates.</dd>
-<dt><em>maxFrameSize</em> (integer, default=65536)</dt>
-<dd>Defaults to 65536. If specified, it is the maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.</dd>
+<dt><em>maxFrameSize</em> (integer, default=16384)</dt>
+<dd>Defaults to 16384. If specified, it is the maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.</dd>
<dt><em>idleTimeoutSeconds</em> (integer, default=16)</dt>
<dd>The idle timeout, in seconds, for connections through this listener. If no frames are received on the connection for this time interval, the connection shall be closed.</dd>
<dt><em>requirePeerAuth</em> (boolean)</dt>
@@ -191,7 +196,9 @@ listener {
<dt><em>protocolFamily</em> (One of [‘IPv4’, ‘IPv6’])</dt>
<dd>[‘IPv4’, ‘IPv6’] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.</dd>
<dt><em>role</em> (One of [‘normal’, ‘inter-router’, ‘route-container’, ‘on-demand’], default=’normal’)</dt>
-<dd>The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections.</dd>
+<dd>The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.</dd>
+<dt><em>cost</em> (integer, default=‘1’)</dt>
+<dd>For the ‘inter-router’ role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.</dd>
<dt><em>certDb</em> (path)</dt>
<dd>The path to the database that contains the public certificates of trusted certificate authorities (CA).</dd>
<dt><em>certFile</em> (path)</dt>
Modified: qpid/site/input/releases/qpid-dispatch-master/man/qdrouterd.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/man/qdrouterd.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/man/qdrouterd.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/man/qdrouterd.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="qdrouterd-manual-page">
<h1>qdrouterd manual page<a class="headerlink" href="#qdrouterd-manual-page" title="Permalink to this headline">.</a></h1>
Modified: qpid/site/input/releases/qpid-dispatch-master/man/qdstat.html.in
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-master/man/qdstat.html.in?rev=1740870&r1=1740869&r2=1740870&view=diff
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-master/man/qdstat.html.in (original)
+++ qpid/site/input/releases/qpid-dispatch-master/man/qdstat.html.in Mon Apr 25 18:13:24 2016
@@ -1,5 +1,4 @@
-
<div class="section" id="qdstat-manual-page">
<h1>qdstat manual page<a class="headerlink" href="#qdstat-manual-page" title="Permalink to this headline">.</a></h1>
@@ -15,19 +14,49 @@ as memory use.</p>
</div>
<div class="section" id="options">
<h2>Options<a class="headerlink" href="#options" title="Permalink to this headline">.</a></h2>
-<p>Command ‘[‘/tmp/ross/transom/qpid-dispatch-master/tools/qdstat’, ‘–help’]’ returned non-zero exit status 1</p>
-<dl class="docutils">
-<dt>Traceback (most recent call last):</dt>
-<dd><dl class="first last docutils">
-<dt>File “/tmp/ross/transom/qpid-dispatch-master/tools/qdstat”, line 30, in <module></dt>
-<dd>from qpid_dispatch.management.client import Url, Node, Entity</dd>
-<dt>File “/tmp/ross/transom/qpid-dispatch-master/python/qpid_dispatch/management/client.py”, line 25, in <module></dt>
-<dd>import proton</dd>
-</dl>
-</dd>
-</dl>
-<p>ImportError: No module named proton</p>
-<p>Run python script ‘/tmp/ross/transom/qpid-dispatch-master/doc/man/help2rst.py’:CalledProcessError: Command ‘[‘/tmp/ross/transom/qpid-dispatch-master/tools/qdstat’, ‘–help’]’ returned non-zero exit status 1</p>
+<p>-h, –help
+: show this help message and exit</p>
+<p>–version
+: Print version and exit.</p>
+<p>-g, –general
+: Show General Router Stats</p>
+<p>-c, –connections
+: Show Connections</p>
+<p>-l, –links
+: Show Router Links</p>
+<p>-n, –nodes
+: Show Router Nodes</p>
+<p>-a, –address
+: Show Router Addresses</p>
+<p>-m, –memory
+: Show Router Memory Stats</p>
+<p>–autolinks
+: Show Auto Links</p>
+<p>–linkroutes
+: Show Link Routes</p>
+<p>-v, –verbose
+: Show maximum detail</p>
+<p>–log
+: Show recent log entries</p>
+<p>–limit=LIMIT
+: Limit number of log entries</p>
+<div class="section" id="connection-options">
+<h3>Connection Options<a class="headerlink" href="#connection-options" title="Permalink to this headline">.</a></h3>
+<p>-b URL, –bus=URL
+: URL of the messaging bus to connect to (default</p>
+<p>-r ROUTER-ID, –router=ROUTER-ID
+: Router to be queried</p>
+<p>-t SECS, –timeout=SECS
+: Maximum time to wait for connection in seconds (default 5)</p>
+<p>–ssl-certificate=CERT
+: Client SSL certificate (PEM Format)</p>
+<p>–ssl-key=KEY
+: Client SSL private key (PEM Format)</p>
+<p>–ssl-trustfile=TRUSTED-CA-DB
+: Trusted Certificate Authority Database file (PEM Format)</p>
+<p>–ssl-password=PASSWORD
+: Certificate password, will be prompted if not specifed.</p>
+</div>
</div>
<div class="section" id="see-also">
<h2>See also<a class="headerlink" href="#see-also" title="Permalink to this headline">.</a></h2>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org