[PROTON-2214] Proton can generate an attach frame that violates the remotes max-frame-size

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: proton-c-0.30.0
• Fix Version/s: proton-c-future
• Component/s: proton-c
• Assignee: Unassigned
• Reporter: Ken Giusti
• Created: 08/May/20 18:11
• Updated: 08/May/20 18:12

Description

Not convinced this is actually a bug - more a user error - but wanted to raise the issue to understand what the expected behavior should be.

See DISPATCH-1533 for details and reproducer;

TL;DR: a chaos client written in Proton/python stresses the qdrouterd by creating links with very long target addresses. If the addresses are too long - resulting in a Attach performative that is larger than the remote's max-frame-size - proton generates and sends the oversized Attach frame regardless.

This could be considered a bug because according to the standard a client must not generate a frame > max-frame-size.

While the reaction of the peer is correct (close w/framing-error) the description is too vague given the actual error is specific (frame too large). It would've helped me debug this faster if description was that specific.

[0x614000035850]: AMQP:FRAME:0 <- @close(24) [error=@error(29) [condition=:"amqp:connection:framing-error", description="malformed frame"]]

Issue Links

• is related to: DISPATCH-1533 Connection drop if > 255 links per conn opened with address == 8133 bytes