activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AMQ-6142) ActiveMQBytesMessage decompress throws DataFormatException incorrect header check
Date Thu, 07 Apr 2016 18:36:25 GMT

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

Gary Tully edited comment on AMQ-6142 at 4/7/16 6:35 PM:
---------------------------------------------------------

[~cshannon] I think rolling back the sync is best, then thinking of mutation being ok on your
own copy which implies maybe doing more copies and those not sharing mutable state. Client
side there is typically a copy per consumer. 
Broker side there is a single copy of the message at the moment and the reduceMemoryFootPrint
policy can control whacking the duplicate state on send/store for a queue. concurrentStoreAndDispatch
muddies that a bit.



was (Author: gtully):
[~cshannon] I think rolling back the sync is best, then thinking of mutation being ok on your
own copy which implies maybe doing more copies and those not sharing mutable state. Client
side there is typically a copy per consumer. 
Broker side there is a single copy of the message at the moment and the reduceMemoryFootPrint
policy can control whacking the duplicate state on send/store for a queue. concurrentStoreAndDispatch
muddies that a bit.
For topics, maybe when the message is invm, we force a marshall/store on the send and can
be done with a single shared message. Because each consumer may or may not want marshalling
it is a little tricky, but it is only vm consumers that would not marshall.

> 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