activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claudio Tagliola (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6142) ActiveMQBytesMessage decompress throws DataFormatException incorrect header check
Date Mon, 25 Jan 2016 14:03:39 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115228#comment-15115228
] 

Claudio Tagliola commented on AMQ-6142:
---------------------------------------

Prior thread on activemq-users: http://activemq.2283324.n4.nabble.com/ActiveMQBytesMessage-decompress-throws-DataFormatException-incorrect-header-check-tp4706292.html

> 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
>         Attachments: Client.java, MessageListener.java, Server.java, pom.xml
>
>
> In our environment we use an embedded broker. On one topic, 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.
> 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