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

ASF GitHub Bot commented on DISPATCH-1579:
------------------------------------------

kgiusti commented on pull request #700: DISPATCH-1579: work-around for 
PROTON-2184
URL: https://github.com/apache/qpid-dispatch/pull/700
 
 
   
 
----------------------------------------------------------------
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:
us...@infra.apache.org


> Traffic hangs when multiple large messages are sent using different priorities
> ------------------------------------------------------------------------------
>
>                 Key: DISPATCH-1579
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1579
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Router Node
>    Affects Versions: 1.10.0
>            Reporter: Ken Giusti
>            Assignee: Ken Giusti
>            Priority: Blocker
>             Fix For: 1.11.0
>
>
> Create a two hop router network.  Attach a single receiver on one router.  
> Create 10 senders on the other router.  Each sender should sent a large 
> number of (unsettled) messages at a given priority (IOW 10 senders, one 
> sender sends priority 0 messages, another sends priority 1 messages, etc).
> If the messages are large enough to trigger Q3 eventually most (all?) of the 
> senders will hang stuck waiting for either settlement or deliveries to be 
> forwarded.   There is no recovery.
> I will post a reproducer soon.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to