http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/book/technical_details.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/book/technical_details.html.in b/input/releases/qpid-dispatch-0.6.1/book/technical_details.html.in new file mode 100644 index 0000000..139ea56 --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/book/technical_details.html.in @@ -0,0 +1,68 @@ + + + <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> +<div class="toctree-wrapper compound"> +<ul> +<li class="toctree-l1"><a class="reference internal" href="client_compatibility.html">3.1. Client Compatibility</a></li> +<li class="toctree-l1"><a class="reference internal" href="addressing.html">3.2. Addressing</a><ul> +<li class="toctree-l2"><a class="reference internal" href="addressing.html#routing-patterns">3.2.1. Routing patterns</a></li> +<li class="toctree-l2"><a class="reference internal" href="addressing.html#routing-mechanisms">3.2.2. Routing mechanisms</a><ul> +<li class="toctree-l3"><a class="reference internal" href="addressing.html#message-routing">3.2.2.1. Message routing</a></li> +</ul> +</li> +</ul> +</li> +<li class="toctree-l1"><a class="reference internal" href="amqp-mapping.html">3.3. AMQP Mapping</a><ul> +<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html#message-annotations">3.3.1. Message Annotations</a></li> +<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html#source-target-capabilities">3.3.2. Source/Target Capabilities</a></li> +<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html#dynamic-node-properties">3.3.3. Dynamic-Node-Properties</a></li> +<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html#addresses-and-address-formats">3.3.4. Addresses and Address Formats</a><ul> +<li class="toctree-l3"><a class="reference internal" href="amqp-mapping.html#address-patterns">3.3.4.1. Address Patterns</a></li> +<li class="toctree-l3"><a class="reference internal" href="amqp-mapping.html#supported-addresses">3.3.4.2. Supported Addresses</a></li> +</ul> +</li> +<li class="toctree-l2"><a class="reference internal" href="amqp-mapping.html#implementation-of-the-amqp-management-specification">3.3.5. Implementation of the AMQP Management Specification</a></li> +</ul> +</li> +<li class="toctree-l1"><a class="reference internal" href="schema.html">3.4. Management Schema</a><ul> +<li class="toctree-l2"><a class="reference internal" href="schema.html#configuration-entities">3.4.1. Configuration Entities</a><ul> +<li class="toctree-l3"><a class="reference internal" href="schema.html#container">3.4.1.1. container</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#router">3.4.1.2. router</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#listener">3.4.1.3. listener</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#connector">3.4.1.4. connector</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#log">3.4.1.5. log</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#fixedaddress">3.4.1.6. fixedAddress</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#waypoint">3.4.1.7. waypoint</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#linkroutepattern">3.4.1.8. linkRoutePattern</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#address">3.4.1.9. address</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#linkroute">3.4.1.10. linkRoute</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#autolink">3.4.1.11. autoLink</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#console">3.4.1.12. console</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#policy">3.4.1.13. policy</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#policyruleset">3.4.1.14. policyRuleset</a></li> +</ul> +</li> +<li class="toctree-l2"><a class="reference internal" href="schema.html#operational-entities">3.4.2. Operational Entities</a><ul> +<li class="toctree-l3"><a class="reference internal" href="schema.html#org-amqp-management">3.4.2.1. org.amqp.management</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#management">3.4.2.2. management</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#router-link">3.4.2.3. router.link</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#router-address">3.4.2.4. router.address</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#router-node">3.4.2.5. router.node</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#connection">3.4.2.6. connection</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#allocator">3.4.2.7. allocator</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#policystats">3.4.2.8. policyStats</a></li> +</ul> +</li> +<li class="toctree-l2"><a class="reference internal" href="schema.html#management-operations">3.4.3. Management Operations</a><ul> +<li class="toctree-l3"><a class="reference internal" href="schema.html#operations-for-all-entity-types">3.4.3.1. Operations for all entity types</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#operations-for-org-amqp-management-entity-type">3.4.3.2. Operations for <cite>org.amqp.management</cite> entity type</a></li> +<li class="toctree-l3"><a class="reference internal" href="schema.html#operations-for-management-entity-type">3.4.3.3. Operations for <cite>management</cite> entity type</a></li> +</ul> +</li> +</ul> +</li> +</ul> +</div> +</div> +
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/book/tools.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/book/tools.html.in b/input/releases/qpid-dispatch-0.6.1/book/tools.html.in new file mode 100644 index 0000000..cb7aefb --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/book/tools.html.in @@ -0,0 +1,76 @@ + + + <div class="section" id="tools"> +<h1>2.2. Tools<a class="headerlink" href="#tools" title="Permalink to this headline">.</a></h1> +<div class="section" id="qdstat"> +<h2>2.2.1. qdstat<a class="headerlink" href="#qdstat" title="Permalink to this headline">.</a></h2> +<p><em>qdstat</em> is a command line tool that lets you view the status of a +Dispatch Router. The following options are useful for seeing what the +router is doing:</p> +<table border="1" class="docutils"> +<colgroup> +<col width="15%" /> +<col width="85%" /> +</colgroup> +<thead valign="bottom"> +<tr class="row-odd"><th class="head"><em>Option</em></th> +<th class="head"><em>Description</em></th> +</tr> +</thead> +<tbody valign="top"> +<tr class="row-even"><td>-l</td> +<td>Print a list of AMQP links attached to the router. Links are +unidirectional. Outgoing links are usually associated with a subscription +address. The tool distinguishes between <em>endpoint</em> links and <em>router</em> +links. Endpoint links are attached to clients using the router. Router links +are attached to other routers in a network of routbers.</td> +</tr> +<tr class="row-odd"><td>-a</td> +<td>Print a list of addresses known to the router.</td> +</tr> +<tr class="row-even"><td>-n</td> +<td>Print a list of known routers in the network.</td> +</tr> +<tr class="row-odd"><td>-c</td> +<td>Print a list of connections to the router.</td> +</tr> +<tr class="row-even"><td>–autolinks</td> +<td>Print a list of configured auto-links.</td> +</tr> +<tr class="row-odd"><td>–linkroutes</td> +<td>Print a list of configures link-routes.</td> +</tr> +</tbody> +</table> +<p>For complete details see the <cite>qdstat(8)</cite> man page and the output of +<cite>qdstat –help</cite>.</p> +</div> +<div class="section" id="qdmanage"> +<h2>2.2.2. qdmanage<a class="headerlink" href="#qdmanage" title="Permalink to this headline">.</a></h2> +<p><em>qdmanage</em> is a general-purpose AMQP management client that allows you +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"><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"><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"><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"><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 +<cite>qdrouterd.conf(5)</cite> man page.</p> +</div> +</div> + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/book/using.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/book/using.html.in b/input/releases/qpid-dispatch-0.6.1/book/using.html.in new file mode 100644 index 0000000..de46f1d --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/book/using.html.in @@ -0,0 +1,32 @@ + + + <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> +<div class="toctree-wrapper compound"> +<ul> +<li class="toctree-l1"><a class="reference internal" href="default_config.html">2.1. Configuration</a></li> +<li class="toctree-l1"><a class="reference internal" href="tools.html">2.2. Tools</a><ul> +<li class="toctree-l2"><a class="reference internal" href="tools.html#qdstat">2.2.1. qdstat</a></li> +<li class="toctree-l2"><a class="reference internal" href="tools.html#qdmanage">2.2.2. qdmanage</a></li> +</ul> +</li> +<li class="toctree-l1"><a class="reference internal" href="basic_usage.html">2.3. Basic Usage and Examples</a><ul> +<li class="toctree-l2"><a class="reference internal" href="basic_usage.html#standalone-and-interior-modes">2.3.1. Standalone and Interior Modes</a></li> +<li class="toctree-l2"><a class="reference internal" href="basic_usage.html#mobile-subscribers">2.3.2. Mobile Subscribers</a></li> +<li class="toctree-l2"><a class="reference internal" href="basic_usage.html#dynamic-reply-to">2.3.3. Dynamic Reply-To</a></li> +</ul> +</li> +<li class="toctree-l1"><a class="reference internal" href="link_routing.html">2.4. Link Routing</a><ul> +<li class="toctree-l2"><a class="reference internal" href="link_routing.html#configuration">2.4.1. Configuration</a></li> +</ul> +</li> +<li class="toctree-l1"><a class="reference internal" href="auto_links.html">2.5. Indirect Waypoints and Auto-Links</a><ul> +<li class="toctree-l2"><a class="reference internal" href="auto_links.html#queue-waypoint-example">2.5.1. Queue Waypoint Example</a></li> +<li class="toctree-l2"><a class="reference internal" href="auto_links.html#sharded-queue-example">2.5.2. Sharded Queue Example</a></li> +<li class="toctree-l2"><a class="reference internal" href="auto_links.html#dynamically-adding-shards">2.5.3. Dynamically Adding Shards</a></li> +</ul> +</li> +</ul> +</div> +</div> + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/index.md ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/index.md b/input/releases/qpid-dispatch-0.6.1/index.md new file mode 100644 index 0000000..7e4fd88 --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/index.md @@ -0,0 +1,66 @@ +;; +;; Licensed to the Apache Software Foundation (ASF) under one +;; or more contributor license agreements. See the NOTICE file +;; distributed with this work for additional information +;; regarding copyright ownership. The ASF licenses this file +;; to you under the Apache License, Version 2.0 (the +;; "License"); you may not use this file except in compliance +;; with the License. You may obtain a copy of the License at +;; +;; http://www.apache.org/licenses/LICENSE-2.0 +;; +;; Unless required by applicable law or agreed to in writing, +;; software distributed under the License is distributed on an +;; "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +;; KIND, either express or implied. See the License for the +;; specific language governing permissions and limitations +;; under the License. +;; + +# Qpid Dispatch 0.6.1 + +Dispatch is a lightweight AMQP message router library. More about +[Qpid +Dispatch]({{site_url}}/components/dispatch-router/index.html). + +For a detailed list of the changes in this release, see the [release +notes](release-notes.html). + +## Downloads + +It's important to [verify the +integrity]({{site_url}}/download.html#verify-what-you-download) of +the files you download. + +| Content | Download | Verify | +|---------|----------|--------| +| Dispatch router | [qpid-dispatch-0.6.1.tar.gz](http://archive.apache.org/dist/qpid/dispatch/0.6.1/qpid-dispatch-0.6.1.tar.gz) | [PGP](http://archive.apache.org/dist/qpid/dispatch/0.6.1/qpid-dispatch-0.6.1.tar.gz.asc) | + +## Documentation + + +<div class="two-column" markdown="1"> + + - [Installing Qpid Dispatch](https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;a=blob_plain;f=README;hb=0.6.1) + - [Dispatch Router User Guide](book/book.html) + - [qdrouterd](man/qdrouterd.html) - Router daemon + - [qdrouterd.conf](man/qdrouterd.conf.html) - Daemon configuration + - [qdstat](man/qdstat.html) - Get router statistics + - [qdmanage](man/qdmanage.html) - Manage the router + +</div> + + +## More information + + - [All release artefacts](http://archive.apache.org/dist/qpid/dispatch/0.6.1) + - [Resolved issues in JIRA](https://issues.apache.org/jira/issues/?jql=project+%3D+DISPATCH+AND+fixVersion+%3D+%270.6.1%27+AND+resolution+%3D+%27fixed%27+ORDER+BY+priority+DESC) + - [Source repository tag](https://git-wip-us.apache.org/repos/asf/qpid-dispatch.git/tree/refs/tags/0.6.1) + +<script type="text/javascript"> + _deferredFunctions.push(function() { + if ("0.6.1" === "{{current_dispatch_release}}") { + _modifyCurrentReleaseLinks(); + } + }); +</script> \ No newline at end of file http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/man/qdmanage.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/man/qdmanage.html.in b/input/releases/qpid-dispatch-0.6.1/man/qdmanage.html.in new file mode 100644 index 0000000..865ef61 --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/man/qdmanage.html.in @@ -0,0 +1,139 @@ + + + <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> +<div class="section" id="synopsis"> +<h2>Synopsis<a class="headerlink" href="#synopsis" title="Permalink to this headline">.</a></h2> +<p>qdmanage <em>operation</em> [<em>options...</em>] [<em>arguments...</em>]</p> +</div> +<div class="section" id="description"> +<h2>Description<a class="headerlink" href="#description" title="Permalink to this headline">.</a></h2> +<p>An AMQP management client for use with qdrouterd. Sends AMQP management +operations requests and prints the response in JSON format. This is a +generic AMQP management tool and can be used with any standard AMQP +managed endpoint, not just with qdrouter.</p> +</div> +<div class="section" id="operations"> +<h2>Operations<a class="headerlink" href="#operations" title="Permalink to this headline">.</a></h2> +<dl class="docutils"> +<dt><cite>query</cite> [<em>ATTR</em>...]</dt> +<dd>Print the attributes named in the ATTR list or all attributes if +none are listed. Print attributes for all entities by default, use +–type, –name and –identity options to restrict what is printed.</dd> +<dt><cite>create</cite> [<em>ATTR=VALUE</em>...]</dt> +<dd>Create a new entity with the specified attributes. With the –stdin +option, read attributes from stdin. This can be a JSON map of +attributes to create a single entity, or a JSON list of maps to +create multiple entitiees.</dd> +<dt><cite>read</cite></dt> +<dd>Print the attributes of an entity specified by the –name or +–identity options. With the –stdin option, create entities based +on data from stdin. This can be a JSON map of attributes to create a +single entity, or a JSON list of maps to create multiple entitiees.</dd> +<dt><cite>update</cite> [<em>ATTR=VALUE</em>...]</dt> +<dd>Update the attributes of an existing entity. With the –stdin +option, read attributes from stdin. This can be a JSON map of +attributes to update a single entity, or a JSON list of maps to +update multiple entitiees. If an ATTR name is listed with no =VALUE, +that attribute will be deleted from the entity.</dd> +<dt><cite>delete</cite></dt> +<dd>Delete an entity specified by the –name or –identity options.</dd> +<dt><cite>get-types</cite> [<em>TYPE</em>]</dt> +<dd>List entity types with their base types. With no arguments list all +types.</dd> +<dt><cite>get-operations</cite> [<em>TYPE</em>]</dt> +<dd>List entity types with their operations. With no arguments list all +types.</dd> +<dt><cite>get-attributes</cite> [<em>TYPE</em>]</dt> +<dd>List entity types with their attributes. With no arguments list all +types.</dd> +<dt><cite>get-annotations</cite> [<em>TYPE</em>]</dt> +<dd>List entity types with their annotations. With no arguments list all +types.</dd> +<dt><cite>get-mgmt-nodes</cite></dt> +<dd>List all other known management nodes connected to this one.</dd> +<dt><cite>get-json-schema</cite> [<em>INDENT</em>]</dt> +<dd>Get the router schema in JSON format. Optional integer indent for +formatted output.</dd> +<dt><cite>get-log</cite> [<em>INDENT</em>]</dt> +<dd>Get recent log entries from the router.</dd> +</dl> +</div> +<div class="section" id="options"> +<h2>Options<a class="headerlink" href="#options" title="Permalink to this headline">.</a></h2> +<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> +<dl class="docutils"> +<dt>/usr/local/share/doc/qpid-dispatch/qdrouter.json</dt> +<dd>Management schema for qdrouterd.</dd> +<dt>/usr/local/share/doc/qpid-dispatch/qdrouter.json.readme.txt</dt> +<dd>Explanation of the management schema.</dd> +</dl> +</div> +<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"><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"><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"><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"><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"><div class="highlight"><pre><span></span>qdmanage udpdate name=log/MESSAGE enable=none +</pre></div> +</div> +</div> +<div class="section" id="see-also"> +<h2>See also<a class="headerlink" href="#see-also" title="Permalink to this headline">.</a></h2> +<p><em>qdrouterd(8)</em>, <em>qdstat(8)</em>, <em>qdrouterd.conf(5)</em></p> +<p><a class="reference external" href="http://qpid.apache.org/components/dispatch-router";>http://qpid.apache.org/components/dispatch-router</a></p> +</div> +</div> + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/man/qdrouterd.conf.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/man/qdrouterd.conf.html.in b/input/releases/qpid-dispatch-0.6.1/man/qdrouterd.conf.html.in new file mode 100644 index 0000000..6e8b211 --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/man/qdrouterd.conf.html.in @@ -0,0 +1,405 @@ + + + <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> +<div class="section" id="synopsis"> +<h2>Synopsis<a class="headerlink" href="#synopsis" title="Permalink to this headline">.</a></h2> +<p>qdroutered.conf is the configuration file for the dispatch router.</p> +</div> +<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"><div class="highlight"><pre><span></span>SECTION-NAME { + ATTRIBUTE-NAME: ATTRIBUTE-VALUE + ATTRIBUTE-NAME: ATTRIBUTE-VALUE + ... +} +</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 +configured via management tools as well as via the configuration file.</p> +<p><em>Annotation sections</em> define a group of attribute values that can be included in +one or more entity sections.</p> +<p>For example you can define an “ssl-profile” annotation section with SSL credentials +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"><div class="highlight"><pre><span></span>ssl-profile { + name: ssl-profile-one + cert-db: ca-certificate-1.pem + cert-file: server-certificate-1.pem + key-file: server-private-key.pem +} + +listener { + ssl-profile: ssl-profile-one + host: 0.0.0.0 + port: 20102 + sasl-mechanisms: ANONYMOUS +} +</pre></div> +</div> +</div> +<div class="section" id="annotation-sections"> +<h2>Annotation Sections<a class="headerlink" href="#annotation-sections" title="Permalink to this headline">.</a></h2> +<div class="section" id="addrport"> +<h3>addrPort<a class="headerlink" href="#addrport" title="Permalink to this headline">.</a></h3> +<p>Attributes for internet address and port.</p> +<p>Used by: <strong>listener</strong>, <strong>connector</strong>.</p> +<dl class="docutils"> +<dt><em>addr</em> (string, default=‘127.0.0.1’)</dt> +<dd>(DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead</dd> +<dt><em>host</em> (string, default=‘127.0.0.1’)</dt> +<dd>IP address: ipv4 or ipv6 literal or a host name</dd> +<dt><em>port</em> (string, default=’amqp’)</dt> +<dd>Port number or symbolic service name.</dd> +<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> +</dl> +</div> +<div class="section" id="connectionrole"> +<h3>connectionRole<a class="headerlink" href="#connectionrole" title="Permalink to this headline">.</a></h3> +<p>Attribute for the role of a connection.</p> +<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. 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"> +<h3>sslProfile<a class="headerlink" href="#sslprofile" title="Permalink to this headline">.</a></h3> +<p>Attributes for setting TLS/SSL configuration for connections.</p> +<p>Used by: <strong>listener</strong>, <strong>connector</strong>.</p> +<dl class="docutils"> +<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> +<dd>The path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.</dd> +<dt><em>keyFile</em> (path)</dt> +<dd>The path to the file containing the PEM-formatted private key for the above certificate.</dd> +<dt><em>passwordFile</em> (path)</dt> +<dd>If the above private key is password protected, this is the path to a file containing the password that unlocks the certificate key.</dd> +<dt><em>password</em> (string)</dt> +<dd>An alternative to storing the password in a file referenced by passwordFile is to supply the password right here in the configuration file. This option can be used by supplying the password in the ‘password’ option. Don’t use both password and passwordFile in the same profile.</dd> +<dt><em>uidFormat</em> (string)</dt> +<dd>A list of x509 client certificate fields that will be used to build a string that will uniquely identify the client certificate owner. For e.g. a value of ‘cou’ indicates that the uid will consist of c - common name concatenated with o - organization-company name concatenated with u - organization unit; or a value of ‘o2’ indicates that the uid will consist of o (organization name) concatenated with 2 (the sha256 fingerprint of the entire certificate) . Allowed values can be any combination of comma separated ‘c’( ISO3166 two character country code), ‘s’(state or province), ‘l’(Locality; generally - city), ‘o’(Organization - Company Name), ‘u’(Organization Unit - typically certificate type or brand), ‘n’(CommonName - typically a user name for client certificates) and ‘1’(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate wi th say a web browser is the hash of the entire certificate) and 2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).</dd> +<dt><em>displayNameFile</em> (string)</dt> +<dd>The path to the file containing the unique id to dispay name mapping</dd> +</dl> +</div> +</div> +<div class="section" id="configuration-sections"> +<h2>Configuration Sections<a class="headerlink" href="#configuration-sections" title="Permalink to this headline">.</a></h2> +<div class="section" id="container"> +<h3>container<a class="headerlink" href="#container" title="Permalink to this headline">.</a></h3> +<p>(DEPRECATED)Attributes related to the AMQP container. This entity has been deprecated. Use the router entity instead.</p> +<dl class="docutils"> +<dt><em>containerName</em> (string)</dt> +<dd>The name of the AMQP container. If not specified, the container name will be set to a value of the container’s choosing. The automatically assigned container name is not guaranteed to be persistent across restarts of the container.</dd> +<dt><em>workerThreads</em> (integer, default=4)</dt> +<dd>The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .</dd> +<dt><em>debugDump</em> (path)</dt> +<dd>A file to dump debugging information that can’t be logged normally.</dd> +<dt><em>saslConfigPath</em> (path)</dt> +<dd>Absolute path to the SASL configuration file.</dd> +<dt><em>saslConfigName</em> (string)</dt> +<dd>Name of the SASL configuration. This string + ‘.conf’ is the name of the configuration file.</dd> +</dl> +</div> +<div class="section" id="router"> +<h3>router<a class="headerlink" href="#router" title="Permalink to this headline">.</a></h3> +<p>Tracks peer routers and computes routes to destinations.</p> +<dl class="docutils"> +<dt><em>routerId</em> (string)</dt> +<dd>(DEPRECATED) Router’s unique identity. This attribute has been deprecated. Use id instead</dd> +<dt><em>id</em> (string)</dt> +<dd>Router’s unique identity. One of id or routerId is required. The router will fail to start without id or routerId</dd> +<dt><em>mode</em> (One of [‘standalone’, ‘interior’], default=’standalone’)</dt> +<dd>In standalone mode, the router operates as a single component. It does not participate in the routing protocol and therefore will not cooperate with other routers. In interior mode, the router operates in cooperation with other interior routers in an interconnected network.</dd> +<dt><em>helloInterval</em> (integer, default=1)</dt> +<dd>Interval in seconds between HELLO messages sent to neighbor routers.</dd> +<dt><em>helloMaxAge</em> (integer, default=3)</dt> +<dd>Time in seconds after which a neighbor is declared lost if no HELLO is received.</dd> +<dt><em>raInterval</em> (integer, default=30)</dt> +<dd>Interval in seconds between Router-Advertisements sent to all routers in a stable network.</dd> +<dt><em>raIntervalFlux</em> (integer, default=4)</dt> +<dd>Interval in seconds between Router-Advertisements sent to all routers during topology fluctuations.</dd> +<dt><em>remoteLsMaxAge</em> (integer, default=60)</dt> +<dd>Time in seconds after which link state is declared stale if no RA is received.</dd> +<dt><em>mobileAddrMaxAge</em> (integer, default=60)</dt> +<dd>(DEPRECATED) This value is no longer used in the router.</dd> +<dt><em>workerThreads</em> (integer, default=4)</dt> +<dd>The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .</dd> +<dt><em>debugDump</em> (path)</dt> +<dd>A file to dump debugging information that can’t be logged normally.</dd> +<dt><em>saslConfigPath</em> (path)</dt> +<dd>Absolute path to the SASL configuration file.</dd> +<dt><em>saslConfigName</em> (string, default=’qdrouterd’)</dt> +<dd>Name of the SASL configuration. This string + ‘.conf’ is the name of the configuration file.</dd> +</dl> +</div> +<div class="section" id="listener"> +<h3>listener<a class="headerlink" href="#listener" title="Permalink to this headline">.</a></h3> +<p>Listens for incoming connections to the router.</p> +<p>Annotations: <strong>addrPort</strong>, <strong>connectionRole</strong>, <strong>sslProfile</strong>.</p> +<dl class="docutils"> +<dt><em>addr</em> (string, default=‘127.0.0.1’)</dt> +<dd>(DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead</dd> +<dt><em>host</em> (string, default=‘127.0.0.1’)</dt> +<dd>IP address: ipv4 or ipv6 literal or a host name</dd> +<dt><em>port</em> (string, default=’amqp’)</dt> +<dd>Port number or symbolic service name.</dd> +<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. 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> +<dd>The path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.</dd> +<dt><em>keyFile</em> (path)</dt> +<dd>The path to the file containing the PEM-formatted private key for the above certificate.</dd> +<dt><em>passwordFile</em> (path)</dt> +<dd>If the above private key is password protected, this is the path to a file containing the password that unlocks the certificate key.</dd> +<dt><em>password</em> (string)</dt> +<dd>An alternative to storing the password in a file referenced by passwordFile is to supply the password right here in the configuration file. This option can be used by supplying the password in the ‘password’ option. Don’t use both password and passwordFile in the same profile.</dd> +<dt><em>uidFormat</em> (string)</dt> +<dd>A list of x509 client certificate fields that will be used to build a string that will uniquely identify the client certificate owner. For e.g. a value of ‘cou’ indicates that the uid will consist of c - common name concatenated with o - organization-company name concatenated with u - organization unit; or a value of ‘o2’ indicates that the uid will consist of o (organization name) concatenated with 2 (the sha256 fingerprint of the entire certificate) . Allowed values can be any combination of comma separated ‘c’( ISO3166 two character country code), ‘s’(state or province), ‘l’(Locality; generally - city), ‘o’(Organization - Company Name), ‘u’(Organization Unit - typically certificate type or brand), ‘n’(CommonName - typically a user name for client certificates) and ‘1’(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate wi th say a web browser is the hash of the entire certificate) and 2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).</dd> +<dt><em>displayNameFile</em> (string)</dt> +<dd>The path to the file containing the unique id to dispay name mapping</dd> +<dt><em>saslMechanisms</em> (string)</dt> +<dd>Comma separated list of accepted SASL authentication mechanisms.</dd> +<dt><em>authenticatePeer</em> (boolean)</dt> +<dd>yes: Require the peer’s identity to be authenticated; no: Do not require any authentication.</dd> +<dt><em>requireEncryption</em> (boolean)</dt> +<dd>yes: Require the connection to the peer to be encrypted; no: Permit non-encrypted communication with the peer</dd> +<dt><em>requireSsl</em> (boolean)</dt> +<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=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> +<dd>(DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.</dd> +<dt><em>allowUnsecured</em> (boolean)</dt> +<dd>(DEPRECATED) This attribute is now controlled by the requireEncryption attribute.</dd> +<dt><em>allowNoSasl</em> (boolean)</dt> +<dd>(DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.</dd> +<dt><em>stripAnnotations</em> (One of [‘in’, ‘out’, ‘both’, ‘no’], default=’both’)</dt> +<dd>[‘in’, ‘out’, ‘both’, ‘no’] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations</dd> +<dt><em>linkCapacity</em> (integer)</dt> +<dd>The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.</dd> +</dl> +</div> +<div class="section" id="connector"> +<h3>connector<a class="headerlink" href="#connector" title="Permalink to this headline">.</a></h3> +<p>Establishes an outgoing connection from the router.</p> +<p>Annotations: <strong>addrPort</strong>, <strong>connectionRole</strong>, <strong>sslProfile</strong>.</p> +<dl class="docutils"> +<dt><em>addr</em> (string, default=‘127.0.0.1’)</dt> +<dd>(DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead</dd> +<dt><em>host</em> (string, default=‘127.0.0.1’)</dt> +<dd>IP address: ipv4 or ipv6 literal or a host name</dd> +<dt><em>port</em> (string, default=’amqp’)</dt> +<dd>Port number or symbolic service name.</dd> +<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. 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> +<dd>The path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.</dd> +<dt><em>keyFile</em> (path)</dt> +<dd>The path to the file containing the PEM-formatted private key for the above certificate.</dd> +<dt><em>passwordFile</em> (path)</dt> +<dd>If the above private key is password protected, this is the path to a file containing the password that unlocks the certificate key.</dd> +<dt><em>password</em> (string)</dt> +<dd>An alternative to storing the password in a file referenced by passwordFile is to supply the password right here in the configuration file. This option can be used by supplying the password in the ‘password’ option. Don’t use both password and passwordFile in the same profile.</dd> +<dt><em>uidFormat</em> (string)</dt> +<dd>A list of x509 client certificate fields that will be used to build a string that will uniquely identify the client certificate owner. For e.g. a value of ‘cou’ indicates that the uid will consist of c - common name concatenated with o - organization-company name concatenated with u - organization unit; or a value of ‘o2’ indicates that the uid will consist of o (organization name) concatenated with 2 (the sha256 fingerprint of the entire certificate) . Allowed values can be any combination of comma separated ‘c’( ISO3166 two character country code), ‘s’(state or province), ‘l’(Locality; generally - city), ‘o’(Organization - Company Name), ‘u’(Organization Unit - typically certificate type or brand), ‘n’(CommonName - typically a user name for client certificates) and ‘1’(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate wi th say a web browser is the hash of the entire certificate) and 2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).</dd> +<dt><em>displayNameFile</em> (string)</dt> +<dd>The path to the file containing the unique id to dispay name mapping</dd> +<dt><em>saslMechanisms</em> (string)</dt> +<dd>Comma separated list of accepted SASL authentication mechanisms.</dd> +<dt><em>allowRedirect</em> (boolean, default=True)</dt> +<dd>Allow the peer to redirect this connection to another address.</dd> +<dt><em>maxFrameSize</em> (integer, default=65536)</dt> +<dd>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 connector. If no frames are received on the connection for this time interval, the connection shall be closed.</dd> +<dt><em>stripAnnotations</em> (One of [‘in’, ‘out’, ‘both’, ‘no’], default=’both’)</dt> +<dd>[‘in’, ‘out’, ‘both’, ‘no’] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations</dd> +<dt><em>linkCapacity</em> (integer)</dt> +<dd>The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.</dd> +<dt><em>verifyHostName</em> (boolean, default=True)</dt> +<dd>yes: Ensures that when initiating a connection (as a client) the host name in the URL to which this connector connects to matches the host name in the digital certificate that the peer sends back as part of the SSL connection; no: Does not perform host name verification</dd> +<dt><em>saslUsername</em> (string)</dt> +<dd>The user name that the connector is using to connect to a peer.</dd> +<dt><em>saslPassword</em> (string)</dt> +<dd>The password that the connector is using to connect to a peer.</dd> +</dl> +</div> +<div class="section" id="log"> +<h3>log<a class="headerlink" href="#log" title="Permalink to this headline">.</a></h3> +<p>Configure logging for a particular module. You can use the <cite>UPDATE</cite> operation to change log settings while the router is running.</p> +<dl class="docutils"> +<dt><em>module</em> (One of [‘ROUTER’, ‘ROUTER_CORE’, ‘ROUTER_HELLO’, ‘ROUTER_LS’, ‘ROUTER_MA’, ‘MESSAGE’, ‘SERVER’, ‘AGENT’, ‘CONTAINER’, ‘CONFIG’, ‘ERROR’, ‘DISPATCH’, ‘POLICY’, ‘DEFAULT’], required)</dt> +<dd>Module to configure. The special module ‘DEFAULT’ specifies defaults for all modules.</dd> +<dt><em>enable</em> (string, default=’default’, required)</dt> +<dd>Levels are: trace, debug, info, notice, warning, error, critical. The enable string is a comma-separated list of levels. A level may have a trailing ‘+’ to enable that level and above. For example ‘trace,debug,warning+’ means enable trace, debug, warning, error and critical. The value ‘none’ means disable logging for the module. The value ‘default’ means use the value from the DEFAULT module.</dd> +<dt><em>timestamp</em> (boolean)</dt> +<dd>Include timestamp in log messages.</dd> +<dt><em>source</em> (boolean)</dt> +<dd>Include source file and line number in log messages.</dd> +<dt><em>output</em> (string)</dt> +<dd>Where to send log messages. Can be ‘stderr’, ‘syslog’ or a file name.</dd> +</dl> +</div> +<div class="section" id="fixedaddress"> +<h3>fixedAddress<a class="headerlink" href="#fixedaddress" title="Permalink to this headline">.</a></h3> +<p>(DEPRECATED) Establishes treatment for addresses starting with a prefix. This entity has been deprecated. Use address instead</p> +<dl class="docutils"> +<dt><em>prefix</em> (string, required)</dt> +<dd>The address prefix (always starting with ‘/’).</dd> +<dt><em>phase</em> (integer)</dt> +<dd>The phase of a multi-hop address passing through one or more waypoints.</dd> +<dt><em>fanout</em> (One of [‘multiple’, ‘single’], default=’multiple’)</dt> +<dd>One of ‘multiple’ or ‘single’. Multiple fanout is a non-competing pattern. If there are multiple consumers using the same address, each consumer will receive its own copy of every message sent to the address. Single fanout is a competing pattern where each message is sent to only one consumer.</dd> +<dt><em>bias</em> (One of [‘closest’, ‘spread’], default=’closest’)</dt> +<dd>Only if fanout is single. One of ‘closest’ or ‘spread’. Closest bias means that messages to an address will always be delivered to the closest (lowest cost) subscribed consumer. Spread bias will distribute the messages across subscribers in an approximately even manner.</dd> +</dl> +</div> +<div class="section" id="waypoint"> +<h3>waypoint<a class="headerlink" href="#waypoint" title="Permalink to this headline">.</a></h3> +<p>(DEPRECATED) A remote node that messages for an address pass through. This entity has been deprecated. Use autoLink instead</p> +<dl class="docutils"> +<dt><em>address</em> (string, required)</dt> +<dd>The AMQP address of the waypoint.</dd> +<dt><em>connector</em> (string, required)</dt> +<dd>The name of the on-demand connector used to reach the waypoint’s container.</dd> +<dt><em>inPhase</em> (integer, default=-1)</dt> +<dd>The phase of the address as it is routed _to_ the waypoint.</dd> +<dt><em>outPhase</em> (integer, default=-1)</dt> +<dd>The phase of the address as it is routed _from_ the waypoint.</dd> +</dl> +</div> +<div class="section" id="linkroutepattern"> +<h3>linkRoutePattern<a class="headerlink" href="#linkroutepattern" title="Permalink to this headline">.</a></h3> +<p>(DEPRECATED) An address pattern to match against link sources and targets to cause the router to link-route the attach across the network to a remote node. This entity has been deprecated. Use linkRoute instead</p> +<dl class="docutils"> +<dt><em>prefix</em> (string, required)</dt> +<dd>An address prefix to match against target and source addresses. This pattern must be of the form ‘<text>.<text1>.<textN>’ or ‘<text>’ or ‘<text>.’ and matches any address that contains that prefix. For example, if the prefix is set to org.apache (or org.apache.), any address that has the prefix ‘org.apache’ (like org.apache.dev) will match. Note that a prefix must not start with a (.), can end in a (.) and can contain zero or more dots (.). Any characters between the dots are simply treated as part of the address</dd> +<dt><em>dir</em> (One of [‘in’, ‘out’, ‘both’], default=’both’)</dt> +<dd>Link direction for match: ‘in’ matches only links inbound to the client; ‘out’ matches only links outbound from the client; ‘both’ matches any link.</dd> +<dt><em>connector</em> (string)</dt> +<dd>The name of the on-demand connector used to reach the target node’s container. If this value is not provided, it means that the target container is expected to be connected to a different router in the network. This prevents links to a link-routable address from being misinterpreted as message-routing links when there is no route to a valid destination available.</dd> +</dl> +</div> +<div class="section" id="address"> +<h3>address<a class="headerlink" href="#address" title="Permalink to this headline">.</a></h3> +<p>Entity type for address configuration. This is used to configure the treatment of message-routed deliveries within a particular address-space. The configuration controls distribution and address phasing.</p> +<dl class="docutils"> +<dt><em>prefix</em> (string, required)</dt> +<dd>The address prefix for the configured settings</dd> +<dt><em>distribution</em> (One of [‘multicast’, ‘closest’, ‘balanced’], default=’balanced’)</dt> +<dd>Treatment of traffic associated with the address</dd> +<dt><em>waypoint</em> (boolean)</dt> +<dd>Designates this address space as being used for waypoints. This will cause the proper address-phasing to be used.</dd> +<dt><em>ingressPhase</em> (integer)</dt> +<dd>Advanced - Override the ingress phase for this address</dd> +<dt><em>egressPhase</em> (integer)</dt> +<dd>Advanced - Override the egress phase for this address</dd> +</dl> +</div> +<div class="section" id="linkroute"> +<h3>linkRoute<a class="headerlink" href="#linkroute" title="Permalink to this headline">.</a></h3> +<p>Entity type for link-route configuration. This is used to identify remote containers that shall be destinations for routed link-attaches. The link-routing configuration applies to an addressing space defined by a prefix.</p> +<dl class="docutils"> +<dt><em>prefix</em> (string, required)</dt> +<dd>The address prefix for the configured settings</dd> +<dt><em>containerId</em> (string)</dt> +<dd>ContainerID for the target container</dd> +<dt><em>connection</em> (string)</dt> +<dd>The name from a connector or listener</dd> +<dt><em>distribution</em> (One of [‘linkBalanced’], default=’linkBalanced’)</dt> +<dd>Treatment of traffic associated with the address</dd> +<dt><em>dir</em> (One of [‘in’, ‘out’], required)</dt> +<dd>The permitted direction of links: ‘in’ means client senders; ‘out’ means client receivers</dd> +</dl> +</div> +<div class="section" id="autolink"> +<h3>autoLink<a class="headerlink" href="#autolink" title="Permalink to this headline">.</a></h3> +<p>Entity type for configuring auto-links. Auto-links are links whose lifecycle is managed by the router. These are typically used to attach to waypoints on remote containers (brokers, etc.).</p> +<dl class="docutils"> +<dt><em>addr</em> (string, required)</dt> +<dd>The address of the provisioned object</dd> +<dt><em>dir</em> (One of [‘in’, ‘out’], required)</dt> +<dd>The direction of the link to be created. In means into the router, out means out of the router.</dd> +<dt><em>phase</em> (integer)</dt> +<dd>The address phase for this link. Defaults to ‘0’ for ‘out’ links and ‘1’ for ‘in’ links.</dd> +<dt><em>containerId</em> (string)</dt> +<dd>ContainerID for the target container</dd> +<dt><em>connection</em> (string)</dt> +<dd>The name from a connector or listener</dd> +</dl> +</div> +<div class="section" id="console"> +<h3>console<a class="headerlink" href="#console" title="Permalink to this headline">.</a></h3> +<p>Start a websocket/tcp proxy and http file server to serve the web console</p> +</div> +<div class="section" id="policy"> +<h3>policy<a class="headerlink" href="#policy" title="Permalink to this headline">.</a></h3> +<p>Defines global connection limit</p> +<dl class="docutils"> +<dt><em>maximumConnections</em> (integer)</dt> +<dd>Global maximum number of concurrent client connections allowed. Zero implies no limit. This limit is always enforced even if no other policy settings have been defined.</dd> +<dt><em>enableAccessRules</em> (boolean)</dt> +<dd>Enable user rule set processing and connection denial.</dd> +<dt><em>policyFolder</em> (path)</dt> +<dd>The path to a folder that holds policyRuleset definition .json files. For a small system the rulesets may all be defined in this file. At a larger scale it is better to have the policy files in their own folder and to have none of the rulesets defined here. All rulesets in all .json files in this folder are processed.</dd> +<dt><em>defaultApplication</em> (string)</dt> +<dd>Application policyRuleset to use for connections with no open.hostname or a hostname that does not match any existing policy. For users that don’t wish to use open.hostname or any multi-tennancy feature, this default policy can be the only policy in effect for the network.</dd> +<dt><em>defaultApplicationEnabled</em> (boolean)</dt> +<dd>Enable defaultApplication policy fallback logic.</dd> +</dl> +</div> +<div class="section" id="policyruleset"> +<h3>policyRuleset<a class="headerlink" href="#policyruleset" title="Permalink to this headline">.</a></h3> +<p>Per application definition of the locations from which users may connect and the groups to which users belong.</p> +<dl class="docutils"> +<dt><em>maxConnections</em> (integer)</dt> +<dd>Maximum number of concurrent client connections allowed. Zero implies no limit.</dd> +<dt><em>maxConnPerUser</em> (integer)</dt> +<dd>Maximum number of concurrent client connections allowed for any single user. Zero implies no limit.</dd> +<dt><em>maxConnPerHost</em> (integer)</dt> +<dd>Maximum number of concurrent client connections allowed for any remote host. Zero implies no limit.</dd> +<dt><em>userGroups</em> (map)</dt> +<dd>A map where each key is a user group name and the corresponding value is a CSV string naming the users in that group. Users who are assigned to one or more groups are deemed ‘restricted’. Restricted users are subject to connection ingress policy and are assigned policy settings based on the assigned user groups. Unrestricted users may be allowed or denied. If unrestricted users are allowed to connect then they are assigned to user group default.</dd> +<dt><em>ingressHostGroups</em> (map)</dt> +<dd>A map where each key is an ingress host group name and the corresponding value is a CSV string naming the IP addresses or address ranges in that group. IP addresses may be FQDN strings or numeric IPv4 or IPv6 host addresses. A host range is two host addresses of the same address family separated with a hyphen. The wildcard host address ‘*’ represents any host address.</dd> +<dt><em>ingressPolicies</em> (map)</dt> +<dd>A map where each key is a user group name and the corresponding value is a CSV string naming the ingress host group names that restrict the ingress host for the user group. Users who are members of the user group are allowed to connect only from a host in one of the named ingress host groups.</dd> +<dt><em>connectionAllowDefault</em> (boolean)</dt> +<dd>Unrestricted users, those who are not members of a defined user group, are allowed to connect to this application. Unrestricted users are assigned to the ‘default’ user group and receive ‘default’ settings.</dd> +<dt><em>settings</em> (map)</dt> +<dd>A map where each key is a user group name and the value is a map of the corresponding settings for that group.</dd> +</dl> +</div> +</div> +<div class="section" id="see-also"> +<h2>See also<a class="headerlink" href="#see-also" title="Permalink to this headline">.</a></h2> +<p><em>qdrouterd(8)</em>, <em>qdmanage(8)</em></p> +<p><a class="reference external" href="http://qpid.apache.org/components/dispatch-router";>http://qpid.apache.org/components/dispatch-router</a></p> +</div> +</div> + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/man/qdrouterd.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/man/qdrouterd.html.in b/input/releases/qpid-dispatch-0.6.1/man/qdrouterd.html.in new file mode 100644 index 0000000..e45fe2c --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/man/qdrouterd.html.in @@ -0,0 +1,43 @@ + + + <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> +<div class="section" id="synopsis"> +<h2>SYNOPSIS<a class="headerlink" href="#synopsis" title="Permalink to this headline">.</a></h2> +<p>qdrouterd [<em>options</em>]</p> +</div> +<div class="section" id="description"> +<h2>DESCRIPTION<a class="headerlink" href="#description" title="Permalink to this headline">.</a></h2> +<p>The Qpid Dispatch router (qdrouterd) is a network daemon that directs +AMQP 1.0 messages between endpoints, such as messaging clients and +servers.</p> +</div> +<div class="section" id="options"> +<h2>OPTIONS<a class="headerlink" href="#options" title="Permalink to this headline">.</a></h2> +<p>-c, –config=PATH (/usr/local/etc/qpid-dispatch/qdrouterd.conf) +: Load configuration from file at PATH</p> +<p>-I, –include=PATH (/usr/local/lib/qpid-dispatch/python) +: Location of Dispatch’s Python library</p> +<p>-d, –daemon +: Run process as a SysV-style daemon</p> +<p>-P, –pidfile +: If daemon, the file for the stored daemon pid</p> +<p>-U, –user +: If daemon, the username to run as</p> +<p>-h, –help +: Print this help</p> +</div> +<div class="section" id="files"> +<h2>FILES<a class="headerlink" href="#files" title="Permalink to this headline">.</a></h2> +<dl class="docutils"> +<dt>/usr/local/etc/qdrouterd.conf</dt> +<dd>Configuration flie.</dd> +</dl> +</div> +<div class="section" id="see-also"> +<h2>SEE ALSO<a class="headerlink" href="#see-also" title="Permalink to this headline">.</a></h2> +<p><em>qdrouterd.conf(5)</em>, <em>qdstat(8)</em>, <em>qdmanage(8)</em></p> +<p><a class="reference external" href="http://qpid.apache.org/components/dispatch-router";>http://qpid.apache.org/components/dispatch-router</a></p> +</div> +</div> + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/man/qdstat.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/man/qdstat.html.in b/input/releases/qpid-dispatch-0.6.1/man/qdstat.html.in new file mode 100644 index 0000000..99cd510 --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/man/qdstat.html.in @@ -0,0 +1,273 @@ + + + <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> +<div class="section" id="synopsis"> +<h2>Synopsis<a class="headerlink" href="#synopsis" title="Permalink to this headline">.</a></h2> +<p>qdstat [options]</p> +</div> +<div class="section" id="description"> +<h2>Description<a class="headerlink" href="#description" title="Permalink to this headline">.</a></h2> +<p><em>qdstat</em> shows status information about networks of Dispatch routers. It +can display connections, network nodes and links, and router stats such +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>-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="output-columns"> +<h2>Output Columns<a class="headerlink" href="#output-columns" title="Permalink to this headline">.</a></h2> +<div class="section" id="qdstat-c"> +<h3>qdstat -c<a class="headerlink" href="#qdstat-c" title="Permalink to this headline">.</a></h3> +<p>Id +: Unique connection identifier</p> +<p>host +: The hostname or internet address of the remotely connected AMQP container</p> +<p>container +: The container-name of the remotely connected AMQP container</p> +<p>role +: The configured role of the connection</p> +<blockquote> +<div><ul class="simple"> +<li>normal - Normal connections from client to router</li> +<li>inter-router - Connection between routers to form a network</li> +<li>route-container - Connection to/from a Broker or other host to receive link-routes and waypoints</li> +</ul> +</div></blockquote> +<p>dir +: The direction of connection establishment</p> +<blockquote> +<div><ul class="simple"> +<li>in - The connection was initiated by the remote container</li> +<li>out - The connection was initiated by this router</li> +</ul> +</div></blockquote> +<p>security +: A description of the security/encryption in effect for this connection</p> +<p>authentication +: The method and user-id of the authenticated user for this connection</p> +</div> +<div class="section" id="qdstat-l"> +<h3>qdstat -l<a class="headerlink" href="#qdstat-l" title="Permalink to this headline">.</a></h3> +<p>type +: Type of link</p> +<blockquote> +<div><ul class="simple"> +<li>router-control - An inter-router link that is reserved for control messages exchanged between routers</li> +<li>inter-router - An inter-router link that is used for normal message-routed deliveries</li> +<li>endpoint - A normal link to an external endpoint container</li> +</ul> +</div></blockquote> +<p>dir +: The direction of message flow on the link</p> +<blockquote> +<div><ul class="simple"> +<li>in - Deliveries flow inbound to the router</li> +<li>out - Deliveries flow outbound from the router</li> +</ul> +</div></blockquote> +<p>conn id +: Unique identifier of the connection over which this link is attached</p> +<p>id +: Unique identifier of this link</p> +<p>peer +: For link-routed links, the unique identifier of the peer link. In link routing, an inbound link is paired with an outbound link</p> +<p>class +: Class of the address bound to the link</p> +<p>addr +: The address bound to the link</p> +<p>phs +: The phase of the address bound to the link</p> +<p>cap +: The capacity, in deliveries, of the link</p> +<p>undel +: The number of undelivered messages stored on the link’s FIFO</p> +<p>unsettled +: The number of unsettled deliveries being tracked by the link</p> +<p>deliveries +: The total number of deliveries that have transited this link</p> +<p>admin +: The administrative status of the link</p> +<blockquote> +<div><ul class="simple"> +<li>enabled - The link is enabled for normal operation</li> +<li>disabled - The link is disabled and should be quiescing or stopped (not yet supported)</li> +</ul> +</div></blockquote> +<p>oper +: The operational status of the link</p> +<blockquote> +<div><ul class="simple"> +<li>up - The link is operational</li> +<li>down - The link is not attached</li> +<li>quiescing - The link is in the process of quiescing (not yet supported)</li> +<li>idle - The link has completed quiescing and is idle (not yet supported)</li> +</ul> +</div></blockquote> +<p>name +: The link name (only shown if the -v option is provided)</p> +</div> +<div class="section" id="qdstat-n"> +<h3>qdstat -n<a class="headerlink" href="#qdstat-n" title="Permalink to this headline">.</a></h3> +<p>router-id +: Identifier of the router</p> +<p>next-hop +: If this router is not a neighbor, identifies the next-hop neighbor used to reach this router</p> +<p>link +: Unique identifier of the link to the neighbor router</p> +<p>cost +: The topology cost to this remote router (with -v option only)</p> +<p>neighbors +: The list of neighbor routers (the router’s link-state) (with -v option only)</p> +<p>valid-origins +: The list of origin routers for which the best path to the listed router passes through this router (with -v option only)</p> +</div> +<div class="section" id="qdstat-a"> +<h3>qdstat -a<a class="headerlink" href="#qdstat-a" title="Permalink to this headline">.</a></h3> +<p>class +: The class of the listed address</p> +<blockquote> +<div><ul class="simple"> +<li>local - Address that is local to this router</li> +<li>topo - Topological address used for router control messages</li> +<li>router - A summary router address used to route messages to a remote router’s local addresses</li> +<li>mobile - A mobile address for an attached consumer or producer</li> +</ul> +</div></blockquote> +<p>addr +: The address text</p> +<p>phs +: For mobile addresses only, the phase of the address. Direct addresses have only a phase 0. Waypoint addresses have multiple phases, normally 0 and 1.</p> +<p>distrib +: Distribution method used for this address</p> +<blockquote> +<div><ul class="simple"> +<li>multicast - A copy of each message is delivered once to each consumer for the address</li> +<li>closest - Each message is delivered to only one consumer for the address. The closest (lowest cost) consumer will be chosen. If there are multiple lowest-cost consumers, deliveries will be spread across those consumers.</li> +<li>balanced - Each message is delivered to only one consumer for the address. The consumer with the fewest outstanding (unsettled) deliveries will be chosen. The cost of the route to the consumer is a threshold for delivery (i.e. higher cost consumers will only receive deliveries if closer consumers are backed up).</li> +<li>flood - Used only for router-control traffic. This is multicast without prevention of duplicate deliveries.</li> +</ul> +</div></blockquote> +<p>in-proc +: The number of in-process consumers for this address</p> +<p>local +: The number of local (on this router) consumers for this address</p> +<p>remote +: The number of remote routers that have at least one consumer for this address</p> +<p>cntnr +: The number of locally attached containers that are destinations for link-routes on this address</p> +<p>in +: The number of deliveries for this address that entered the network on this router</p> +<p>out +: The number of deliveries for this address that exited the network on this router</p> +<p>thru +: The number of deliveries for this address that were forwarded to other routers</p> +<p>to-proc +: The number of deliveries for this address that were delivered to an in-process consumer</p> +<p>from-proc +: The number of deliveries for this address that were received from an in-process producer</p> +</div> +<div class="section" id="qdstat-linkroutes"> +<h3>qdstat –linkroutes<a class="headerlink" href="#qdstat-linkroutes" title="Permalink to this headline">.</a></h3> +<p>prefix +: The prefix for matching addresses of routed links</p> +<p>dir +: The direction (from the router’s perspective) of matching links</p> +<p>distrib +: The distribution method used for routed links</p> +<blockquote> +<div><ul class="simple"> +<li>linkBalanced - the only supported distribution for routed links</li> +</ul> +</div></blockquote> +<p>status +: Operational status of the link route</p> +<blockquote> +<div><ul class="simple"> +<li>active - Route is actively routing attaches (i.e. ready for use)</li> +<li>inactive - Route is inactive because there is no local destination connected</li> +</ul> +</div></blockquote> +</div> +<div class="section" id="qstat-autolinks"> +<h3>qstat –autolinks<a class="headerlink" href="#qstat-autolinks" title="Permalink to this headline">.</a></h3> +<p>addr +: The address of the auto link</p> +<p>dir +: The direction of message flow for the auto link</p> +<blockquote> +<div><ul class="simple"> +<li>in - Messages flow in from the route-container to the router network</li> +<li>out - Messages flow out to the route-container from the router network</li> +</ul> +</div></blockquote> +<p>phs +: Phase of the address for this auto link</p> +<p>link +: Unique identifier of the link managed by this auto link</p> +<p>status +: The operational status of this auto link</p> +<blockquote> +<div><ul class="simple"> +<li>inactive - There is no connected container for this auto link</li> +<li>attaching - The link is attaching to the container</li> +<li>failed - The link-attach failed</li> +<li>active - The link is operational</li> +<li>quiescing - The link is quiescing (not yet supported)</li> +<li>idle - The link is idle (not yet supported)</li> +</ul> +</div></blockquote> +<p>lastErr +: The description of the last attach failure that occurred on this auto link</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> +<p><em>qdrouterd(8)</em>, <em>qdmanage(8)</em>, <em>qdrouterd.conf(5)</em></p> +<p><a class="reference external" href="http://qpid.apache.org/components/dispatch-router";>http://qpid.apache.org/components/dispatch-router</a></p> +</div> +</div> + http://git-wip-us.apache.org/repos/asf/qpid-site/blob/48fa0554/input/releases/qpid-dispatch-0.6.1/release-notes.md ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.1/release-notes.md b/input/releases/qpid-dispatch-0.6.1/release-notes.md new file mode 100644 index 0000000..a3be13a --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.1/release-notes.md @@ -0,0 +1,46 @@ +;; +;; Licensed to the Apache Software Foundation (ASF) under one +;; or more contributor license agreements. See the NOTICE file +;; distributed with this work for additional information +;; regarding copyright ownership. The ASF licenses this file +;; to you under the Apache License, Version 2.0 (the +;; "License"); you may not use this file except in compliance +;; with the License. You may obtain a copy of the License at +;; +;; http://www.apache.org/licenses/LICENSE-2.0 +;; +;; Unless required by applicable law or agreed to in writing, +;; software distributed under the License is distributed on an +;; "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +;; KIND, either express or implied. See the License for the +;; specific language governing permissions and limitations +;; under the License. +;; + +# Qpid Dispatch 0.6.1 Release Notes + +Dispatch is a lightweight AMQP message router library. More about +[Qpid +Dispatch]({{site_url}}/components/dispatch-router/index.html). + +For more information about this release, including download links and +documentation, see the [release overview](index.html). + + +## New features and improvements + + - [DISPATCH-367](https://issues.apache.org/jira/browse/DISPATCH-367) - balanced distribution needs to be more... balanced. + +## Bugs fixed + + - [DISPATCH-341](https://issues.apache.org/jira/browse/DISPATCH-341) - router did not respond to request to drain a message-routed consumers link credit + - [DISPATCH-364](https://issues.apache.org/jira/browse/DISPATCH-364) - Inter-router listeners should not permit normal endpoint traffic + - [DISPATCH-365](https://issues.apache.org/jira/browse/DISPATCH-365) - Standalone router crashes if an interior router attempts to connect to it + - [DISPATCH-366](https://issues.apache.org/jira/browse/DISPATCH-366) - When delivery fails the router sends the RELEASED disposition, not MODIFIED + - [DISPATCH-387](https://issues.apache.org/jira/browse/DISPATCH-387) - Router core dumps with misbehaving client + - [DISPATCH-443](https://issues.apache.org/jira/browse/DISPATCH-443) - Reverse name lookup on listener connections can hang the entire router + - [DISPATCH-460](https://issues.apache.org/jira/browse/DISPATCH-460) - Regression: Link-routed dynamic sources don't work + +## Tasks + + - [DISPATCH-410](https://issues.apache.org/jira/browse/DISPATCH-410) - console build fixups \ No newline at end of file --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
