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] (AMQ-6142) ActiveMQBytesMessage decompress throws DataFormatException incorrect header check
Date Mon, 01 Feb 2016 17:38:39 GMT


ASF subversion and git services commented on AMQ-6142:

Commit aaa2fdd5418098b98595f9f85be8248da32aff7b in activemq's branch refs/heads/activemq-5.13.x
from [~cshannon]
[;h=aaa2fdd ]

Fixing a race condition that exists in the decompress method of
ActiveMQBytesMessage that can cause an invalid length to be read.

(cherry picked from commit 5f7a81f9280fb65b8a3c1f85c4570a18d87fafd9)

> ActiveMQBytesMessage decompress throws DataFormatException incorrect header check
> ---------------------------------------------------------------------------------
>                 Key: AMQ-6142
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.10.2, 5.12.1, 5.11.3, 5.13.0
>            Reporter: Claudio Tagliola
>            Assignee: Christopher L. Shannon
>         Attachments:,,, pom.xml
> In our environment we use an embedded broker. On one topic where compression is enabled,
the server is also listening in on the messages. From ActiveMQ 5.10.0 up to 5.13.0, we encounter
DataFormatException: incorrect header check exceptions on the tcp clients due to corruption
of the payload. Attached are a test server and client. At some point, the client will exit
due to mentioned exception. Increase chances by running multiple clients. This scenario works
with 5.8.0 and 5.9.1.
> If the server has multiple consumers on the same topic, they will encounter corruption
as well, but this has other side-effects.

This message was sent by Atlassian JIRA

View raw message