qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DISPATCH-974) Getting connections via the router management protocol causes AMQP framing errors
Date Wed, 08 May 2019 16:28:00 GMT

    [ https://issues.apache.org/jira/browse/DISPATCH-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16835737#comment-16835737

ASF GitHub Bot commented on DISPATCH-974:

ganeshmurthy commented on pull request #503: DISPATCH-974 - Added code to qdstat and qdmanage
clients to repeatedl…
URL: https://github.com/apache/qpid-dispatch/pull/503
   …y get rows to overcome the limitations imposed by PROTON-1846
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Getting connections via the router management protocol causes AMQP framing errors
> ---------------------------------------------------------------------------------
>                 Key: DISPATCH-974
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-974
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Management Agent
>    Affects Versions: 1.0.1
>            Reporter: Marcel Meulemans
>            Assignee: Ganesh Murthy
>            Priority: Major
>         Attachments: qdrouter-frame-errors.pcapng.gz
> 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.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org

View raw message