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

Gordon Sim commented on DISPATCH-1517:
--------------------------------------

To see the issue, start a router, run the attached example against it, then run 
qdstat -l, then without killing that client, run qdstat -l and you should see 
something like this:

{noformat}
Router Links
  type      dir  conn id  id  peer  class   addr                  phs  cap  pri 
 undel  unsett  deliv  presett  psdrop  acc  rej  rel  mod  delay  rate
  
=======================================================================================================================================================
  endpoint  in   4        9         mobile  examples              0    250  0   
 0      0       1      0        0       1    0    9    0    0      0
  endpoint  in   5        11        mobile  $management           0    250  0   
 0      0       2      0        0       2    0    0    0    0      0
  endpoint  out  5        12        local   temp.47Tv1eHzUYpkSo8       250  0   
 0      0       1      1        0       0    0    0    0    0      0
{noformat}

There were 10 deliveries sent on the sender of which 1 was accepted and 9 were 
released. The acc and rel columns are correct, but the deliv column is only 
counting the accepted delivery.

> delivery count is not incremented for undeliverable messages
> ------------------------------------------------------------
>
>                 Key: DISPATCH-1517
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-1517
>             Project: Qpid Dispatch
>          Issue Type: Improvement
>            Reporter: Gordon Sim
>            Priority: Major
>         Attachments: dispatch-1517.py
>
>




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