activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher L. Shannon (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (AMQ-6142) ActiveMQBytesMessage decompress throws DataFormatException incorrect header check
Date Mon, 01 Feb 2016 17:16:39 GMT

     [ https://issues.apache.org/jira/browse/AMQ-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christopher L. Shannon reassigned AMQ-6142:
-------------------------------------------

    Assignee: Christopher L. Shannon

> ActiveMQBytesMessage decompress throws DataFormatException incorrect header check
> ---------------------------------------------------------------------------------
>
>                 Key: AMQ-6142
>                 URL: https://issues.apache.org/jira/browse/AMQ-6142
>             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: Client.java, MessageListener.java, Server.java, 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
(v6.3.4#6332)

Mime
View raw message