[
https://issues.apache.org/jira/browse/AMQ-6142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15228135#comment-15228135
]
Gary Tully commented on AMQ-6142:
---------------------------------
[~cshannon] sorry for the late input. I was peeking at this change and some of
the sync from https://issues.apache.org/jira/browse/AMQ-6218 etc.
Message intentionally has no sync, the intent is that copy is called if mods
will be made. There is one before dispatch to a consumer that should sort this
issue.
However, the copy seems broken.
For this bytesMessage case, it looks like the root cause is in message.copy
where the content ByteSequence is referenced rather than copied in error.
For AMQ-6218 - if all of those issues relate to concurrentStoreAndDispatch, it
may be that we need to take a message.copy for the async store case.
Let me attach a diff to see if this makes sense to you.
> 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, 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)
