[DISPATCH-974] Getting connections via the router management protocol causes AMQP framing errors

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.1
• Fix Version/s: 1.8.0
• Component/s: Management Agent
• Assignee: Ganesh Murthy
• Reporter: Marcel Meulemans
• Created: 23/Apr/18 12:12
• Updated: 11/Jun/19 19:36
• Resolved: 10/May/19 19:06

Description

I am running a standalone router with 5000 clients connected. When I try to get all connections via qdstat (qdstat --limit 5000 -c) something goes wrong (seems to be a framing error). The output from qdstat is:

 MessageException: [-10]: data error: (null)

The problems seems to somehow be related to result size because when I set the limit to less I get the list of connections as expected. In my situation the critical limit is 3447 (i.e. 3447 result in the expected list of connections, 3448 result in the error above). It does not seem to be frame size related because getting 3447 connection is already spread over transfer frames (256182, 256512 and 159399 bytes).

The error is not qdstat related because using some plain proton code to create a management query results in the same problem. Ultimately the call to pn_message_decode with data receive from the router fails (also wireshark can not decode the final frame).

I have attached a wireshark dump to the qdstat session with the router (qdrouter-frame-errors.pcapng.gz). The logs of the router (at info level) contain no further information.

 

Issue Links

• is caused by: PROTON-1846 [proton-c] Message decode fails with PN_OUT_OF_MEMORY if there are large lists in the message
• is duplicated by: DISPATCH-999 error querying large number of addresses with qdmanage
• links to: GitHub Pull Request #503