[jira] [Commented] (DISPATCH-1772) Fallback destination test prints insufficient data when it fails
[
https://issues.apache.org/jira/browse/DISPATCH-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200379#comment-17200379
]
Charles E. Rolke commented on DISPATCH-1772:
Adding some logging to the SwitchoverMix test and running it enough times leads
to this instance of failure;
Time of day is just in seconds.
Test 35. Sender: INT.A, Primary receiver: INT.B, Fallback receiver: EA1
Test agent is named "peer_5".
{code:java}
Time(S) What
---
00.3450 sender link open
00.3470 rx link open
00.3480 rx link open
--- sender sends, all messages accepted
00.7241 B0_11 all accepted, detach (closes one minute later after TMO)
--- release storm as A sends to B ---
01.2191 A -> B add MFdest.35 (this seem way late)
01.2522 B <- A add MFdest.35
01.3446 B -> A del M0dest.35
01.3473 A <- B del M0 dest.35
01.4448 A -> peer_5 FLOW with drain
peer_5 sends 95 messages that consumes all the available credit
peer_5 never sends a FLOW with drain set.
{code}
There are a couple of odd things in the logs.
1. By the time that A notifies B of the fallback destination mobile address,
the sender has already sent all of the Phase 0 messages.
2. The drain cycle is satisfied by having the sender send the full amount of
credit's worth of transfers. Peer_5 never sends a FLOW with drain set back to
INT.A.
> Fallback destination test prints insufficient data when it fails
>
>
> Key: DISPATCH-1772
> URL: https://issues.apache.org/jira/browse/DISPATCH-1772
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Tests
>Affects Versions: 1.13.0
>Reporter: Charles E. Rolke
>Assignee: Charles E. Rolke
>Priority: Major
>
> Occasionally the Switchover_mix test fails in CI. When this happens then the
> self test prints only a single line describing the failure such as:
> {code:java}
> "63:
> ==",
> "63: FAIL: test_35_switchover_mix_1
> (system_tests_fallback_dest.RouterTest)",
> "63:
> --",
> "63: Traceback (most recent call last):",
> "63: File
> \"/opt/qpid-dispatch-src/tests/system_tests_fallback_dest.py\", line 353, in
> test_35_switchover_mix_1",
> "63: self.assertEqual(None, test.error)",
> "63: AssertionError: None != u'Timeout Expired - n_tx=0, n_rx=0,
> n_rel=1046, phase=1, local_rel=0'",
> "63: ",
> "63:
> --",
> {code}
> This error message says that (phase=1) all the messages were sent
> successfully before the switchover was initiated. Then 1046 messages were
> released by the locally connected router until the test timed out.
> Class system_test/Logger could be used to generate a much more detailed
> narrative describing how the client test event stream played out. Further,
> the Logger log marks the client events with microsecond resolution so that
> when possible the log can be correlated with qdrouterd logs.
--
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
[jira] [Commented] (DISPATCH-1777) inter-router transfer of streaming message representing tcp connection is not delivered
[
https://issues.apache.org/jira/browse/DISPATCH-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200334#comment-17200334
]
Gordon Sim commented on DISPATCH-1777:
--
To reproduce, setup a pair of routers, one with a tcp listener, one with a tcp
connector. Have some service running that the tcp connector is configured to
connect to. Then try and use that service via the port the tcp listener is
listening on.
E.g. router 1 config:
{noformat}
router {
id: router-a
mode: interior
}
listener {
host: 0.0.0.0
port: amqp
authenticatePeer: no
saslMechanisms: ANONYMOUS
}
listener {
host: 0.0.0.0
port: 55672
role: inter-router
authenticatePeer: no
saslMechanisms: ANONYMOUS
}
tcpConnector {
host: 127.0.0.1
port: 9090
address: foo
siteId: bar
}
log {
module: TCP_ADAPTOR
enable: trace+
}
{noformat}
router 2 config:
{noformat}
router {
id: router-b
mode: interior
}
listener {
host: 0.0.0.0
port: 5673
authenticatePeer: no
saslMechanisms: ANONYMOUS
}
connector {
host: 0.0.0.0
port: 55672
role: inter-router
}
tcpListener {
host: 0.0.0.0
port: 9191
address: foo
siteId: bar
}
log {
module: TCP_ADAPTOR
enable: trace+
}
{noformat}
For a service I used simple echo service, e.g. {{podman run -it -p9090:9090
quay.io/skupper/tcp-echo}} (or docker if you don't use podman), then {{telnet
localhost 9191}} and type data to be echoed.
> inter-router transfer of streaming message representing tcp connection is not
> delivered
> ---
>
> Key: DISPATCH-1777
> URL: https://issues.apache.org/jira/browse/DISPATCH-1777
> Project: Qpid Dispatch
> Issue Type: Sub-task
>Reporter: Gordon Sim
>Priority: Major
>
> The message for a tcp connections gets correctly router to an inter-router
> link, but that link seems not to be able to transfer it. It remains in the
> undelivered state.
> {noformat}
> $ qdstat -l -r router-b
> 2020-09-18 09:56:27.754348 UTC
> router-b
> Router Links
> typedir conn id id peer class addr phs
> cap pri undel unsett deliv presett psdrop acc rej rel mod delay
> rate stuck cred blkd
>
>
> router-control in 11
> 250 00 0 746746 0 00000 1
> 0 250 -
> router-control out 12 local qdhello
> 250 00 0 744744 0 00000 0
> 0 250 -
> inter-routerin 13
> 250 00 0 0 00 00000 0
> 0 250 -
> inter-routerout 14
> 250 00 0 0 00 00000 0
> 0 250 -
> inter-routerin 15
> 250 00 0 0 00 00000 0
> 0 250 -
> inter-routerout 16
> 250 10 0 0 00 00000 0
> 0 250 -
> inter-routerin 17
> 250 00 0 0 00 00000 0
> 0 250 -
> inter-routerout 18
> 250 20 0 0 00 00000 0
> 0 250 -
> inter-routerin 19
> 250 00 0 0 00 00000 0
> 0 250 -
> inter-routerout 110
> 250 30 0 0 00 00000 0
> 0 250 -
> inter-routerin 111
> 250 00 0 5 00 50000 0
> 0 250 -
> inter-routerout 112
> 250 40 0 4 40 00000 0
> 0 250 -
> inter-routerin 113
> 250 00 0 0 00 00000 0
> 0 25
[jira] [Updated] (DISPATCH-1655) http2 protocol bridging (ingress and egress)
[ https://issues.apache.org/jira/browse/DISPATCH-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated DISPATCH-1655: - Sprint: (was: Multi-Protocol Support) > http2 protocol bridging (ingress and egress) > > > Key: DISPATCH-1655 > URL: https://issues.apache.org/jira/browse/DISPATCH-1655 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Gordon Sim >Priority: Major > -- 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
[jira] [Assigned] (DISPATCH-1779) http stats/metrics
[ https://issues.apache.org/jira/browse/DISPATCH-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned DISPATCH-1779: Assignee: Gordon Sim > http stats/metrics > -- > > Key: DISPATCH-1779 > URL: https://issues.apache.org/jira/browse/DISPATCH-1779 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Gordon Sim >Assignee: Gordon Sim >Priority: Major > Fix For: 1.15.0 > > -- 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
[jira] [Updated] (DISPATCH-1744) Add HTTP/1.1 support to the router
[ https://issues.apache.org/jira/browse/DISPATCH-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated DISPATCH-1744: - Sprint: Multi-Protocol Support > Add HTTP/1.1 support to the router > -- > > Key: DISPATCH-1744 > URL: https://issues.apache.org/jira/browse/DISPATCH-1744 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Container >Reporter: Ganesh Murthy >Assignee: Ken Giusti >Priority: Major > > Add new feature to support HTTP/1.1 protocol on the router. > This feature involves the introduction of new entities to the router called > httpListener and httpConnector. The httpListener will accept HTTP/1.1 > connections and make an outbound connection using the httpConnector. > The router will use AMQP to route the messages. The router will act as a > protocol bridge. -- 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
[jira] [Updated] (DISPATCH-1780) multicast support for http 1.1 adaptor
[ https://issues.apache.org/jira/browse/DISPATCH-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated DISPATCH-1780: - Sprint: Multi-Protocol Support > multicast support for http 1.1 adaptor > -- > > Key: DISPATCH-1780 > URL: https://issues.apache.org/jira/browse/DISPATCH-1780 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Gordon Sim >Priority: Major > Fix For: 1.15.0 > > -- 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
[jira] [Updated] (DISPATCH-1743) Add HTTP/2 support to the router
[ https://issues.apache.org/jira/browse/DISPATCH-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated DISPATCH-1743: - Sprint: Multi-Protocol Support > Add HTTP/2 support to the router > > > Key: DISPATCH-1743 > URL: https://issues.apache.org/jira/browse/DISPATCH-1743 > Project: Qpid Dispatch > Issue Type: New Feature > Components: Container >Reporter: Ganesh Murthy >Assignee: Ganesh Murthy >Priority: Major > > Add new feature to support HTTP/2 protocol on the router. > This feature involves the introduction of new entities to the router called > httpListener and httpConnector. The httpListener will accept HTTP/2 > connections and make an outbound connection using the httpConnector. > The router will use AMQP to route the messages. The router will act as a > protocol bridge. -- 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
[jira] [Updated] (DISPATCH-1779) http stats/metrics
[ https://issues.apache.org/jira/browse/DISPATCH-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated DISPATCH-1779: - Sprint: Multi-Protocol Support > http stats/metrics > -- > > Key: DISPATCH-1779 > URL: https://issues.apache.org/jira/browse/DISPATCH-1779 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Gordon Sim >Priority: Major > Fix For: 1.15.0 > > -- 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
[jira] [Closed] (DISPATCH-1655) http2 protocol bridging (ingress and egress)
[ https://issues.apache.org/jira/browse/DISPATCH-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim closed DISPATCH-1655. Resolution: Duplicate > http2 protocol bridging (ingress and egress) > > > Key: DISPATCH-1655 > URL: https://issues.apache.org/jira/browse/DISPATCH-1655 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Gordon Sim >Priority: Major > -- 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
[jira] [Updated] (DISPATCH-1654) tcp protocol bridging (ingress and egress)
[ https://issues.apache.org/jira/browse/DISPATCH-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated DISPATCH-1654: - Sprint: Extended Sprint 1 > tcp protocol bridging (ingress and egress) > -- > > Key: DISPATCH-1654 > URL: https://issues.apache.org/jira/browse/DISPATCH-1654 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Gordon Sim >Assignee: Gordon Sim >Priority: Major > Fix For: 1.15.0 > > -- 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
[jira] [Updated] (DISPATCH-1655) http2 protocol bridging (ingress and egress)
[ https://issues.apache.org/jira/browse/DISPATCH-1655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated DISPATCH-1655: - Sprint: Extended Sprint 1 > http2 protocol bridging (ingress and egress) > > > Key: DISPATCH-1655 > URL: https://issues.apache.org/jira/browse/DISPATCH-1655 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Gordon Sim >Priority: Major > -- 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
[jira] [Updated] (DISPATCH-1780) multicast support for http 1.1 adaptor
[ https://issues.apache.org/jira/browse/DISPATCH-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated DISPATCH-1780: - Fix Version/s: 1.15.0 > multicast support for http 1.1 adaptor > -- > > Key: DISPATCH-1780 > URL: https://issues.apache.org/jira/browse/DISPATCH-1780 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Gordon Sim >Priority: Major > Fix For: 1.15.0 > > -- 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
[jira] [Created] (DISPATCH-1780) multicast support for http 1.1 adaptor
Gordon Sim created DISPATCH-1780: Summary: multicast support for http 1.1 adaptor Key: DISPATCH-1780 URL: https://issues.apache.org/jira/browse/DISPATCH-1780 Project: Qpid Dispatch Issue Type: Improvement Reporter: Gordon Sim -- 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
[jira] [Created] (DISPATCH-1779) http stats/metrics
Gordon Sim created DISPATCH-1779: Summary: http stats/metrics Key: DISPATCH-1779 URL: https://issues.apache.org/jira/browse/DISPATCH-1779 Project: Qpid Dispatch Issue Type: Improvement Reporter: Gordon Sim Fix For: 1.15.0 -- 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
[jira] [Updated] (DISPATCH-1654) tcp protocol bridging (ingress and egress)
[ https://issues.apache.org/jira/browse/DISPATCH-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim updated DISPATCH-1654: - Fix Version/s: 1.15.0 > tcp protocol bridging (ingress and egress) > -- > > Key: DISPATCH-1654 > URL: https://issues.apache.org/jira/browse/DISPATCH-1654 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Gordon Sim >Assignee: Gordon Sim >Priority: Major > Fix For: 1.15.0 > > -- 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
[jira] [Assigned] (DISPATCH-1654) tcp protocol bridging (ingress and egress)
[ https://issues.apache.org/jira/browse/DISPATCH-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reassigned DISPATCH-1654: Assignee: Gordon Sim > tcp protocol bridging (ingress and egress) > -- > > Key: DISPATCH-1654 > URL: https://issues.apache.org/jira/browse/DISPATCH-1654 > Project: Qpid Dispatch > Issue Type: Improvement >Reporter: Gordon Sim >Assignee: Gordon Sim >Priority: Major > -- 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
[jira] [Resolved] (PROTON-2234) [proton-c] Need ability to add an authorization id in the SASL exchange
[ https://issues.apache.org/jira/browse/PROTON-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Stitcher resolved PROTON-2234. - Fix Version/s: proton-c-0.33.0 Resolution: Fixed > [proton-c] Need ability to add an authorization id in the SASL exchange > --- > > Key: PROTON-2234 > URL: https://issues.apache.org/jira/browse/PROTON-2234 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Affects Versions: proton-c-0.31.0 >Reporter: Ganesh Murthy >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.33.0 > > > The Qpid Dispatch router is capable of delegating SASL authentication to an > external auth service. > We need a way > (1) for a server to get the authzid for a sasl external request - The > "server" in this case the router, needs a way to obtain the authzid if the > client has specified one during the SASL exchange > (2) for a client to specify the authzid to send with an external request - > the "client" in this case the router acts as a client to the auth service and > it needs a way to specify/send the authzid to the auth service as part of the > SASL exchange. > [https://tools.ietf.org/html/rfc4422#page-29] (section A.2) -- 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
