qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DISPATCH-341) router did not respond to request to drain a message-routed consumers link credit
Date Fri, 20 May 2016 17:03:13 GMT

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

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

GitHub user ganeshmurthy opened a pull request:

    https://github.com/apache/qpid-dispatch/pull/76

    DISPATCH-341 - Added drain support for message routes and link routes

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ganeshmurthy/qpid-dispatch DISPATCH-341

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/qpid-dispatch/pull/76.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #76
    
----
commit bdd8462c2ee4040123584d1ca876cd4e95dd14d0
Author: Ganesh Murthy <gmurthy@redhat.com>
Date:   2016-05-20T16:59:48Z

    DISPATCH-341 - Added drain support for message routes and link routes

----


> router did not respond to request to drain a message-routed consumers link credit
> ---------------------------------------------------------------------------------
>
>                 Key: DISPATCH-341
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-341
>             Project: Qpid Dispatch
>          Issue Type: Bug
>    Affects Versions: 0.6.0
>         Environment: Qpid Dispatch 0.6.0 RC3
> Qpid JMS 0.10.0-SNAPSHOT
>            Reporter: Robbie Gemmell
>            Assignee: Ganesh Murthy
>
> With a router using the provided default config (updated only to set saslMechanisms to
ANONYMOUS), and attaching a sender and receiver (using the JMS client Sender and Receiver
examples) to the address "queue" (so presumably using messge routing), it could be seen that
Dispatch didn't respond to requests to drain the receivers link.
> In one case, after receiving some messages, a 'drain requst' flow is issued, but neither
enough messages to use the credit (expected since no more were sent) or a 'drain reponse'
flow are received, just heartbeating back and forth.
> {noformat}
> [1925974223:1] -> Disposition{role=RECEIVER, first=8, last=8, settled=true, state=Accepted{},
batchable=false}
> [1925974223:1] -> Flow{nextIncomingId=9, incomingWindow=2047, nextOutgoingId=1, outgoingWindow=2147483647,
handle=0, deliveryCount=9, linkCredit=991, available=null, drain=true, echo=false, properties=null}
> [1925974223:0] -> Empty Frame
> [1925974223:0] -> Empty Frame
> [1925974223:0] <- Empty Frame
> {noformat}
> In another case, after flowing some credit but not receiving any messages, a 'drain request'
is issued, but neither enough messages to use the credit (expected since none were sent) or
a 'drain reponse' flow are received, just heartbeating back and forth.
> {noformat}
> [2111953084:1] -> Flow{nextIncomingId=0, incomingWindow=2047, nextOutgoingId=1, outgoingWindow=2147483647,
handle=0, deliveryCount=0, linkCredit=1000, available=null, drain=false, echo=false, properties=null}
> [2111953084:1] -> Flow{nextIncomingId=0, incomingWindow=2047, nextOutgoingId=1, outgoingWindow=2147483647,
handle=0, deliveryCount=0, linkCredit=1000, available=null, drain=true, echo=false, properties=null}
> [2111953084:0] -> Empty Frame
> [2111953084:0] -> Empty Frame
> [2111953084:0] <- Empty Frame
> {noformat}



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

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


Mime
View raw message