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

ASF subversion and git services commented on DISPATCH-231:
----------------------------------------------------------

Commit ce66606fa25cf892f9f605aa2ad789488eefcbfe in qpid-dispatch's branch 
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-dispatch.git;h=ce66606 ]

DISPATCH-231 - Don't issue credit on targeted incoming links until there is at 
least one consumer for the target address.


> Router should not issue credit for unavailable targets
> ------------------------------------------------------
>
>                 Key: DISPATCH-231
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-231
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Router Node
>    Affects Versions: 0.5
>            Reporter: Ken Giusti
>            Assignee: Ted Ross
>             Fix For: 0.6
>
>
> When a client creates a sending link to a target, the router accepts the link 
> on behalf of the target, and issues credit.
> This happens even if the target is unknown (eg. no consumers exist).
> In this case, the client will send a bunch of messages that simply stall or 
> are released.
> As an alternative, the router should only issue credit if the target is 
> available. 
> Specifically:
> 1 - on attach, do not issue credit if the target is not available
> 2 - if the target goes away, stop issuing additional credit
> #2 can result in in-flight messages being left in limbo.  In this case, it is 
> acceptable to drop those messages that have been sent pre-settled, and 
> release those messages sent unsettled.  Ideally, the router would hold on to 
> these messages for a short time (TTL?) and re-send if the target becomes 
> available in that time.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to