[
https://issues.apache.org/jira/browse/ARTEMIS-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15532268#comment-15532268
]
ASF GitHub Bot commented on ARTEMIS-758:
----------------------------------------
Github user mtaylor commented on the issue:
https://github.com/apache/activemq-artemis/pull/810
The issue aiui is that the CORE object message encoding adds some
additional data to the serialized byte stream received from the client, it
prepends the byte with the length of the binary, I presume this was used in the
past when reading the binary back from the Journal. The problem with just
dumping the byte stream as we were doing previously, is that there's a
different encoding for CORE vs OpenWire. This small changes ensures that both
encodings are the same.
Another way to approach this would have been to add some extra meta-data to
the message describing it's content as @tabish121 mentioned with the
"'application/x-java-serialized-object" type or something similar. I think we
can do that as part of the larger task of removing the translations. Right now
though, this small change fixes the cross protocol issue.
> List/Object message sent by OpenWire JMS client can't be consumed with other
> clients
> ------------------------------------------------------------------------------------
>
> Key: ARTEMIS-758
> URL: https://issues.apache.org/jira/browse/ARTEMIS-758
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP, Broker
> Affects Versions: 1.4.0
> Reporter: Andy Taylor
> Assignee: Andy Taylor
> Fix For: 1.5.0
>
>
> something gets screwed when the object is deserialised at the broker
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
