You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2016/12/16 21:44:59 UTC
[jira] [Closed] (ARTEMIS-892) Error decoding AMQP frame sent by
Artemis
[ https://issues.apache.org/jira/browse/ARTEMIS-892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
clebert suconic closed ARTEMIS-892.
-----------------------------------
> Error decoding AMQP frame sent by Artemis
> -----------------------------------------
>
> Key: ARTEMIS-892
> URL: https://issues.apache.org/jira/browse/ARTEMIS-892
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Reporter: Ulf Lilleengen
> Assignee: Andy Taylor
> Fix For: 1.5.next, 2.0.0
>
>
> We're seeing an issue with bad frames being sent from Artemis in a setup where we have 1 router R
> connected to the broker B, and 1 sender/receiver pair C connected to the router.
> C <-> R <-> B
> The clients send and receive messages at a controlled rate of ~900 msgs/second. We are using Artemis snapshot from 15th of december.
> After running the test for a minute or two, the broker sends a frame that the router is unable to decode,
> producing the following message in the router log:
> [0x7f18a4190ae0]:Error decoding frame: PN_ARG_ERR (null)
> \x00S\x15\xc0\x11\x05Ap\x00\x01\x94.p\x00\x01\x94.\x00\x00\x00\x0c\x02
> A wireshark trace shows that the frame sent by the broker is corrupt. An analysis by [~gsim] explains
> this in more detail.
> A reproducer with instructions inside can be found here:
> http://people.redhat.com/~ulilleen/bugs/artemis_bad_frame/reproducer.tar.gz
> Wireshark trace can be found here:
> http://people.redhat.com/~ulilleen/bugs/artemis_bad_frame/wireshark_trace.pcapng
> An analysis of the wireshark trace:
> http://people.redhat.com/~ulilleen/bugs/artemis_bad_frame/gordon_analysis.txt
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)