[
https://issues.apache.org/jira/browse/QPID-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644240#comment-14644240
]
ASF subversion and git services commented on QPID-6661:
-------------------------------------------------------
Commit 1693067 from [~gsim] in branch 'qpid/trunk'
[ https://svn.apache.org/r1693067 ]
QPID-6661: address some anomalies with heartbeats on the AMQP 1.0 path
* the ticker driving heartbeats are restarted whenever data is sent out
* the client checks whether there is data pending in determining whether it
can encode
> [AMQP 1.0] heartbeat anomalies
> ------------------------------
>
> Key: QPID-6661
> URL: https://issues.apache.org/jira/browse/QPID-6661
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker, C++ Client
> Affects Versions: qpid-cpp-0.34
> Reporter: Gordon Sim
> Assignee: Gordon Sim
> Priority: Minor
> Fix For: qpid-cpp-next
>
>
> The first heartbeat is often sent after the full idle period, whereas
> subsequent heartbeats are sent twice as frequently. This happens on both
> broker and client. This is a result of the periodic timer task that triggers
> the heartbeats being out of sync with the times computed by proton.
> Also on the client, occasionally a heartbeat is missed. This is in part due
> to the issue above, but also occasionally due to timing of incoming
> heartbeats with respect to the timer task, resulting in proton emitting the
> heartbeat but it not actually being written to the wire.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
