Repository: qpid-site Updated Branches: refs/heads/asf-site 80d07ca33 -> ac1c16638
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/ac1c1663/input/releases/qpid-dispatch-0.6.0/man/qdrouterd.conf.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.0/man/qdrouterd.conf.html.in b/input/releases/qpid-dispatch-0.6.0/man/qdrouterd.conf.html.in new file mode 100644 index 0000000..6e8b211 --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.0/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/ac1c1663/input/releases/qpid-dispatch-0.6.0/man/qdrouterd.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.0/man/qdrouterd.html.in b/input/releases/qpid-dispatch-0.6.0/man/qdrouterd.html.in new file mode 100644 index 0000000..e45fe2c --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.0/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/ac1c1663/input/releases/qpid-dispatch-0.6.0/man/qdstat.html.in ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.0/man/qdstat.html.in b/input/releases/qpid-dispatch-0.6.0/man/qdstat.html.in new file mode 100644 index 0000000..99cd510 --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.0/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/ac1c1663/input/releases/qpid-dispatch-0.6.0/release-notes.md ---------------------------------------------------------------------- diff --git a/input/releases/qpid-dispatch-0.6.0/release-notes.md b/input/releases/qpid-dispatch-0.6.0/release-notes.md new file mode 100644 index 0000000..31388fe --- /dev/null +++ b/input/releases/qpid-dispatch-0.6.0/release-notes.md @@ -0,0 +1,160 @@ +;; +;; 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.0 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-10](https://issues.apache.org/jira/browse/DISPATCH-10) - Add link-cost for route computation + - [DISPATCH-57](https://issues.apache.org/jira/browse/DISPATCH-57) - Balance deliveries adaptively across all competing consumers in the network + - [DISPATCH-144](https://issues.apache.org/jira/browse/DISPATCH-144) - Configurable heartbeats for listeners and connectors + - [DISPATCH-148](https://issues.apache.org/jira/browse/DISPATCH-148) - Strip qpid-dispatch-specific message annotations on ingress/egress + - [DISPATCH-159](https://issues.apache.org/jira/browse/DISPATCH-159) - Enhance the address prefix used for link routing to support different patterns + - [DISPATCH-163](https://issues.apache.org/jira/browse/DISPATCH-163) - Add username and password for authentication of connectors + - [DISPATCH-164](https://issues.apache.org/jira/browse/DISPATCH-164) - Remove connector state-machine from the server module + - [DISPATCH-165](https://issues.apache.org/jira/browse/DISPATCH-165) - Discriminate between sending and receiving links when matching link-route patterns + - [DISPATCH-166](https://issues.apache.org/jira/browse/DISPATCH-166) - Use test-controlled SASL configuration for system tests + - [DISPATCH-170](https://issues.apache.org/jira/browse/DISPATCH-170) - qdrouterd should not require a restart after the destination broker restarts + - [DISPATCH-178](https://issues.apache.org/jira/browse/DISPATCH-178) - Route proton trace messages to the dispatch router log file instead of console + - [DISPATCH-179](https://issues.apache.org/jira/browse/DISPATCH-179) - Refactor Router Core + - [DISPATCH-180](https://issues.apache.org/jira/browse/DISPATCH-180) - Add a system test to test the 'linkRoutePattern' attribute of qdrouterd.conf + - [DISPATCH-188](https://issues.apache.org/jira/browse/DISPATCH-188) - Dispatch needs a policy mechanism to limit user connections and activity + - [DISPATCH-190](https://issues.apache.org/jira/browse/DISPATCH-190) - Expose the Protocol Family for the configuration of listeners and connectors + - [DISPATCH-193](https://issues.apache.org/jira/browse/DISPATCH-193) - Updates to the Container API + - [DISPATCH-194](https://issues.apache.org/jira/browse/DISPATCH-194) - Move libqpid-dispatch.so out of /lib + - [DISPATCH-197](https://issues.apache.org/jira/browse/DISPATCH-197) - Provide list of current link routing + - [DISPATCH-199](https://issues.apache.org/jira/browse/DISPATCH-199) - Add Dockerfiles that launches the dispatch router inside a container for RHEL and Debian based systems + - [DISPATCH-200](https://issues.apache.org/jira/browse/DISPATCH-200) - Flexible mapping from x.509 certificates to an identity + - [DISPATCH-203](https://issues.apache.org/jira/browse/DISPATCH-203) - Improve loop-prevention to drop messages before they are improperly forwarded + - [DISPATCH-217](https://issues.apache.org/jira/browse/DISPATCH-217) - Make the UI more consistant with other hawtio plugins + - [DISPATCH-228](https://issues.apache.org/jira/browse/DISPATCH-228) - In ctools, add a variant of DEQ_* to allow membership in multiple lists + - [DISPATCH-230](https://issues.apache.org/jira/browse/DISPATCH-230) - New connection role: route-container + - [DISPATCH-232](https://issues.apache.org/jira/browse/DISPATCH-232) - Add capability to delete listeners and connectors via the qdmanage DELETE operation + - [DISPATCH-242](https://issues.apache.org/jira/browse/DISPATCH-242) - Add options to qdstat to display autoLinks and linkRoutes + - [DISPATCH-253](https://issues.apache.org/jira/browse/DISPATCH-253) - Configurable link-capacity + - [DISPATCH-256](https://issues.apache.org/jira/browse/DISPATCH-256) - Documentation Updates for 0.6 + - [DISPATCH-265](https://issues.apache.org/jira/browse/DISPATCH-265) - Improvements to Detecting Routers with Duplicate IDs + - [DISPATCH-277](https://issues.apache.org/jira/browse/DISPATCH-277) - Improve defaults for router configuration + - [DISPATCH-286](https://issues.apache.org/jira/browse/DISPATCH-286) - Prefix delimiters: allow slashes as well as periods + - [DISPATCH-300](https://issues.apache.org/jira/browse/DISPATCH-300) - Deprecate the ContainerEntity and move its attributes to RouterEntity + - [DISPATCH-303](https://issues.apache.org/jira/browse/DISPATCH-303) - Block all remote access to the "console" entity + - [DISPATCH-305](https://issues.apache.org/jira/browse/DISPATCH-305) - Don't tie inter-router flow credit to unsettled deliveries + - [DISPATCH-306](https://issues.apache.org/jira/browse/DISPATCH-306) - Deprecate addr and routerId attributes in qdrouter schema and replace them with host and id respectively + - [DISPATCH-331](https://issues.apache.org/jira/browse/DISPATCH-331) - Allow for a default policy to apply when open.hostname doesn't match an existing policy + +## Bugs fixed + + - [DISPATCH-32](https://issues.apache.org/jira/browse/DISPATCH-32) - Undeliverable messages should get released. + - [DISPATCH-43](https://issues.apache.org/jira/browse/DISPATCH-43) - Router control messages delayed by inter-router message traffic + - [DISPATCH-47](https://issues.apache.org/jira/browse/DISPATCH-47) - qdrouterd doesn't know where its libraries are + - [DISPATCH-53](https://issues.apache.org/jira/browse/DISPATCH-53) - waypoints are not robust if targets not set up in advance. + - [DISPATCH-58](https://issues.apache.org/jira/browse/DISPATCH-58) - Router/Broker interaction - Unroutable/released messages are continually resent + - [DISPATCH-111](https://issues.apache.org/jira/browse/DISPATCH-111) - helloworld example hangs when run against a broker via link-routing + - [DISPATCH-126](https://issues.apache.org/jira/browse/DISPATCH-126) - Link-route behavior doesn't honor the semantics assigned to the address prefix + - [DISPATCH-127](https://issues.apache.org/jira/browse/DISPATCH-127) - Messages from waypoints to remote routers are not delivered + - [DISPATCH-155](https://issues.apache.org/jira/browse/DISPATCH-155) - Allow multiple connectors to the same broker + - [DISPATCH-168](https://issues.apache.org/jira/browse/DISPATCH-168) - A message sent to $management without a reply-to field causes a crash + - [DISPATCH-171](https://issues.apache.org/jira/browse/DISPATCH-171) - SSL Domain objects are leaked. + - [DISPATCH-172](https://issues.apache.org/jira/browse/DISPATCH-172) - QDStat system test never tests SASL EXTERNAL + - [DISPATCH-173](https://issues.apache.org/jira/browse/DISPATCH-173) - Half-closed connections spin on "writable" until they close + - [DISPATCH-174](https://issues.apache.org/jira/browse/DISPATCH-174) - Improper use of ref-counted object references in container + - [DISPATCH-175](https://issues.apache.org/jira/browse/DISPATCH-175) - Router continues to forward messages to the broker even when the broker is not available + - [DISPATCH-176](https://issues.apache.org/jira/browse/DISPATCH-176) - Messages sent got lost when one of the brokers went down + - [DISPATCH-183](https://issues.apache.org/jira/browse/DISPATCH-183) - plaintext sasl password being written to the dispatch router log + - [DISPATCH-191](https://issues.apache.org/jira/browse/DISPATCH-191) - router not replying to detach frame + - [DISPATCH-196](https://issues.apache.org/jira/browse/DISPATCH-196) - Remove endpoint mode from router documentation + - [DISPATCH-198](https://issues.apache.org/jira/browse/DISPATCH-198) - Message module doesn't parse AMQP-Value bodies that are strings or symbols + - [DISPATCH-207](https://issues.apache.org/jira/browse/DISPATCH-207) - When a message body of [ ] is sent from rhea it is rejected as an invalid body + - [DISPATCH-208](https://issues.apache.org/jira/browse/DISPATCH-208) - Closest semantics forwards improperly in multi-router network + - [DISPATCH-215](https://issues.apache.org/jira/browse/DISPATCH-215) - The topology diagram initially draws off the bottom of the visible page. + - [DISPATCH-218](https://issues.apache.org/jira/browse/DISPATCH-218) - Dispatch system tests run very slowly if connected to a VPN + - [DISPATCH-219](https://issues.apache.org/jira/browse/DISPATCH-219) - System test security configuration for installed/built tests. + - [DISPATCH-222](https://issues.apache.org/jira/browse/DISPATCH-222) - For Dispatch 0.6 release move up the minimum required version of qpid proton to 0.12.0 + - [DISPATCH-223](https://issues.apache.org/jira/browse/DISPATCH-223) - Unknown connector name is not properly printed in error messages + - [DISPATCH-225](https://issues.apache.org/jira/browse/DISPATCH-225) - Sending UPDATE log request with relative path crashes router + - [DISPATCH-226](https://issues.apache.org/jira/browse/DISPATCH-226) - The default role is not applied when creating a connector + - [DISPATCH-231](https://issues.apache.org/jira/browse/DISPATCH-231) - Router should not issue credit for unavailable targets + - [DISPATCH-234](https://issues.apache.org/jira/browse/DISPATCH-234) - undeliverable-here set to true for messages from waypoints if there is no receiver + - [DISPATCH-237](https://issues.apache.org/jira/browse/DISPATCH-237) - Dispatch Router overwrites delivery tag for link-routed deliveries + - [DISPATCH-238](https://issues.apache.org/jira/browse/DISPATCH-238) - Need more documentation for qdstat output + - [DISPATCH-240](https://issues.apache.org/jira/browse/DISPATCH-240) - qdstat : leading "/" character effects a wrong showed address + - [DISPATCH-241](https://issues.apache.org/jira/browse/DISPATCH-241) - Bias "spread" config with leading "/" on address has a "multicast" behavior + - [DISPATCH-245](https://issues.apache.org/jira/browse/DISPATCH-245) - Various Bugs found by Coverity + - [DISPATCH-247](https://issues.apache.org/jira/browse/DISPATCH-247) - Policy gets username from transport + - [DISPATCH-248](https://issues.apache.org/jira/browse/DISPATCH-248) - Policy self test uses python features not supported by RHEL 6 (python 2.6) + - [DISPATCH-250](https://issues.apache.org/jira/browse/DISPATCH-250) - Router crash when deleting connector + - [DISPATCH-254](https://issues.apache.org/jira/browse/DISPATCH-254) - Router crash after several management requests + - [DISPATCH-259](https://issues.apache.org/jira/browse/DISPATCH-259) - qdstat man-page doc is no good + - [DISPATCH-261](https://issues.apache.org/jira/browse/DISPATCH-261) - Bind error on one port causes bind error on other ports + - [DISPATCH-262](https://issues.apache.org/jira/browse/DISPATCH-262) - oslo.messaging RPC fanout crashes qdrouterd + - [DISPATCH-263](https://issues.apache.org/jira/browse/DISPATCH-263) - Router crash when requesting log + - [DISPATCH-264](https://issues.apache.org/jira/browse/DISPATCH-264) - printf formats for 64-bit quantities need to be 64/32-bit safe + - [DISPATCH-267](https://issues.apache.org/jira/browse/DISPATCH-267) - Policy does not increment denial statistics + - [DISPATCH-268](https://issues.apache.org/jira/browse/DISPATCH-268) - Delivery from waypoint queue can stall when messages are released + - [DISPATCH-269](https://issues.apache.org/jira/browse/DISPATCH-269) - Policy denial logs at wrong level + - [DISPATCH-271](https://issues.apache.org/jira/browse/DISPATCH-271) - Handle single router + - [DISPATCH-272](https://issues.apache.org/jira/browse/DISPATCH-272) - Re-enable the connection cross-section popup + - [DISPATCH-273](https://issues.apache.org/jira/browse/DISPATCH-273) - The entity view is missing information for some entities + - [DISPATCH-275](https://issues.apache.org/jira/browse/DISPATCH-275) - Prevent javascript alert errors when navigating to console from a bookmark + - [DISPATCH-278](https://issues.apache.org/jira/browse/DISPATCH-278) - Deleting amqp listener using qdmanage crashes the router + - [DISPATCH-279](https://issues.apache.org/jira/browse/DISPATCH-279) - Policy crash when application name is null + - [DISPATCH-281](https://issues.apache.org/jira/browse/DISPATCH-281) - Hostname not sent in open frame on connectors + - [DISPATCH-282](https://issues.apache.org/jira/browse/DISPATCH-282) - Prevent topology updates when adding a new router node + - [DISPATCH-283](https://issues.apache.org/jira/browse/DISPATCH-283) - Start the overview page with the Router tree node expanded + - [DISPATCH-284](https://issues.apache.org/jira/browse/DISPATCH-284) - The management schema no longer exposes a way to associate links with their connections + - [DISPATCH-285](https://issues.apache.org/jira/browse/DISPATCH-285) - qdmanage returns an empty list when you QUERY for certain entities + - [DISPATCH-287](https://issues.apache.org/jira/browse/DISPATCH-287) - Policy does not allow configuration for unspecified Open hostname + - [DISPATCH-288](https://issues.apache.org/jira/browse/DISPATCH-288) - Driver - Wakeup pipe was seen to block on read, deadlocking the driver. + - [DISPATCH-289](https://issues.apache.org/jira/browse/DISPATCH-289) - Unit tests failing on Solaris + - [DISPATCH-290](https://issues.apache.org/jira/browse/DISPATCH-290) - Adapt CMakeLists.txt and code so that qpid-dispatch can be compiled on Solaris + - [DISPATCH-292](https://issues.apache.org/jira/browse/DISPATCH-292) - some router.link attributes should be graphable + - [DISPATCH-293](https://issues.apache.org/jira/browse/DISPATCH-293) - The $ character can't be used inside a prefix for linkRoute + - [DISPATCH-294](https://issues.apache.org/jira/browse/DISPATCH-294) - Crash in the core-thread due to an address referencing a link on a closed connection + - [DISPATCH-295](https://issues.apache.org/jira/browse/DISPATCH-295) - Router aborted on assertion failed after socker closing by client + - [DISPATCH-298](https://issues.apache.org/jira/browse/DISPATCH-298) - router spinning on shutdown (in qdr_del_connection_ref) + - [DISPATCH-299](https://issues.apache.org/jira/browse/DISPATCH-299) - After policy rejects a connection queued Begin causes a crash + - [DISPATCH-304](https://issues.apache.org/jira/browse/DISPATCH-304) - Console PNG images not showing up in documentation + - [DISPATCH-309](https://issues.apache.org/jira/browse/DISPATCH-309) - Mobile addresses get the wrong distribution when mapped to remote routers + - [DISPATCH-310](https://issues.apache.org/jira/browse/DISPATCH-310) - Use router.id instead of container.containerName + - [DISPATCH-312](https://issues.apache.org/jira/browse/DISPATCH-312) - Closest distribution fails to react to loss of a remote destination + - [DISPATCH-319](https://issues.apache.org/jira/browse/DISPATCH-319) - Discrepancy between origin router's path and other routers' valid-origins + - [DISPATCH-320](https://issues.apache.org/jira/browse/DISPATCH-320) - SSL enabled connector does not do hostname verification + - [DISPATCH-321](https://issues.apache.org/jira/browse/DISPATCH-321) - Dispatch does not send out SASL-OUTCOME frame on sasl failure + - [DISPATCH-334](https://issues.apache.org/jira/browse/DISPATCH-334) - Proton sequence error during backpressure with balanced distribution + - [DISPATCH-335](https://issues.apache.org/jira/browse/DISPATCH-335) - link routes aren't balanced over remote routers + - [DISPATCH-338](https://issues.apache.org/jira/browse/DISPATCH-338) - Incorrect default distribution for addresses + - [DISPATCH-339](https://issues.apache.org/jira/browse/DISPATCH-339) - The change from 'routerId' to 'id' and 'addr' to 'host' configuration option is not backwards compatible + - [DISPATCH-340](https://issues.apache.org/jira/browse/DISPATCH-340) - Test inter_router_plain_over_ssl fails to find SSL connection + - [DISPATCH-342](https://issues.apache.org/jira/browse/DISPATCH-342) - qdrouterd.conf doc calls out router.config.{address,linkRoute,autoLink} + - [DISPATCH-343](https://issues.apache.org/jira/browse/DISPATCH-343) - Router stops accepting connections after load from parallel senders + - [DISPATCH-356](https://issues.apache.org/jira/browse/DISPATCH-356) - Creating and deleting a listener on already listening port causes router to crash + - [DISPATCH-368](https://issues.apache.org/jira/browse/DISPATCH-368) - Router in bad state in two inter-connected routers + +## Tasks + + - [DISPATCH-307](https://issues.apache.org/jira/browse/DISPATCH-307) - misc fixups for console plugin build + - [DISPATCH-308](https://issues.apache.org/jira/browse/DISPATCH-308) - console documentation needs updated \ No newline at end of file --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
