[
https://issues.apache.org/jira/browse/DISPATCH-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles E. Rolke updated DISPATCH-1731:
---------------------------------------
Description:
A test network has 12 routers (
https://issues.apache.org/jira/secure/attachment/12985276/edge2-apr5-network-diagram.pdf
), four interior routers connected in a line, each with two edge routers.
A test runs sending unsettled multicast messages to EA2 and ED1, and receiving
them on INTA, EB1, and ED2. On top of that routers EC1 and EC2 have
intermittent receivers that continuously (connect, receive between 1 and 5
messages, disconnect). See attached png file.
The issue is that routers EC1 and EC2 show every message sent over link 14 as
_delayed_.
{code:java}
chug@unused 29jul20> qdstat -b $EC1_normal -l
2020-07-29 19:16:13.409662 UTC
EC1
Router Links
type dir conn id id peer class addr phs cap
pri undel unsett deliv presett psdrop acc rej rel mod delay rate
stuck cred blkd
==================================================================================================================================================================================
endpoint out 1 9 local _edge 250
0 0 0 30194 30194 0 0 0 0 0 0 2
0 250 -
endpoint in 1 10 250
0 0 0 30194 0 0 30194 0 0 0 0 2
0 250 -
endpoint in 1 11 250
0 0 0 0 0 0 0 0 0 0 0 0
0 32 -
endpoint out 1 12 250
0 0 0 0 0 0 0 0 0 0 0 0
0 250 -
endpoint in 1 13 250
0 0 0 0 0 0 0 0 0 0 0 0
0 100 -
endpoint out 1 14 250
0 0 0 487940 487940 0 0 0 0 0 487940 31
0 32 -
endpoint in 1 15 250
0 0 0 487940 487940 0 0 0 0 0 0 31
0 250 -
endpoint in 1 975893 250
0 0 0 31 0 0 0 0 0 0 0 0
0 250 -
endpoint in 487941 975894 mobile $management 0 250
0 0 0 2 0 0 2 0 0 0 0 0
0 250 -
endpoint out 487941 975895 local temp.TEqKGJ7xXF1yjpY 250
0 0 0 1 1 0 0 0 0 0 0 0
0 1 -
{code}
The attached interior router INTC looks like it is receiving the messages ok
{code:java}
type dir conn id id peer class addr
phs cap pri undel unsett deliv presett psdrop acc rej rel
mod delay rate stuck cred blkd
==================================================================================================================================================================================================
endpoint in 1 14 mobile _$qd.addr_lookup
0 250 0 0 0 496964 496964 0 0 0 0
0 0 32 0 32 -
{code}
Note that edge addr lookups are happening at the rate of 5 to 10 lookups per
second as the test receivers connect and reconnect as fast as they can.
was:
A test network has 12 routers ( [^edge2-apr5-network-diagram.pdf] ), four
interior routers connected in a line, each with two edge routers.
A test runs sending unsettled multicast messages to EA2 and ED1, and receiving
them on INTA, EB1, and ED2. On top of that routers EC1 and EC2 have
intermittent receivers that continuously (connect, receive between 1 and 5
messages, disconnect). See attached png file.
The issue is that routers EC1 and EC2 show every message sent over link 14 as
_delayed_.
{code:java}
chug@unused 29jul20> qdstat -b $EC1_normal -l
2020-07-29 19:16:13.409662 UTC
EC1
Router Links
type dir conn id id peer class addr phs cap
pri undel unsett deliv presett psdrop acc rej rel mod delay rate
stuck cred blkd
==================================================================================================================================================================================
endpoint out 1 9 local _edge 250
0 0 0 30194 30194 0 0 0 0 0 0 2
0 250 -
endpoint in 1 10 250
0 0 0 30194 0 0 30194 0 0 0 0 2
0 250 -
endpoint in 1 11 250
0 0 0 0 0 0 0 0 0 0 0 0
0 32 -
endpoint out 1 12 250
0 0 0 0 0 0 0 0 0 0 0 0
0 250 -
endpoint in 1 13 250
0 0 0 0 0 0 0 0 0 0 0 0
0 100 -
endpoint out 1 14 250
0 0 0 487940 487940 0 0 0 0 0 487940 31
0 32 -
endpoint in 1 15 250
0 0 0 487940 487940 0 0 0 0 0 0 31
0 250 -
endpoint in 1 975893 250
0 0 0 31 0 0 0 0 0 0 0 0
0 250 -
endpoint in 487941 975894 mobile $management 0 250
0 0 0 2 0 0 2 0 0 0 0 0
0 250 -
endpoint out 487941 975895 local temp.TEqKGJ7xXF1yjpY 250
0 0 0 1 1 0 0 0 0 0 0 0
0 1 -
{code}
The attached interior router INTC looks like it is receiving the messages ok
{code:java}
type dir conn id id peer class addr
phs cap pri undel unsett deliv presett psdrop acc rej rel
mod delay rate stuck cred blkd
==================================================================================================================================================================================================
endpoint in 1 14 mobile _$qd.addr_lookup
0 250 0 0 0 496964 496964 0 0 0 0
0 0 32 0 32 -
{code}
Note that edge addr lookups are happening at the rate of 5 to 10 lookups per
second as the test receivers connect and reconnect as fast as they can.
> Edge router counts all addr_lookup messages as delayed
> ------------------------------------------------------
>
> Key: DISPATCH-1731
> URL: https://issues.apache.org/jira/browse/DISPATCH-1731
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Routing Engine
> Affects Versions: 1.12.0
> Reporter: Charles E. Rolke
> Priority: Major
> Attachments: DISPATCH-1731-console-picture.png
>
>
> A test network has 12 routers (
> https://issues.apache.org/jira/secure/attachment/12985276/edge2-apr5-network-diagram.pdf
> ), four interior routers connected in a line, each with two edge routers.
> A test runs sending unsettled multicast messages to EA2 and ED1, and
> receiving them on INTA, EB1, and ED2. On top of that routers EC1 and EC2 have
> intermittent receivers that continuously (connect, receive between 1 and 5
> messages, disconnect). See attached png file.
> The issue is that routers EC1 and EC2 show every message sent over link 14 as
> _delayed_.
> {code:java}
> chug@unused 29jul20> qdstat -b $EC1_normal -l
> 2020-07-29 19:16:13.409662 UTC
> EC1
> Router Links
> type dir conn id id peer class addr phs
> cap pri undel unsett deliv presett psdrop acc rej rel mod delay
> rate stuck cred blkd
>
> ==================================================================================================================================================================================
> endpoint out 1 9 local _edge
> 250 0 0 0 30194 30194 0 0 0 0 0 0
> 2 0 250 -
> endpoint in 1 10
> 250 0 0 0 30194 0 0 30194 0 0 0 0
> 2 0 250 -
> endpoint in 1 11
> 250 0 0 0 0 0 0 0 0 0 0 0
> 0 0 32 -
> endpoint out 1 12
> 250 0 0 0 0 0 0 0 0 0 0 0
> 0 0 250 -
> endpoint in 1 13
> 250 0 0 0 0 0 0 0 0 0 0 0
> 0 0 100 -
> endpoint out 1 14
> 250 0 0 0 487940 487940 0 0 0 0 0
> 487940 31 0 32 -
> endpoint in 1 15
> 250 0 0 0 487940 487940 0 0 0 0 0 0
> 31 0 250 -
> endpoint in 1 975893
> 250 0 0 0 31 0 0 0 0 0 0 0
> 0 0 250 -
> endpoint in 487941 975894 mobile $management 0
> 250 0 0 0 2 0 0 2 0 0 0 0
> 0 0 250 -
> endpoint out 487941 975895 local temp.TEqKGJ7xXF1yjpY
> 250 0 0 0 1 1 0 0 0 0 0 0
> 0 0 1 -
> {code}
> The attached interior router INTC looks like it is receiving the messages ok
> {code:java}
> type dir conn id id peer class addr
> phs cap pri undel unsett deliv presett psdrop acc rej rel
> mod delay rate stuck cred blkd
>
> ==================================================================================================================================================================================================
> endpoint in 1 14 mobile _$qd.addr_lookup
> 0 250 0 0 0 496964 496964 0 0 0 0
> 0 0 32 0 32 -
> {code}
> Note that edge addr lookups are happening at the rate of 5 to 10 lookups per
> second as the test receivers connect and reconnect as fast as they can.
--
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
