[
https://issues.apache.org/jira/browse/DISPATCH-1533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Giusti resolved DISPATCH-1533.
----------------------------------
Resolution: Not A Bug
On closer examination this is not a bug in qdrouterd but actually in proton.
What is happening is when address-loader generates the 256th frame the "handle"
value in the sent attach frame goes from 255 to 256 which increases its encoded
length by 3 bytes [1 byte int -> 4 byte int]. This ends up pushing the entire
frame size over the router's default max-frame-size (16384)
The router is doing precisely the correct thing - shutting down a connection
from a client that is violating its max-frame-size.
Is this a bug in proton? Will kick it over there and see what happens.
> Connection drop if > 255 links per conn opened with address == 8133 bytes
> -------------------------------------------------------------------------
>
> Key: DISPATCH-1533
> URL: https://issues.apache.org/jira/browse/DISPATCH-1533
> Project: Qpid Dispatch
> Issue Type: Bug
> Components: Router Node
> Affects Versions: 1.9.0, 1.10.0
> Reporter: Ken Giusti
> Assignee: Ken Giusti
> Priority: Major
> Attachments: address-loader
>
>
> Using the attached reproducer attempting to create > 255 links on a single
> connection fails with
> AMQP:FRAME:0 <- @close(24) [error=@error(29)
> [condition=:"amqp:connection:framing-error", description="malformed frame"]]
> Run the reproducer:
> ./address-loader --verbose --conns 1 --links 1000 --length 8133
> Note this appears to be connection related rather than a route table
> limitation. It is possible to open many connections with 255 links:
> ./address-loader --verbose --conns 20 --links 255 --length 8133
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
