Red Hat Bugzilla – Bug 1249942
[docs] Heartbeats for AMQP 1.0 Qpid Messaging API
Last modified: 2015-10-08 09:11:03 EDT
Documentation BZ about heartbeat support for AMQP 1.0 Qpid Messaging API.
Original discussion can be found in bugzilla #1151446
Jared's last comment:
(In reply to Ken Giusti from comment #16)
> In summary - the documentation for connection heartbeats is not correct. We
> should drop the recommendation to set heartbeats to 1/2 the tcp retransmit
> interval. Applications should be free to determine how long a link remains
> unresponsive - not TCP.
> The semantics column should simply say something like this:
> Requests that heartbeats be sent every N seconds. If two successive
> heartbeats are missed the connection is considered lost and will fail or
> start the reconnect process if configured to do so.
This recommendation is now included in the docs. Thanks for providing this clarifying text, Ken.
Documentation seems ok apart from this minor error:
"Table 20.2. Broker List URL Options" you have there option "heartbeat" which should be "idle_timeout" as this table is for JMS client.
You have it correctly written at the end of "16.5. Failover Behavior in Java JMS Clients" part, witch example.
Moving "back" to assigned from previous state on_qa (moved by Jared), before creating this documentation bugzilla.
Taking ownership of MRG-M bugs
I have verified the proposed change. Looks good.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.