qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ken Giusti (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Closed: (QPID-2841) QMF: set TTL on agent heartbeat messages
Date Wed, 01 Sep 2010 19:28:53 GMT

     [ https://issues.apache.org/jira/browse/QPID-2841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Ken Giusti closed QPID-2841.

    Resolution: Fixed

Set the TTL value in agent heartbeat messages to 2 times the agent heartbeat interval.  That
should be enough to guarantee that at least one valid heartbeat remains available at all times.

> QMF: set TTL on agent heartbeat messages
> ----------------------------------------
>                 Key: QPID-2841
>                 URL: https://issues.apache.org/jira/browse/QPID-2841
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Qpid Managment Framework
>         Environment: all
>            Reporter: Ken Giusti
>            Assignee: Ken Giusti
> Heartbeats are issued periodically by QMF agents.  Each heartbeat is stateless - there
is no information loss if a heartbeat is dropped or ignored by the client.   While performance
testing, it was discovered that multiple heartbeats will queue up should a console be unable
to consume them fast enough.  Most of these heartbeats are stale: the agent has issue a new
heartbeat(s) since the older heartbeat was queued.  Processing these "stale" heartbeats is
> By setting the TTL in heartbeat messages, stale heartbeats will be discarded by the broker
instead of being sent to the console.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message