You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/10/29 23:25:33 UTC
[jira] [Commented] (QPID-5538) [amqp1.0] Qpidd does not generate
keep-alive frames for peers using idle timeout.
[ https://issues.apache.org/jira/browse/QPID-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14189137#comment-14189137 ]
ASF subversion and git services commented on QPID-5538:
-------------------------------------------------------
Commit 1635316 from [~gsim] in branch 'qpid/trunk'
[ https://svn.apache.org/r1635316 ]
QPID-5538: simple heartbeat enablement over 1.0 for broker
> [amqp1.0] Qpidd does not generate keep-alive frames for peers using idle timeout.
> ---------------------------------------------------------------------------------
>
> Key: QPID-5538
> URL: https://issues.apache.org/jira/browse/QPID-5538
> Project: Qpid
> Issue Type: Bug
> Components: C++ Broker
> Affects Versions: 0.26
> Reporter: Ken Giusti
> Assignee: Gordon Sim
> Fix For: Future
>
>
> When establishing an AMQP 1.0 connection, an endpoint may elect to use an idle link timeout. This timeout is advertised to the peer in the Open frame.
> The recipient of the advertised timeout should either:
> 1) Close the connection if the idle timeout cannot be honored, or
> 2) guarantee it will generate traffic frequently enough to prevent the peer from timing out simply because there is no data to transfer.
> Currently, qpidd does neither - it simply ignores the timeout. This will cause the peer to incorrectly drop the link should no data become available on the broker within the advertised idle time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org