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

ASF subversion and git services commented on QPID-8451:
-------------------------------------------------------

Commit 3a74fc4976c3e49c4841c8dce76924b59033e294 in qpid-broker-j's branch 
refs/heads/master from Alex Rudyy
[ https://gitbox.apache.org/repos/asf?p=qpid-broker-j.git;h=3a74fc4 ]

QPID-8451:[Broker-J] Block session before adding it into blocked sesssion set

This should eliminate the possibility of leaving session in blocked state
when a consumer thread unblock the blocked sessions and remove them from the 
blocked session set


> [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