Author: robbie
Date: Mon Apr 7 09:49:14 2014
New Revision: 1585441
URL: http://svn.apache.org/r1585441
Log:
QPID-5664: correct documentation of the client side option value related to the
max-delivery feature
Modified:
qpid/trunk/qpid/doc/book/src/java-broker/Java-Broker-Runtime-Handling-Undeliverable-Messages.xml
Modified:
qpid/trunk/qpid/doc/book/src/java-broker/Java-Broker-Runtime-Handling-Undeliverable-Messages.xml
URL:
http://svn.apache.org/viewvc/qpid/trunk/qpid/doc/book/src/java-broker/Java-Broker-Runtime-Handling-Undeliverable-Messages.xml?rev=1585441&r1=1585440&r2=1585441&view=diff
==============================================================================
---
qpid/trunk/qpid/doc/book/src/java-broker/Java-Broker-Runtime-Handling-Undeliverable-Messages.xml
(original)
+++
qpid/trunk/qpid/doc/book/src/java-broker/Java-Broker-Runtime-Handling-Undeliverable-Messages.xml
Mon Apr 7 09:49:14 2014
@@ -65,7 +65,7 @@
once it reconnects.</para>
<para> If the consuming application is using AMQP 0-9-1, 0-9, or 0-8
protocols, it is necessary to
set the client system property <varname>qpid.reject.behaviour</varname> or
connection or binding
- URL option <varname>rejectbehaviour</varname> to the value
<literal>system</literal>.</para>
+ URL option <varname>rejectbehaviour</varname> to the value
<literal>server</literal>.</para>
<para>It is possible to determine the number of times a message has been
sent to a consumer via
the Management interfaces, but is not possible to determine this
information from a message client.
Specifically, the optional JMS message header
<property>JMSXDeliveryCount</property> is not
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
