You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@qpid.apache.org by kw...@apache.org on 2013/10/09 00:32:50 UTC
svn commit: r1530450 [1/4] -
/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/
Author: kwall
Date: Tue Oct 8 22:32:49 2013
New Revision: 1530450
URL: http://svn.apache.org/r1530450
Log:
NO-JIRA: publish the latest trunk java docbook based documentation
Modified:
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Close-Connection-When-No-Route.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts-Exchanges.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts-Virtual-Hosts.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Configuring-And-Managing-HTTP-Management.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Configuring-And-Managing.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Backup.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-ClientFailover.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Configuration.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-DisasterRecovery.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-DurabilityGuarantee.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-JMXAPI.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-MigrationFromNonHA.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Monitoring-cluster.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-OfferingsOfJavaBroker.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Performance.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-TwoNodeCluster.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Queues.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Runtime-Disk-Space-Management.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Security.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Stores-BDB-Store-Configuration.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Stores-Derby-Store-Configuration.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Stores-JDBC-Store-Configuration.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Stores-Memory-Store-Configuration.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Virtual-Host-Binding-Queue.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Virtual-Host-Configuration-Exchange.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Virtual-Host-Configuration-File-Example.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Virtual-Host-Configure-Disk-Quotas.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Virtual-Host-Configure-Flow-Control.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Virtual-Host-Configuring-DLQ.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Virtual-Host-Declare-Queues.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Virtual-Host-Transaction-Timeout-Configuring.html
qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/index.html
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Close-Connection-When-No-Route.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Close-Connection-When-No-Route.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Close-Connection-When-No-Route.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Close-Connection-When-No-Route.html Tue Oct 8 22:32:49 2013
@@ -23,7 +23,7 @@
</p><p>
Setting the <span class="emphasis"><em>closeWhenNoRoute</em></span> in the JMS client connection URL can override the broker configuration
on a connection specific basis, for example :
- </p><div class="example"><a name="idp7179440"></a><p class="title"><b>Example 12.1. Disable feature to close connection on unroutable messages with client URL</b></p><div class="example-contents"><pre class="screen">
+ </p><div class="example"><a name="idp7424064"></a><p class="title"><b>Example 12.1. Disable feature to close connection on unroutable messages with client URL</b></p><div class="example-contents"><pre class="screen">
amqp://guest:guest@clientid/?brokerlist='tcp://localhost:5672'&closeWhenNoRoute='false'</pre></div></div><br class="example-break"><p>
If no value is specified on the client the broker setting will be used. If client setting is specified then it will take precedence
over the broker-wide configuration. If the client specifies and broker does not support this feature the warning will be logged.
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts-Exchanges.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts-Exchanges.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts-Exchanges.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts-Exchanges.html Tue Oct 8 22:32:49 2013
@@ -1,42 +1,56 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>4.3. Exchanges</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="AMQP Messaging Broker (Java)"><link rel="up" href="Java-Broker-Concepts.html" title="Chapter 4. Concepts"><link rel="prev" href="Java-Broker-Concepts-Virtual-Hosts.html" title="4.2. Virtual Hosts"><link rel="next" href="Java-Broker-Concepts-Queues.html" title="4.4. Queues"></head><body><div class="container" bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><DIV class="header"><DIV class="logo"><H1>Apache Qpidâ¢</H1><H2>Open Source AMQP Messaging</H2></DIV></DIV><DIV class="menu_box"><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Apache Qpid</H3><UL><LI><A href="http://qpid.apache.org/index.html">Home</A></LI><LI><A href="http://qpid.apache.org/download
.html">Download</A></LI><LI><A href="http://qpid.apache.org/getting_started.html">Getting Started</A></LI><LI><A href="http://www.apache.org/licenses/">License</A></LI><LI><A href="https://cwiki.apache.org/qpid/faq.html">FAQ</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Documentation</H3><UL><LI><A href="http://qpid.apache.org/documentation.html#doc-release">Latest Release</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-trunk">Trunk</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-archives">Archive</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Community</H3><UL><LI><A href="http://qpid.apache.org/getting_involved.html">Getting Involved</A></LI><LI><A href="http://qpid.apache.org/source_repository.html">Source Repository</A></LI><LI><A href="http://qpid.apache.org/mailing_lists.html">Mailing Lists</A></LI><L
I><A href="https://cwiki.apache.org/qpid/">Wiki</A></LI><LI><A href="https://issues.apache.org/jira/browse/qpid">Issue Reporting</A></LI><LI><A href="http://qpid.apache.org/people.html">People</A></LI><LI><A href="http://qpid.apache.org/acknowledgements.html">Acknowledgements</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Developers</H3><UL><LI><A href="https://cwiki.apache.org/qpid/building.html">Building Qpid</A></LI><LI><A href="https://cwiki.apache.org/qpid/developer-pages.html">Developer Pages</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About AMQP</H3><UL><LI><A href="http://qpid.apache.org/amqp.html">What is AMQP?</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About Apache</H3><UL><LI><A href="http://www.apache.org">Home</A></LI><LI><A href="http://www.apache.org/foun
dation/sponsorship.html">Sponsorship</A></LI><LI><A href="http://www.apache.org/foundation/thanks.html">Thanks</A></LI><LI><A href="http://www.apache.org/security/">Security</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV></DIV><div class="main_text_area"><div class="main_text_area_top"></div><div class="main_text_area_body"><DIV class="breadcrumbs"><span class="breadcrumb-link"><a href="index.html">AMQP Messaging Broker (Java)</a></span> > <span class="breadcrumb-link"><a href="Java-Broker-Concepts.html">Concepts</a></span> > <span class="breadcrumb-node">Exchanges</span></DIV><div class="section"><div class="titlepage"><div><div><h2 class="title"><a name="Java-Broker-Concepts-Exchanges"></a>4.3. Exchanges</h2></div></div></div><p>An <span class="emphasis"><em>Exchange</em></span> is a named entity within the <span class="emphasis"><em>Virtual Host</em></span> which receives
messages from producers and routes them to matching <span class="emphasis"><em>Queue</em></span>s within the <span class="emphasis"><em>Virtual Host</em></span>.</p><p>The server provides a set of exchange types with each exchange type implementing a different routing algorithm. For details of how
- these exchanges types work see <a class="xref" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-Types" title="4.3.2. Exchange Types">Section 4.3.2, âExchange Typesâ</a> below.</p><p>The server predeclares a number of exchange instances with names starting with <code class="literal">amq.</code>. These are defined in
+ these exchanges types work see <a class="xref" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-Types" title="4.3.2. Exchange Types">Section 4.3.2, âExchange Typesâ</a> below.</p><p>The server predeclares a number of exchange instances with names starting with "<code class="literal">amq.</code>". These are defined in
<a class="xref" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-Predeclared" title="4.3.1. Predeclared Exchanges">Section 4.3.1, âPredeclared Exchangesâ</a>.</p><p>Applications can make use the pre-declared exchanges, or they may declare their own. The number of exchanges within a virtual host is
- limited only by resource constraints.</p><p>The behaviour when an exchange is unable to route a message to any queue is defined in <a class="xref" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-UnroutableMessage" title="4.3.3. Unrouteable Messages">Section 4.3.3, âUnrouteable Messagesâ</a></p><p>Exchange configuration is covered in <a class="xref" href="Java-Broker-Exchanges.html" title="Chapter 8. Exchanges">Chapter 8, <i>Exchanges</i></a>.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="Java-Broker-Concepts-Exchanges-Predeclared"></a>4.3.1. Predeclared Exchanges</h3></div></div></div><p>Each virtual host pre-declares the following exchanges:
+ limited only by resource constraints.</p><p>The behaviour when an exchange is unable to route a message to any queue is defined in <a class="xref" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-UnroutableMessage" title="4.3.4. Unrouteable Messages">Section 4.3.4, âUnrouteable Messagesâ</a></p><p>Exchange configuration is covered in <a class="xref" href="Java-Broker-Exchanges.html" title="Chapter 8. Exchanges">Chapter 8, <i>Exchanges</i></a>.</p><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="Java-Broker-Concepts-Exchanges-Predeclared"></a>4.3.1. Predeclared Exchanges</h3></div></div></div><p>Each virtual host pre-declares the following exchanges:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">amq.direct (an instance of a direct exchange)</li><li class="listitem">amq.topic (an instance of a topic exchange)</li><li class="listitem">amq.fanout (an instance of a fanout exchange)</li><li class="listitem">amq.match (an instance of a headers exchange)</li></ul></div><p>
- </p><p>An exchange known as the default exchange is also pre-declared. This is a direct exchange but is special in that all
- queues are automatically bound to it once using their name as a binding key. It is not possible to manually add or remove
- bindings within this exchange.</p><p>Applications may not declare exchanges with names beginning with <code class="literal">amq.</code>. Such names are reserved for system use.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="Java-Broker-Concepts-Exchanges-Types"></a>4.3.2. Exchange Types</h3></div></div></div><p>
+ </p><p>The conceptual "<code class="literal">default exchange</code>" always exists, effectively a special instance of
+ direct exchange which uses the empty string as its name. All queues are automatically bound to it upon their creation
+ using the queue name as the binding key, and unbound upon their deletion. It is not possible to manually add or remove
+ bindings within this exchange.</p><p>Applications may not declare exchanges with names beginning with "<code class="literal">amq.</code>". Such names are reserved for system use.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="Java-Broker-Concepts-Exchanges-Types"></a>4.3.2. Exchange Types</h3></div></div></div><p>
The following Exchange types are supported.
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">Direct</li><li class="listitem">Topic</li><li class="listitem">Fanout</li><li class="listitem">Headers</li></ul></div><p>
These exchange types are described in the following sub-sections.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-Concepts-Exchanges-Types-Direct"></a>4.3.2.1. Direct</h4></div></div></div><p>The direct exchange type routes messages to queues based on an exact match between
- the routing key of the message, and the binding key used to bind the queue to the exchange.
+ the routing key of the message, and the binding key used to bind the queue to the exchange. Additional
+ filter rules may be specified using a <a class="link" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-BindingArguments-JMSSelector" title="4.3.3.1. JMS Selector">
+ binding argument specifying a JMS message selector</a>.
</p><p>This exchange type is often used to implement point to point messaging. When used in this manner, the normal
convention is that the binding key matches the name of the queue. It is also possible to use this exchange type
- for multi-cast, in this case the same binding key is associated with many queues.</p><div class="figure"><a name="idp7027664"></a><p class="title"><b>Figure 4.3. Direct exchange</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/Exchange-Direct.png" alt="Direct exchange"></div></div></div><br class="figure-break"><p>The figure above illustrates the operation of direct exchange type. The yellow messages published with the routing key
- <code class="literal">myqueue</code> match the binding key corresponding to queue <code class="literal">myqueue</code> to are routes there. The red
- messages published with the routing key <code class="literal">foo</code> match two bindings in the table so a copy of the message is
- routed to both <code class="literal">bar1</code> and <code class="literal">bar2</code>.</p><p>The routing key of the blue message matches no binding keys, so the message is unroutable. It is handled as described
- in <a class="xref" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-UnroutableMessage" title="4.3.3. Unrouteable Messages">Section 4.3.3, âUnrouteable Messagesâ</a>.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-Concepts-Exchanges-Types-Topic"></a>4.3.2.2. Topic</h4></div></div></div><p>This exchange type is used to support the classic publish/subscribe paradigm.</p><p>The topic exchange is capable of routing messages to queues based on wildcard matches between the routing key and the
+ for multi-cast, in this case the same binding key is associated with many queues.</p><div class="figure"><a name="idp7041712"></a><p class="title"><b>Figure 4.3. Direct exchange</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/Exchange-Direct.png" alt="Direct exchange"></div></div></div><br class="figure-break"><p>The figure above illustrates the operation of direct exchange type. The yellow messages published with the routing key
+ "<code class="literal">myqueue</code>" match the binding key corresponding to queue "<code class="literal">myqueue</code>" and so are routed there. The red
+ messages published with the routing key "<code class="literal">foo</code>" match two bindings in the table so a copy of the message is
+ routed to both the "<code class="literal">bar1</code>" and "<code class="literal">bar2</code>" queues.</p><p>The routing key of the blue message matches no binding keys, so the message is unroutable. It is handled as described
+ in <a class="xref" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-UnroutableMessage" title="4.3.4. Unrouteable Messages">Section 4.3.4, âUnrouteable Messagesâ</a>.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-Concepts-Exchanges-Types-Topic"></a>4.3.2.2. Topic</h4></div></div></div><p>This exchange type is used to support the classic publish/subscribe paradigm.</p><p>The topic exchange is capable of routing messages to queues based on wildcard matches between the routing key and the
binding key pattern defined by the queue binding. Routing keys are formed from one or more words, with each word delimited
by a full-stop (.). The pattern matching characters are the * and # symbols. The * symbol matches a single word and the #
- symbol matches zero or more words.</p><p>The topic exchange is also capable of routing messages according to whether a message's header values or properties match
- a JMS message selector <a href="#ftn.idp7036560" class="footnote" name="idp7036560"><sup class="footnote">[4]</sup></a>.</p><p>The following three figures help explain how the topic exchange functions.</p><p></p><div class="figure"><a name="idp7037968"></a><p class="title"><b>Figure 4.4. Topic exchange - exact match on topic name</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/Exchange-Topic.png" alt="Topic exchange - exact match on topic name"></div></div></div><br class="figure-break"><p>The figure above illustrates publishing messages with routing key <code class="literal">weather</code>. The exchange routes each
- message to every bound queue whose binding key matches the routing key.</p><p>In the case illustrated, this means that each subscriber's queue receives every yellow message.</p><div class="figure"><a name="idp7041920"></a><p class="title"><b>Figure 4.5. Topic exchange - matching on hierarchical topic patterns</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/Exchange-Topic-Hierarchical.png" alt="Topic exchange - matching on hierarchical topic patterns"></div></div></div><br class="figure-break"><p>The figure above illustrates publishing messages with hierarchical routing keys. As before, the exchange routes each
+ symbol matches zero or more words.</p><p>Additional filter rules may be specified using a <a class="link" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-BindingArguments-JMSSelector" title="4.3.3.1. JMS Selector">
+ binding argument specifying a JMS message selector</a>.</p><p>The following three figures help explain how the topic exchange functions.</p><p></p><div class="figure"><a name="idp7052128"></a><p class="title"><b>Figure 4.4. Topic exchange - exact match on topic name</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/Exchange-Topic.png" alt="Topic exchange - exact match on topic name"></div></div></div><br class="figure-break"><p>The figure above illustrates publishing messages with routing key "<code class="literal">weather</code>". The exchange routes each
+ message to every bound queue whose binding key matches the routing key.</p><p>In the case illustrated, this means that each subscriber's queue receives every yellow message.</p><div class="figure"><a name="idp7056080"></a><p class="title"><b>Figure 4.5. Topic exchange - matching on hierarchical topic patterns</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/Exchange-Topic-Hierarchical.png" alt="Topic exchange - matching on hierarchical topic patterns"></div></div></div><br class="figure-break"><p>The figure above illustrates publishing messages with hierarchical routing keys. As before, the exchange routes each
message to every bound queue whose binding key matches the routing key but as the binding keys contain wildcards, the
- wildcard rules described above apply.</p><p>In the case illustrated, <code class="literal">sub1</code> has received the red and green message as <code class="literal">news.uk</code> and <code class="literal">news.de</code>
- match binding key <code class="literal">news.#</code>. The red message has also gone to <code class="literal">sub2</code> and <code class="literal">sub3</code> as it's routing key
- is matched exactly by <code class="literal">news.uk</code> and by <code class="literal">*.uk</code>.</p><p>The routing key of the yellow message matches no binding keys, so the message is unroutable. It is handled as described
- in <a class="xref" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-UnroutableMessage" title="4.3.3. Unrouteable Messages">Section 4.3.3, âUnrouteable Messagesâ</a>.</p><div class="figure"><a name="idp7049824"></a><p class="title"><b>Figure 4.6. Topic exchange - matching on JMS message selector</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/Exchange-Topic-JMSSelector.png" alt="Topic exchange - matching on JMS message selector"></div></div></div><br class="figure-break"><p>The figure above illustrates messages with properties published with routing key <code class="literal">shipping</code>.</p><p>As before, the exchange routes each message to every bound queue whose binding key matches the routing key but as a JMS selector
- argument has been specified, the expression is evalutated against each matching message. Only messages whose message's header values or properties
- match the expression are routed to the queue.</p><p>In the case illustrated, <code class="literal">sub1</code> has received the yellow and blue message as their property <code class="literal">area</code>
- cause expression <code class="literal">area in ('Forties', 'Cromarty')</code> to evaluate true. Similarly, the yellow message has also gone to
- <code class="literal">gale_alert</code> as its property <code class="literal">speed</code> causes expression <code class="literal">speed > 7 and speed < 10</code>.
- to evaluate true.</p><p>The properties of purple message cause expressions no evaluate true, so the message is unroutable. It is handled as described in
- <a class="xref" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-UnroutableMessage" title="4.3.3. Unrouteable Messages">Section 4.3.3, âUnrouteable Messagesâ</a>.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-Concepts-Exchanges-Types-Fanout"></a>4.3.2.3. Fanout</h4></div></div></div><p>The fanout exchange type routes messages to all queues bound to the exchange, regardless of the message's routing key.</p><div class="figure"><a name="idp7059440"></a><p class="title"><b>Figure 4.7. Fanout exchange</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/Exchange-Fanout.png" alt="Fanout exchange"></div></div></div><br class="figure-break"></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-Concepts-Exchanges-Types-Headers"></a>4.3.2.4. Headers</h4></div></div></div><p>The headers exchange type routes message
s to queues based on header properties within the AMQP message. The message is
- passed to a queue if the header properties of the message satisfy header matching arguments table with which the queue was bound.
- </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="Java-Broker-Concepts-Exchanges-UnroutableMessage"></a>4.3.3. Unrouteable Messages</h3></div></div></div><p>If an exchange is unable to route a message to any queues, the Broker will:
+ wildcard rules described above apply.</p><p>In the case illustrated, <code class="literal">sub1</code> has received the red and green message as "<code class="literal">news.uk</code>" and "<code class="literal">news.de</code>"
+ match binding key "<code class="literal">news.#</code>". The red message has also gone to <code class="literal">sub2</code> and <code class="literal">sub3</code> as it's routing key
+ is matched exactly by "<code class="literal">news.uk</code>" and by "<code class="literal">*.uk</code>".</p><p>The routing key of the yellow message matches no binding keys, so the message is unroutable. It is handled as described
+ in <a class="xref" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-UnroutableMessage" title="4.3.4. Unrouteable Messages">Section 4.3.4, âUnrouteable Messagesâ</a>.</p><div class="figure"><a name="idp7064000"></a><p class="title"><b>Figure 4.6. Topic exchange - matching on JMS message selector</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/Exchange-Topic-JMSSelector.png" alt="Topic exchange - matching on JMS message selector"></div></div></div><br class="figure-break"><p>The figure above illustrates messages with properties published with routing key "<code class="literal">shipping</code>".</p><p>As before, the exchange routes each message to every bound queue whose binding key matches the routing key but as a JMS selector
+ argument has been specified, the expression is evaluated against each matching message. Only messages whose message header values or properties
+ match the expression are routed to the queue.</p><p>In the case illustrated, <code class="literal">sub1</code> has received the yellow and blue message as their property "<code class="literal">area</code>"
+ cause expression "<code class="literal">area in ('Forties', 'Cromarty')</code>" to evaluate true. Similarly, the yellow message has also gone to
+ <code class="literal">gale_alert</code> as its property "<code class="literal">speed</code>" causes expression "<code class="literal">speed > 7 and speed < 10</code>"
+ to evaluate true.</p><p>The properties of purple message cause no expressions to evaluate true, so the message is unroutable. It is handled as described in
+ <a class="xref" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-UnroutableMessage" title="4.3.4. Unrouteable Messages">Section 4.3.4, âUnrouteable Messagesâ</a>.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-Concepts-Exchanges-Types-Fanout"></a>4.3.2.3. Fanout</h4></div></div></div><p>The fanout exchange type routes messages to all queues bound to the exchange, regardless of the message's routing key.</p><p>Filter rules may be specified using a <a class="link" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-BindingArguments-JMSSelector" title="4.3.3.1. JMS Selector">
+ binding argument specifying a JMS message selector</a>.</p><div class="figure"><a name="idp7074784"></a><p class="title"><b>Figure 4.7. Fanout exchange</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/Exchange-Fanout.png" alt="Fanout exchange"></div></div></div><br class="figure-break"></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-Concepts-Exchanges-Types-Headers"></a>4.3.2.4. Headers</h4></div></div></div><p>The headers exchange type routes messages to queues based on header properties within the message. The message is passed to
+ a queue if the header properties of the message satisfy the <a class="link" href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-BindingArguments-x-match" title="4.3.3.2. x-match">
+ x-match expression</a> specified by the binding arguments with which the queue was bound.
+ </p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="Java-Broker-Concepts-Exchanges-BindingArguments"></a>4.3.3. Binding Arguments</h3></div></div></div><p>Binding arguments are used by certain exchange types to further filter messages.</p><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-Concepts-Exchanges-BindingArguments-JMSSelector"></a>4.3.3.1. JMS Selector</h4></div></div></div><p>The binding argument <code class="literal">x-filter-jms-selector</code> specifies a JMS selector conditional expression. The expression
+ is written in terms of message header and message property names. If the expression evaluates to true, the message is routed to the queue.
+ This type of binding argument is understood by exchange types direct, topic and fanout.<a href="#ftn.idp7083136" class="footnote" name="idp7083136"><sup class="footnote">[4]</sup></a>.</p></div><div class="section"><div class="titlepage"><div><div><h4 class="title"><a name="Java-Broker-Concepts-Exchanges-BindingArguments-x-match"></a>4.3.3.2. x-match</h4></div></div></div><p>The binding argument <code class="literal">x-match</code> is understood by exchange type headers. It can take two values, dictating how the
+ rest of the name value pairs are treated during matching.</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><code class="literal">all</code> implies that all the other pairs must match the headers property of a message for that message to be routed
+ (i.e. an AND match)</li><li class="listitem">any<code class="literal"></code> implies that the message should be routed if any of the fields in the headers property match one of the
+ fields in the arguments table (i.e. an OR match)</li></ul></div><p>A field in the bind arguments matches a field in the message if either the field in the bind arguments has no value and a field of the
+ same name is present in the message headers or if the field in the bind arguments has a value and a field of the same name exists in the
+ message headers and has that same value.</p></div></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="Java-Broker-Concepts-Exchanges-UnroutableMessage"></a>4.3.4. Unrouteable Messages</h3></div></div></div><p>If an exchange is unable to route a message to any queues, the Broker will:
</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem">If using AMQP 0-10 protocol, and an alternate exchange has been set on the exchange, the message is routed to the alternate exchange.
The alternate exchange routes the message according to its routing algorithm and its binding table. If the messages is still unroutable,
- the message is discarded.</li><li class="listitem">If using AMQP protocols 0-8..0-9-1, and the publisher set the mandatory flag, the message is returned to the Producer.</li><li class="listitem">Otherwise, the message is discarded.</li></ul></div><p>
- </p></div><div class="footnotes"><br><hr width="100" align="left"><div id="ftn.idp7036560" class="footnote"><p><a href="#idp7036560" class="para"><sup class="para">[4] </sup></a>This is a Qpid specific extension.</p></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Java-Broker-Concepts-Virtual-Hosts.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Java-Broker-Concepts.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Java-Broker-Concepts-Queues.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.2. Virtual Hosts </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4.4. Queues</td></tr></table></div><div class="main_text_area_bottom"></div></div></div></body></html>
+ the message is discarded.</li><li class="listitem">If using AMQP protocols 0-8..0-9-1, and the publisher set the mandatory flag and the<a class="link" href="Java-Broker-Close-Connection-When-No-Route.html" title="12.6. Closing client connections on unroutable mandatory messages">
+ close when no route</a> feature is disabled, the message is returned to the Producer.</li><li class="listitem">Otherwise, the message is discarded.</li></ul></div><p>
+ </p></div><div class="footnotes"><br><hr width="100" align="left"><div id="ftn.idp7083136" class="footnote"><p><a href="#idp7083136" class="para"><sup class="para">[4] </sup></a>
+ This is a Qpid specific extension.</p></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Java-Broker-Concepts-Virtual-Hosts.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Java-Broker-Concepts.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Java-Broker-Concepts-Queues.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">4.2. Virtual Hosts </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4.4. Queues</td></tr></table></div><div class="main_text_area_bottom"></div></div></div></body></html>
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts-Virtual-Hosts.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts-Virtual-Hosts.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts-Virtual-Hosts.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts-Virtual-Hosts.html Tue Oct 8 22:32:49 2013
@@ -4,7 +4,7 @@ and associated objects. Client <span cla
with one being configured as the default for clients that can't or don't specify which they wish to connect to.
</p><p>
The following diagram depicts the Virtual Host model:
- </p><div class="figure"><a name="idp6995392"></a><p class="title"><b>Figure 4.2. Virtual Host Model</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/VirtualHost-Model.png" alt="Virtual Host Model"></div></div></div><p><br class="figure-break">
+ </p><div class="figure"><a name="idp6808768"></a><p class="title"><b>Figure 4.2. Virtual Host Model</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/VirtualHost-Model.png" alt="Virtual Host Model"></div></div></div><p><br class="figure-break">
</p><p>Each <span class="emphasis"><em>Virtual Host</em></span> has its own <span class="emphasis"><em>Message Store</em></span> which is used to store persistent
messages on durable <span class="emphasis"><em>Queues</em></span> it contains, as well as the configuration of any durable
<span class="emphasis"><em>Queues</em></span>, <span class="emphasis"><em>Exchanges</em></span>, and <span class="emphasis"><em>Bindings</em></span> made during its operation.</p><p>
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Concepts.html Tue Oct 8 22:32:49 2013
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 4. Concepts</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="AMQP Messaging Broker (Java)"><link rel="up" href="index.html" title="AMQP Messaging Broker (Java)"><link rel="prev" href="Java-Broker-Getting-Started-CommandLine.html" title="3.5. Using the command line"><link rel="next" href="Java-Broker-Concepts-Virtual-Hosts.html" title="4.2. Virtual Hosts"></head><body><div class="container" bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><DIV class="header"><DIV class="logo"><H1>Apache Qpidâ¢</H1><H2>Open Source AMQP Messaging</H2></DIV></DIV><DIV class="menu_box"><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Apache Qpid</H3><UL><LI><A href="http://qpid.apache.org/index.html">Home</A></LI><LI><A href="http://
qpid.apache.org/download.html">Download</A></LI><LI><A href="http://qpid.apache.org/getting_started.html">Getting Started</A></LI><LI><A href="http://www.apache.org/licenses/">License</A></LI><LI><A href="https://cwiki.apache.org/qpid/faq.html">FAQ</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Documentation</H3><UL><LI><A href="http://qpid.apache.org/documentation.html#doc-release">Latest Release</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-trunk">Trunk</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-archives">Archive</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Community</H3><UL><LI><A href="http://qpid.apache.org/getting_involved.html">Getting Involved</A></LI><LI><A href="http://qpid.apache.org/source_repository.html">Source Repository</A></LI><LI><A href="http://qpid.apache.org/mailing_lists.html">
Mailing Lists</A></LI><LI><A href="https://cwiki.apache.org/qpid/">Wiki</A></LI><LI><A href="https://issues.apache.org/jira/browse/qpid">Issue Reporting</A></LI><LI><A href="http://qpid.apache.org/people.html">People</A></LI><LI><A href="http://qpid.apache.org/acknowledgements.html">Acknowledgements</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Developers</H3><UL><LI><A href="https://cwiki.apache.org/qpid/building.html">Building Qpid</A></LI><LI><A href="https://cwiki.apache.org/qpid/developer-pages.html">Developer Pages</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About AMQP</H3><UL><LI><A href="http://qpid.apache.org/amqp.html">What is AMQP?</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About Apache</H3><UL><LI><A href="http://www.apache.org">Home</A></LI><LI><A href="ht
tp://www.apache.org/foundation/sponsorship.html">Sponsorship</A></LI><LI><A href="http://www.apache.org/foundation/thanks.html">Thanks</A></LI><LI><A href="http://www.apache.org/security/">Security</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV></DIV><div class="main_text_area"><div class="main_text_area_top"></div><div class="main_text_area_body"><DIV class="breadcrumbs"><span class="breadcrumb-link"><a href="index.html">AMQP Messaging Broker (Java)</a></span> > <span class="breadcrumb-node">Concepts</span></DIV><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="Java-Broker-Concepts"></a>Chapter 4. Concepts</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="Java-Broker-Concepts.html#Java-Broker-Concepts-Broker">4.1. Broker</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Virtual-Hosts.html">4.2. Virtual Hosts</a></span></dt><dt><span class="secti
on"><a href="Java-Broker-Concepts-Exchanges.html">4.3. Exchanges</a></span></dt><dd><dl><dt><span class="section"><a href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-Predeclared">4.3.1. Predeclared Exchanges</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-Types">4.3.2. Exchange Types</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-UnroutableMessage">4.3.3. Unrouteable Messages</a></span></dt></dl></dd><dt><span class="section"><a href="Java-Broker-Concepts-Queues.html">4.4. Queues</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Ports.html">4.5. Ports</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Authentication-Providers.html">4.6. Authentication Providers</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Other-Services.html">4.7. Other Services</a></span><
/dt><dd><dl><dt><span class="section"><a href="Java-Broker-Concepts-Other-Services.html#Java-Broker-Concepts-Access-Control-Providers">4.7.1. Access Control Providers</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Other-Services.html#Java-Broker-Concepts-Group-Providers">4.7.2. Group Providers</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Other-Services.html#Java-Broker-Concepts-Keystores">4.7.3. Keystores</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Other-Services.html#Java-Broker-Concepts-Truststores">4.7.4. Truststores</a></span></dt></dl></dd></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title"><a name="Java-Broker-Concepts-Broker"></a>4.1. Broker</h2></div></div></div><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 4. Concepts</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="AMQP Messaging Broker (Java)"><link rel="up" href="index.html" title="AMQP Messaging Broker (Java)"><link rel="prev" href="Java-Broker-Getting-Started-CommandLine.html" title="3.5. Using the command line"><link rel="next" href="Java-Broker-Concepts-Virtual-Hosts.html" title="4.2. Virtual Hosts"></head><body><div class="container" bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><DIV class="header"><DIV class="logo"><H1>Apache Qpidâ¢</H1><H2>Open Source AMQP Messaging</H2></DIV></DIV><DIV class="menu_box"><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Apache Qpid</H3><UL><LI><A href="http://qpid.apache.org/index.html">Home</A></LI><LI><A href="http://
qpid.apache.org/download.html">Download</A></LI><LI><A href="http://qpid.apache.org/getting_started.html">Getting Started</A></LI><LI><A href="http://www.apache.org/licenses/">License</A></LI><LI><A href="https://cwiki.apache.org/qpid/faq.html">FAQ</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Documentation</H3><UL><LI><A href="http://qpid.apache.org/documentation.html#doc-release">Latest Release</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-trunk">Trunk</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-archives">Archive</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Community</H3><UL><LI><A href="http://qpid.apache.org/getting_involved.html">Getting Involved</A></LI><LI><A href="http://qpid.apache.org/source_repository.html">Source Repository</A></LI><LI><A href="http://qpid.apache.org/mailing_lists.html">
Mailing Lists</A></LI><LI><A href="https://cwiki.apache.org/qpid/">Wiki</A></LI><LI><A href="https://issues.apache.org/jira/browse/qpid">Issue Reporting</A></LI><LI><A href="http://qpid.apache.org/people.html">People</A></LI><LI><A href="http://qpid.apache.org/acknowledgements.html">Acknowledgements</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Developers</H3><UL><LI><A href="https://cwiki.apache.org/qpid/building.html">Building Qpid</A></LI><LI><A href="https://cwiki.apache.org/qpid/developer-pages.html">Developer Pages</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About AMQP</H3><UL><LI><A href="http://qpid.apache.org/amqp.html">What is AMQP?</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About Apache</H3><UL><LI><A href="http://www.apache.org">Home</A></LI><LI><A href="ht
tp://www.apache.org/foundation/sponsorship.html">Sponsorship</A></LI><LI><A href="http://www.apache.org/foundation/thanks.html">Thanks</A></LI><LI><A href="http://www.apache.org/security/">Security</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV></DIV><div class="main_text_area"><div class="main_text_area_top"></div><div class="main_text_area_body"><DIV class="breadcrumbs"><span class="breadcrumb-link"><a href="index.html">AMQP Messaging Broker (Java)</a></span> > <span class="breadcrumb-node">Concepts</span></DIV><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="Java-Broker-Concepts"></a>Chapter 4. Concepts</h1></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="Java-Broker-Concepts.html#Java-Broker-Concepts-Broker">4.1. Broker</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Virtual-Hosts.html">4.2. Virtual Hosts</a></span></dt><dt><span class="secti
on"><a href="Java-Broker-Concepts-Exchanges.html">4.3. Exchanges</a></span></dt><dd><dl><dt><span class="section"><a href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-Predeclared">4.3.1. Predeclared Exchanges</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-Types">4.3.2. Exchange Types</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-BindingArguments">4.3.3. Binding Arguments</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Exchanges.html#Java-Broker-Concepts-Exchanges-UnroutableMessage">4.3.4. Unrouteable Messages</a></span></dt></dl></dd><dt><span class="section"><a href="Java-Broker-Concepts-Queues.html">4.4. Queues</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Ports.html">4.5. Ports</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Authentication-Providers
.html">4.6. Authentication Providers</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Other-Services.html">4.7. Other Services</a></span></dt><dd><dl><dt><span class="section"><a href="Java-Broker-Concepts-Other-Services.html#Java-Broker-Concepts-Access-Control-Providers">4.7.1. Access Control Providers</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Other-Services.html#Java-Broker-Concepts-Group-Providers">4.7.2. Group Providers</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Other-Services.html#Java-Broker-Concepts-Keystores">4.7.3. Keystores</a></span></dt><dt><span class="section"><a href="Java-Broker-Concepts-Other-Services.html#Java-Broker-Concepts-Truststores">4.7.4. Truststores</a></span></dt></dl></dd></dl></div><div class="section"><div class="titlepage"><div><div><h2 class="title"><a name="Java-Broker-Concepts-Broker"></a>4.1. Broker</h2></div></div></div><p>
The Qpid Broker has one or more <span class="emphasis"><em>Virtual Hosts</em></span> (independent containers of <span class="emphasis"><em>Queues</em></span>,
<span class="emphasis"><em>Exchanges</em></span>, etc) sharing a connection, authentication, and access control model via the configured
<span class="emphasis"><em>Ports</em></span>, <span class="emphasis"><em>Authentication Providers</em></span>, <span class="emphasis"><em>Group providers</em></span> and
@@ -7,6 +7,6 @@
also provides management plugins to allow configuring and monitoring it.
</p><p>
The following diagram depicts the Broker model:
- </p><div class="figure"><a name="idp6907984"></a><p class="title"><b>Figure 4.1. Broker Model</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/Broker-Model.png" alt="Broker Model"></div></div></div><p><br class="figure-break">
+ </p><div class="figure"><a name="idp6908112"></a><p class="title"><b>Figure 4.1. Broker Model</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/Broker-Model.png" alt="Broker Model"></div></div></div><p><br class="figure-break">
These concepts will be expanded upon in the forthcoming pages.
</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Java-Broker-Getting-Started-CommandLine.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="Java-Broker-Concepts-Virtual-Hosts.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">3.5. Using the command line </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 4.2. Virtual Hosts</td></tr></table></div><div class="main_text_area_bottom"></div></div></div></body></html>
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Configuring-And-Managing-HTTP-Management.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Configuring-And-Managing-HTTP-Management.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Configuring-And-Managing-HTTP-Management.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Configuring-And-Managing-HTTP-Management.html Tue Oct 8 22:32:49 2013
@@ -22,7 +22,7 @@
instance although it is still evolving toward being fully considered a seperately supported interface.
</p><p>The brokers REST interface support traditional REST model which uses the GET method requests to retrieve
the information about broker configured objects, DELETE method requests to delete the configured object,
- PUT to create or update the configured object and POST to perform the configured objects updates not available with the PUT requests.</p><p>The table below lists the available REST services with brief description how they can be used.</p><div class="table"><a name="idp7289008"></a><p class="title"><b>Table 5.2. Rest services</b></p><div class="table-contents"><table summary="Rest services" border="1"><colgroup><col><col><col><col><col><col></colgroup><thead><tr><th>REST Service URL</th><th>Description</th><th>GET</th><th>PUT</th><th>POST</th><th>DELETE</th></tr></thead><tbody><tr><td><p>/rest/broker</p></td><td><p>Rest service to manage broker instance</p></td><td><p>Retrieves the details of broker configuration</p></td><td><p>Updates broker attributes</p></td><td><p>Not implemented yet</p></td><td><p>Not implemented yet</p></td></tr><tr><td><p>/rest/authenticationprovider</p>
+ PUT to create or update the configured object and POST to perform the configured objects updates not available with the PUT requests.</p><p>The table below lists the available REST services with brief description how they can be used.</p><div class="table"><a name="idp7301872"></a><p class="title"><b>Table 5.2. Rest services</b></p><div class="table-contents"><table summary="Rest services" border="1"><colgroup><col><col><col><col><col><col></colgroup><thead><tr><th>REST Service URL</th><th>Description</th><th>GET</th><th>PUT</th><th>POST</th><th>DELETE</th></tr></thead><tbody><tr><td><p>/rest/broker</p></td><td><p>Rest service to manage broker instance</p></td><td><p>Retrieves the details of broker configuration</p></td><td><p>Updates broker attributes</p></td><td><p>Not implemented yet</p></td><td><p>Not implemented yet</p></td></tr><tr><td><p>/rest/authenticationprovider</p>
<p>/rest/authenticationprovider/<authentication provider name></p>
</td><td>Rest service to manage authentication providers on the broker</td><td>Retrieves the details about authentication providers</td><td>Creates or updates authentication providers</td><td>Not implemented yet</td><td>Deletes authentication providers</td></tr><tr><td><p>/rest/user</p>
<p>/rest/user/<authentication provider name>/<user name></p>
@@ -76,12 +76,12 @@
If <span class="emphasis"><em><binding></em></span> and <span class="emphasis"><em><queue></em></span> are omitted in binding REST URL
(http://localhost:8080/rest/binding/<vhostname>/<exchangename>) the GET request will result in returning
all bindings for all queues for the given exchange in the virtual host.
- </p><div class="example"><a name="idp7367984"></a><p class="title"><b>Example 5.2. Examples of queue creation using curl (authenticating as user admin):</b></p><div class="example-contents"><pre class="programlisting">
+ </p><div class="example"><a name="idp7380848"></a><p class="title"><b>Example 5.2. Examples of queue creation using curl (authenticating as user admin):</b></p><div class="example-contents"><pre class="programlisting">
#create a durable queue
curl --user admin -X PUT -d '{"durable":true}' http://localhost:8080/rest/queue/<vhostname>/<queuename>
#create a durable priority queue
curl --user admin -X PUT -d '{"durable":true,"type":"priority"}' http://localhost:8080/rest/queue/<vhostname>/<queuename>
- </pre></div></div><br class="example-break"><div class="example"><a name="idp7369392"></a><p class="title"><b>Example 5.3. Example of binding a queue to an exchange using curl</b></p><div class="example-contents"><pre class="programlisting">
+ </pre></div></div><br class="example-break"><div class="example"><a name="idp7382256"></a><p class="title"><b>Example 5.3. Example of binding a queue to an exchange using curl</b></p><div class="example-contents"><pre class="programlisting">
curl --user admin -X PUT -d '{}' http://localhost:8080/rest/binding/<vhostname>/<exchangename>/<queue-name>/<binding-name>
</pre></div></div><br class="example-break"><p>
NOTE: These curl examples utilise unsecure HTTP transport. To use the examples it is first necessary enable Basic
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Configuring-And-Managing.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Configuring-And-Managing.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Configuring-And-Managing.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-Configuring-And-Managing.html Tue Oct 8 22:32:49 2013
@@ -83,7 +83,7 @@ $ ./qpid-server -st memory
If both are defined, System Property values take precedence.
</p><p>
The broker has the following set of core configuration properties, with the indicated default values if not otherwise configured by the user:
- </p><div class="table"><a name="idp7223168"></a><p class="title"><b>Table 5.1. Base Configuration Properties</b></p><div class="table-contents"><table summary="Base Configuration Properties" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>
+ </p><div class="table"><a name="idp7233328"></a><p class="title"><b>Table 5.1. Base Configuration Properties</b></p><div class="table-contents"><table summary="Base Configuration Properties" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>
Name
</th><th>
Description
@@ -148,7 +148,7 @@ $ ./qpid-server -prop "qpid.amqp_port=10
</p><p>
NOTE: When running the broker on Windows and starting it via the qpid-server.bat file, the "name=value" argument MUST be quoted.
</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="Java-Broker-Configuring-And-Managing-Configuration-Initial-Config-Example"></a>5.1.8. Example of JSON 'Initial Configuration'</h3></div></div></div><p>
- An example of the default 'Initial Configuration' JSON file the broker uses is provided below:</p><div class="example"><a name="idp7246208"></a><p class="title"><b>Example 5.1. JSON 'Initial configuration' File</b></p><div class="example-contents"><pre class="programlisting">
+ An example of the default 'Initial Configuration' JSON file the broker uses is provided below:</p><div class="example"><a name="idp7256368"></a><p class="title"><b>Example 5.1. JSON 'Initial configuration' File</b></p><div class="example-contents"><pre class="programlisting">
{
"name" : "Broker",
"defaultVirtualHost" : "default",
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Backup.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Backup.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Backup.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Backup.html Tue Oct 8 22:32:49 2013
@@ -1,5 +1,5 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>13.13. Backups</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="AMQP Messaging Broker (Java)"><link rel="up" href="Java-Broker-High-Availability.html" title="Chapter 13. High Availability"><link rel="prev" href="Java-Broker-High-Availability-Security.html" title="13.12. Security"><link rel="next" href="Java-Broker-High-Availability-MigrationFromNonHA.html" title="13.14. Migration of a non-HA store to HA"></head><body><div class="container" bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><DIV class="header"><DIV class="logo"><H1>Apache Qpidâ¢</H1><H2>Open Source AMQP Messaging</H2></DIV></DIV><DIV class="menu_box"><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Apache Qpid</H3><UL><LI><A href="http://qpid.apache.org
/index.html">Home</A></LI><LI><A href="http://qpid.apache.org/download.html">Download</A></LI><LI><A href="http://qpid.apache.org/getting_started.html">Getting Started</A></LI><LI><A href="http://www.apache.org/licenses/">License</A></LI><LI><A href="https://cwiki.apache.org/qpid/faq.html">FAQ</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Documentation</H3><UL><LI><A href="http://qpid.apache.org/documentation.html#doc-release">Latest Release</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-trunk">Trunk</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-archives">Archive</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Community</H3><UL><LI><A href="http://qpid.apache.org/getting_involved.html">Getting Involved</A></LI><LI><A href="http://qpid.apache.org/source_repository.html">Source Repository</A></LI><LI><A hre
f="http://qpid.apache.org/mailing_lists.html">Mailing Lists</A></LI><LI><A href="https://cwiki.apache.org/qpid/">Wiki</A></LI><LI><A href="https://issues.apache.org/jira/browse/qpid">Issue Reporting</A></LI><LI><A href="http://qpid.apache.org/people.html">People</A></LI><LI><A href="http://qpid.apache.org/acknowledgements.html">Acknowledgements</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Developers</H3><UL><LI><A href="https://cwiki.apache.org/qpid/building.html">Building Qpid</A></LI><LI><A href="https://cwiki.apache.org/qpid/developer-pages.html">Developer Pages</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About AMQP</H3><UL><LI><A href="http://qpid.apache.org/amqp.html">What is AMQP?</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About Apache</H3><UL><LI><A href="http:
//www.apache.org">Home</A></LI><LI><A href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</A></LI><LI><A href="http://www.apache.org/foundation/thanks.html">Thanks</A></LI><LI><A href="http://www.apache.org/security/">Security</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV></DIV><div class="main_text_area"><div class="main_text_area_top"></div><div class="main_text_area_body"><DIV class="breadcrumbs"><span class="breadcrumb-link"><a href="index.html">AMQP Messaging Broker (Java)</a></span> > <span class="breadcrumb-link"><a href="Java-Broker-High-Availability.html">High Availability</a></span> > <span class="breadcrumb-node">Backups</span></DIV><div class="section"><div class="titlepage"><div><div><h2 class="title"><a name="Java-Broker-High-Availability-Backup"></a>13.13. Backups</h2></div></div></div><p>In order to protect the entire cluster from some cataclysms which might destroy all cluster nodes,
backups of the Master store should be taken on a regular basis.</p><p>Qpid Broker distribution includes the "hot" backup utility <span class="emphasis"><em>backup.sh</em></span> which can be found at broker bin folder.
- This utility can perform the backup when broker is running.</p><p><span class="emphasis"><em>backup.sh</em></span> script invokes <code class="classname">org.apache.qpid.server.store.berkeleydb.BDBBackup</code> to do the job.</p><p>You can also run this class from command line like in an example below:</p><div class="example"><a name="idp8355344"></a><p class="title"><b>Example 13.5. Performing store backup by using <code class="classname">BDBBackup</code> class directly</b></p><div class="example-contents"><span class="command"><strong>
- java -cp qpid-bdbstore-0.18.jar org.apache.qpid.server.store.berkeleydb.BDBBackup -fromdir path/to/store/folder -todir path/to/backup/foldeAr</strong></span></div></div><br class="example-break"><p>In the example above BDBBackup utility is called from qpid-bdbstore-0.18.jar to backup the store at <span class="emphasis"><em>path/to/store/folder</em></span> and copy store logs into <span class="emphasis"><em>path/to/backup/folder</em></span>.</p><p>Linux and Unix users can take advantage of <span class="emphasis"><em>backup.sh</em></span> bash script by running this script in a similar way.</p><div class="example"><a name="idp8359200"></a><p class="title"><b>Example 13.6. Performing store backup by using <code class="classname">backup.sh</code> bash script</b></p><div class="example-contents"><span class="command"><strong>backup.sh -fromdir path/to/store/folder -todir path/to/backup/folder</strong></span></div></div><br class="example-break"><div class="note" style="marg
in-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Do not forget to ensure that the Master store is being backed up, in the event the Node elected Master changes during
+ This utility can perform the backup when broker is running.</p><p><span class="emphasis"><em>backup.sh</em></span> script invokes <code class="classname">org.apache.qpid.server.store.berkeleydb.BDBBackup</code> to do the job.</p><p>You can also run this class from command line like in an example below:</p><div class="example"><a name="idp8368784"></a><p class="title"><b>Example 13.5. Performing store backup by using <code class="classname">BDBBackup</code> class directly</b></p><div class="example-contents"><span class="command"><strong>
+ java -cp qpid-bdbstore-0.18.jar org.apache.qpid.server.store.berkeleydb.BDBBackup -fromdir path/to/store/folder -todir path/to/backup/foldeAr</strong></span></div></div><br class="example-break"><p>In the example above BDBBackup utility is called from qpid-bdbstore-0.18.jar to backup the store at <span class="emphasis"><em>path/to/store/folder</em></span> and copy store logs into <span class="emphasis"><em>path/to/backup/folder</em></span>.</p><p>Linux and Unix users can take advantage of <span class="emphasis"><em>backup.sh</em></span> bash script by running this script in a similar way.</p><div class="example"><a name="idp8372640"></a><p class="title"><b>Example 13.6. Performing store backup by using <code class="classname">backup.sh</code> bash script</b></p><div class="example-contents"><span class="command"><strong>backup.sh -fromdir path/to/store/folder -todir path/to/backup/folder</strong></span></div></div><br class="example-break"><div class="note" style="marg
in-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Do not forget to ensure that the Master store is being backed up, in the event the Node elected Master changes during
the lifecycle of the cluster.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Java-Broker-High-Availability-Security.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Java-Broker-High-Availability.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Java-Broker-High-Availability-MigrationFromNonHA.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">13.12. Security </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 13.14. Migration of a non-HA store to HA</td></tr></table></div><div class="main_text_area_bottom"></div></div></div></body></html>
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-ClientFailover.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-ClientFailover.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-ClientFailover.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-ClientFailover.html Tue Oct 8 22:32:49 2013
@@ -5,6 +5,6 @@
The recommended value for <span class="emphasis"><em>connectdelay</em></span> option in broker URL should be set to
the value greater than 1000 milliseconds. If it is desired that clients re-connect automatically after a
master to replica failure, <code class="varname">cyclecount</code> should be tuned so that the retry period is longer than
- the expected length of time to perform the failover.</p><div class="example"><a name="idp8269504"></a><p class="title"><b>Example 13.2. Example of connection URL for the HA Cluster</b></p><div class="example-contents">
+ the expected length of time to perform the failover.</p><div class="example"><a name="idp8282944"></a><p class="title"><b>Example 13.2. Example of connection URL for the HA Cluster</b></p><div class="example-contents">
amqp://guest:guest@clientid/test?brokerlist='tcp://localhost:5672?connectdelay='2000'&retries='3';tcp://localhost:5671?connectdelay='2000'&retries='3';tcp://localhost:5673?connectdelay='2000'&retries='3''&failover='roundrobin?cyclecount='30''
</div></div><br class="example-break"></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Java-Broker-High-Availability-DurabilityGuarantee.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Java-Broker-High-Availability.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Java-Broker-High-Availability-JMXAPI.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">13.6. Durability Guarantees </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 13.8. Qpid JMX API for HA</td></tr></table></div><div class="main_text_area_bottom"></div></div></div></body></html>
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Configuration.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Configuration.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Configuration.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-Configuration.html Tue Oct 8 22:32:49 2013
@@ -1,6 +1,6 @@
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>13.5. Configuring a Virtual Host to be a node</title><link rel="stylesheet" type="text/css" href="css/style.css"><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="AMQP Messaging Broker (Java)"><link rel="up" href="Java-Broker-High-Availability.html" title="Chapter 13. High Availability"><link rel="prev" href="Java-Broker-High-Availability-MultiNodeCluster.html" title="13.4. Multi Node Cluster"><link rel="next" href="Java-Broker-High-Availability-DurabilityGuarantee.html" title="13.6. Durability Guarantees"></head><body><div class="container" bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><DIV class="header"><DIV class="logo"><H1>Apache Qpidâ¢</H1><H2>Open Source AMQP Messaging</H2></DIV></DIV><DIV class="menu_box"><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Apache Qpid</H3><UL
><LI><A href="http://qpid.apache.org/index.html">Home</A></LI><LI><A href="http://qpid.apache.org/download.html">Download</A></LI><LI><A href="http://qpid.apache.org/getting_started.html">Getting Started</A></LI><LI><A href="http://www.apache.org/licenses/">License</A></LI><LI><A href="https://cwiki.apache.org/qpid/faq.html">FAQ</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Documentation</H3><UL><LI><A href="http://qpid.apache.org/documentation.html#doc-release">Latest Release</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-trunk">Trunk</A></LI><LI><A href="http://qpid.apache.org/documentation.html#doc-archives">Archive</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Community</H3><UL><LI><A href="http://qpid.apache.org/getting_involved.html">Getting Involved</A></LI><LI><A href="http://qpid.apache.org/source_repository.html">
Source Repository</A></LI><LI><A href="http://qpid.apache.org/mailing_lists.html">Mailing Lists</A></LI><LI><A href="https://cwiki.apache.org/qpid/">Wiki</A></LI><LI><A href="https://issues.apache.org/jira/browse/qpid">Issue Reporting</A></LI><LI><A href="http://qpid.apache.org/people.html">People</A></LI><LI><A href="http://qpid.apache.org/acknowledgements.html">Acknowledgements</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Developers</H3><UL><LI><A href="https://cwiki.apache.org/qpid/building.html">Building Qpid</A></LI><LI><A href="https://cwiki.apache.org/qpid/developer-pages.html">Developer Pages</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>About AMQP</H3><UL><LI><A href="http://qpid.apache.org/amqp.html">What is AMQP?</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV><DIV class="menu_box_top"></DIV><DIV class="menu_box_body"><H3>Abo
ut Apache</H3><UL><LI><A href="http://www.apache.org">Home</A></LI><LI><A href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</A></LI><LI><A href="http://www.apache.org/foundation/thanks.html">Thanks</A></LI><LI><A href="http://www.apache.org/security/">Security</A></LI></UL></DIV><DIV class="menu_box_bottom"></DIV></DIV><div class="main_text_area"><div class="main_text_area_top"></div><div class="main_text_area_body"><DIV class="breadcrumbs"><span class="breadcrumb-link"><a href="index.html">AMQP Messaging Broker (Java)</a></span> > <span class="breadcrumb-link"><a href="Java-Broker-High-Availability.html">High Availability</a></span> > <span class="breadcrumb-node">Configuring a Virtual Host to be a node</span></DIV><div class="section"><div class="titlepage"><div><div><h2 class="title"><a name="Java-Broker-High-Availability-Configuration"></a>13.5. Configuring a Virtual Host to be a node</h2></div></div></div><p>To configure a virtualhost as a cluster no
de, configure the virtualhost.xml in the following manner:</p><p>
- </p><div class="example"><a name="idp8201216"></a><p class="title"><b>Example 13.1. Configuring a VirtualHost to use the BDBHAMessageStore</b></p><div class="example-contents"><pre class="programlisting">
+ </p><div class="example"><a name="idp8214656"></a><p class="title"><b>Example 13.1. Configuring a VirtualHost to use the BDBHAMessageStore</b></p><div class="example-contents"><pre class="programlisting">
<virtualhosts>
<virtualhost>
<name>vhostname</name>
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-DisasterRecovery.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-DisasterRecovery.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-DisasterRecovery.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-DisasterRecovery.html Tue Oct 8 22:32:49 2013
@@ -3,7 +3,7 @@
In case when HA message store needs to be restored on a different host with a different IP address
the cluster replication configuration should be reseted in this case</p><p>Oracle provides a command line utility <a class="ulink" href="http://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/rep/util/DbResetRepGroup.html" target="_top"><code class="classname">DbResetRepGroup</code></a>
to reset the members of a replication group and replace the group with a new group consisting of a single new member
- as described by the arguments supplied to the utility</p><p>Cluster can be restored with the following steps:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Copy log files into the store folder from backup</p></li><li class="listitem"><p>Use <code class="classname">DbResetRepGroup</code> to reset an existing environment. See an example below</p><div class="example"><a name="idp8380800"></a><p class="title"><b>Example 13.9. Reseting of replication group with <code class="classname">DbResetRepGroup</code></b></p><div class="example-contents"><span class="command"><strong>
+ as described by the arguments supplied to the utility</p><p>Cluster can be restored with the following steps:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Copy log files into the store folder from backup</p></li><li class="listitem"><p>Use <code class="classname">DbResetRepGroup</code> to reset an existing environment. See an example below</p><div class="example"><a name="idp8394240"></a><p class="title"><b>Example 13.9. Reseting of replication group with <code class="classname">DbResetRepGroup</code></b></p><div class="example-contents"><span class="command"><strong>
java -cp je-5.0.84.jar com.sleepycat.je.rep.util.DbResetRepGroup -h ha-work/Node-5001/bdbstore -groupName TestClusterGroup -nodeName Node-5001 -nodeHostPort localhost:5001</strong></span></div></div><br class="example-break"><p>In the example above <code class="classname">DbResetRepGroup</code> utility from Berkeley JE of version 5.0.84 is used to reset the store
at location <span class="emphasis"><em>ha-work/Node-5001/bdbstore</em></span> and set a replication group to <span class="emphasis"><em>TestClusterGroup</em></span>
having a node <span class="emphasis"><em>Node-5001</em></span> which runs at <span class="emphasis"><em>localhost:5001</em></span>.</p></li><li class="listitem"><p>Start a broker with HA store configured as specified on running of <code class="classname">DbResetRepGroup</code> utility.</p></li><li class="listitem"><p>Start replica nodes having the same replication group and a helper host port pointing to a new master. The store content will be copied into Replicas from Master on their start up.</p></li></ul></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="Java-Broker-High-Availability-MigrationFromNonHA.html">Prev</a>Â </td><td width="20%" align="center"><a accesskey="u" href="Java-Broker-High-Availability.html">Up</a></td><td width="40%" align="right">Â <a accesskey="n" href="Java-Broker-High-Availability-Performance.html">Next</a></td></tr><tr><td width="40%" align="
left" valign="top">13.14. Migration of a non-HA store to HA </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 13.16. Performance</td></tr></table></div><div class="main_text_area_bottom"></div></div></div></body></html>
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-DurabilityGuarantee.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-DurabilityGuarantee.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-DurabilityGuarantee.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-DurabilityGuarantee.html Tue Oct 8 22:32:49 2013
@@ -22,7 +22,7 @@
of this combination is described in the table below. It offers a good compromise between durability guarantee and performance
with writes being guaranteed on the master and the additional guarantee that a majority of replicas have received the
transaction.</p></div><div class="section"><div class="titlepage"><div><div><h3 class="title"><a name="Java-Broker-High-Availability-DurabilityGuarantee_Examples"></a>13.6.4. Examples</h3></div></div></div><p>Here are some examples illustrating the effects of the durability and coalescing-sync settings.</p><p>
- </p><div class="table"><a name="idp8249488"></a><p class="title"><b>Table 13.1. Effect of different durability guarantees</b></p><div class="table-contents"><table summary="Effect of different durability guarantees" border="1"><colgroup><col><col><col><col></colgroup><thead><tr><th> </th><th>Durability</th><th>Coalescing-sync</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>NO_SYNC, NO_SYNC, SIMPLE_MAJORITY</td><td>true</td><td>Before the commit returns to the client, the transaction will be written/sync'd to the Master's disk (effect of
+ </p><div class="table"><a name="idp8262928"></a><p class="title"><b>Table 13.1. Effect of different durability guarantees</b></p><div class="table-contents"><table summary="Effect of different durability guarantees" border="1"><colgroup><col><col><col><col></colgroup><thead><tr><th> </th><th>Durability</th><th>Coalescing-sync</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>NO_SYNC, NO_SYNC, SIMPLE_MAJORITY</td><td>true</td><td>Before the commit returns to the client, the transaction will be written/sync'd to the Master's disk (effect of
coalescing-sync) and a majority of the replica(s) will have acknowledged the <span class="bold"><strong>receipt</strong></span>
of the transaction. The replicas will write and sync the transaction to their disk at a point in the future governed by
<a class="ulink" href="http://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/rep/ReplicationMutableConfig.html#LOG_FLUSH_TASK_INTERVAL" target="_top">ReplicationMutableConfig#LOG_FLUSH_INTERVAL</a>.
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-JMXAPI.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-JMXAPI.html?rev=1530450&r1=1530449&r2=1530450&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-JMXAPI.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-Java-Book/html/Java-Broker-High-Availability-JMXAPI.html Tue Oct 8 22:32:49 2013
@@ -69,7 +69,7 @@
</td>
<td>void</td>
<td>Update the address of another node. The node must be in a STOPPED state.</td>
- </tr></tbody></table></div><div class="figure"><a name="idp8311488"></a><p class="title"><b>Figure 13.7. BDBHAMessageStore view from jconsole.</b></p><div class="figure-contents"><div><img src="images/HA-BDBHAMessageStore-MBean-jconsole.png" alt="BDBHAMessageStore view from jconsole."></div></div></div><br class="figure-break"><div class="example"><a name="idp8312896"></a><p class="title"><b>Example 13.3. Example of java code to get the node state value</b></p><div class="example-contents"><pre class="programlisting">
+ </tr></tbody></table></div><div class="figure"><a name="idp8324928"></a><p class="title"><b>Figure 13.7. BDBHAMessageStore view from jconsole.</b></p><div class="figure-contents"><div><img src="images/HA-BDBHAMessageStore-MBean-jconsole.png" alt="BDBHAMessageStore view from jconsole."></div></div></div><br class="figure-break"><div class="example"><a name="idp8326336"></a><p class="title"><b>Example 13.3. Example of java code to get the node state value</b></p><div class="example-contents"><pre class="programlisting">
Map<String, Object> environment = new HashMap<String, Object>();
// credentials: user name and password
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org