[ 
https://issues.apache.org/jira/browse/QPID-8451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193226#comment-17193226
 ] 

ASF GitHub Bot commented on QPID-8451:
--------------------------------------

alex-rufous commented on pull request #58:
URL: https://github.com/apache/qpid-broker-j/pull/58#issuecomment-689859917


   The changes look reasonable to me. I will merge them shortly


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


> [Broker-J][AMQP 1.0] Queues with enforced producer flow control should not 
> allow to produce messages on sender links created on new connections
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-8451
>                 URL: https://issues.apache.org/jira/browse/QPID-8451
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Broker-J
>    Affects Versions: qpid-java-broker-8.0.0
>            Reporter: Alex Rudyy
>            Priority: Major
>             Fix For: qpid-java-broker-8.0.1
>
>
> The existing producer flow control functionality only blocks existing sender 
> links and new sender links created on the same connection(within existing or 
> new session). It does not block senders created on new connections. As 
> result, such senders can populate queue with messages (especially for use 
> cases when each message is published per new connection). The queue with 
> blocked flow should not give credits to senders created on new connections.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to