activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6142) ActiveMQBytesMessage decompress throws DataFormatException incorrect header check
Date Mon, 11 Apr 2016 12:33:25 GMT

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

ASF subversion and git services commented on AMQ-6142:
------------------------------------------------------

Commit 20e84d63e045d3d26627e204c808677a8fe77dc4 in activemq's branch refs/heads/activemq-5.13.x
from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=20e84d6 ]

https://issues.apache.org/jira/browse/AMQ-6142

Moving the bytes copy to the parent Message class to solve this this
issue for all message types as that is the root cause

(cherry picked from commit e69c2cbad6611fa355bd9eb592f03bd3b8f90abb)


> 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
>             Fix For: 5.13.1, 5.14.0
>
>         Attachments: Client.java, MessageListener.java, Server.java, amq-6142.diff, 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