You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ken Giusti (JIRA)" <ji...@apache.org> on 2011/02/07 17:06:31 UTC
[jira] Commented: (QPID-2935) Support "best effort" producer flow
control within the AMQP 0.10 implementation.
[ https://issues.apache.org/jira/browse/QPID-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991431#comment-12991431 ]
Ken Giusti commented on QPID-2935:
----------------------------------
As of 2/7/2011: Code functionally complete, and passing simple unit tests. The following TODO items still pending:
o) Performance regression testing & tuning.
o) Cleanup synchronous completion case in SessionState ~line 267
o) Sends completion on every execution.sync, else hangs. Can this be fixed?
o) Hang in clustered + async store tests. Need debug & fix.
o) Creates a request for IOProcessing on each completion - need to aggregate these.
o) Reviews pending for management changes.
o) Reviews pending for queue flow limit changes.
> Support "best effort" producer flow control within the AMQP 0.10 implementation.
> --------------------------------------------------------------------------------
>
> Key: QPID-2935
> URL: https://issues.apache.org/jira/browse/QPID-2935
> Project: Qpid
> Issue Type: New Feature
> Components: C++ Broker, C++ Client
> Affects Versions: 0.9
> Environment: any
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Fix For: 0.9
>
> Attachments: QPID-2935.tgz
>
>
> To what extent, if any, could producer flow control be supported on the existing (pre-1.0) protocol?
> In the current C++ broker/client implementation, when a queue on the broker fills to the point where it cannot accept any more messages (--default-queue-limit hit), the broker will forcibly disconnect any client that attempts to route a message to that queue. This is an abrupt failure - the producing client is not privy to the queue's remaining capacity. The broker provides no feedback to the producing client, which could be used to throttle the client's message production rate.
> The purpose of this JIRA is to explore the possible methods for implementing producer throttling on the current 0.10 C++ codebase.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org