activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-892) Error decoding AMQP frame sent by Artemis
Date Fri, 16 Dec 2016 19:17:58 GMT


ASF subversion and git services commented on ARTEMIS-892:

Commit 6d022d035e2084e427be8157acc25d17d113d250 in activemq-artemis's branch refs/heads/1.x
from [~andytaylor]
[;h=6d022d0 ]

ARTEMIS-892 - add lock to tick method
(cherry picked from commit 198143edd082325801cbe8b1d8aa885a3ad47f35)

> Error decoding AMQP frame sent by Artemis
> -----------------------------------------
>                 Key: ARTEMIS-892
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP
>            Reporter: Ulf Lilleengen
>            Assignee: Andy Taylor
>             Fix For:, 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:
> Wireshark trace can be found here:
> An analysis of the  wireshark trace:

This message was sent by Atlassian JIRA

View raw message