Charles E. Rolke created DISPATCH-1522:
------------------------------------------
Summary: Aborted sender transfer closes receiver connection with
framing error
Key: DISPATCH-1522
URL: https://issues.apache.org/jira/browse/DISPATCH-1522
Project: Qpid Dispatch
Issue Type: Bug
Components: Router Node
Affects Versions: 1.9.0
Environment: Fedora 29, proton master @8c6d4 and dispatch master 2417e.
Reporter: Charles E. Rolke
Start a single router with a normal listener. Run a proton cpp simple_receiver
to receive on an address at that listener. Run proton c/examples/send-abort to
send to that address on the same listener.
The router forwards the abort and then immediately closes the connection with a
framing error.
This same behavior happens through a network of routers. The abort is
propagated properly through the router network but then the connection between
the final receiver and its attached router gets closed.
These are preliminary findings before proper blame between qpid-dispatch and
qpid-proton has been assessed.
In the one router case peer_4 is the receiver and peer_5 is the sender. Scraper
shows :
{noformat}
◊ 2019-12-11 17:12:30.331080 A0#2672 INTC [A0_6] -> [] peer_5 attach [0,0]
receiver my_sender (source: none, target: "examples", class: client)
◊ 2019-12-11 17:12:30.331216 A0#2673 INTC [A0_6] -> [] peer_5 flow [0,0]
(0,250)
◊ 2019-12-11 17:12:30.344997 A0#2674 INTC [A0_6] <- [] peer_5 transfer [0,0]
(0) more transfer_62 - 16350 bytes (pending)
◊ 2019-12-11 17:12:30.346441 A0#2687 INTC [A0_5] -> [] peer_4 transfer [0,0]
(0) more transfer_62 - 15872 bytes (pending)
◊ 2019-12-11 17:12:30.349521 A0#2689 INTC [A0_6] <- [] peer_5 transfer [0,0]
(0) more transfer_63 - 16350 bytes (pending)
◊ 2019-12-11 17:12:30.349965 A0#2695 INTC [A0_5] -> [] peer_4 transfer [0,0]
(0) more transfer_63 - 16384 bytes (pending)
◊ 2019-12-11 17:12:30.352966 A0#2697 INTC [A0_6] <- [] peer_5 transfer [0,0]
(0) more transfer_63 - 16350 bytes (pending)
◊ 2019-12-11 17:12:30.353264 A0#2703 INTC [A0_5] -> [] peer_4 transfer [0,0]
(0) more transfer_63 - 16384 bytes (pending)
◊ 2019-12-11 17:12:30.355887 A0#2705 INTC [A0_6] <- [] peer_5 transfer [0,0]
(0) more transfer_63 - 16350 bytes (pending)
◊ 2019-12-11 17:12:30.356269 A0#2711 INTC [A0_5] -> [] peer_4 transfer [0,0]
(0) more transfer_63 - 16384 bytes (pending)
◊ 2019-12-11 17:12:30.359045 A0#2713 INTC [A0_6] <- [] peer_5 transfer [0,0]
(0) more transfer_63 - 13626 bytes (pending)
◊ 2019-12-11 17:12:30.359090 A0#2714 INTC [A0_6] <- [] peer_5 transfer [0,0]
(0) settled aborted - 0 bytes transfer presettled
◊ 2019-12-11 17:12:30.359489 A0#2734 INTC [A0_6] -> [] peer_5 flow [0,0]
(1,250)
◊ 2019-12-11 17:12:30.359524 A0#2735 INTC [A0_5] -> [] peer_4 transfer [0,0]
(0) settled aborted - 0 bytes transfer presettled
◊ 2019-12-11 17:12:30.360812 A0#2739 INTC [A0_5] -> [] peer_4 close [0] error
:"amqp:connection:framing-error" "connection aborted"
◊ 2019-12-11 17:12:30.360850 A0#2740 INTC [A0_5] <- [] peer_4 EOS
◊ 2019-12-11 17:12:30.360870 A0#2741 INTC [A0_5] [] peer_4 Connection from
192.168.1.17:46324 (to 0.0.0.0:21015) failed: amqp:connection:framing-error
connection aborted
◊ 2019-12-11 17:12:30.360932 A0#2742 INTC [A0_5] -> [] peer_4 EOS
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
