[
https://issues.apache.org/jira/browse/ARTEMIS-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16173827#comment-16173827
]
ASF subversion and git services commented on ARTEMIS-1424:
----------------------------------------------------------
Commit f84d26ebb26b0c424ae90f994fc1aa673bbad88f in activemq-artemis's branch
refs/heads/master from [~gaohoward]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=f84d26e ]
ARTEMIS-1424 Openwire not work with different tightEncoding options
If message senders and receivers uses different
wireformat.tightEncodingEnabled options, broker will get marshalling
problem. This is because when openwire messages are converted to
core messages, and later these core messages converted to openwire
messages, the broker uses a mashaller that comes with the connection
used to carry the messages.
For example, if a producer sents a message using option "wireformat
.tightEncodingEnabled=false" and a receiver tries to receive it
using 'true' for the same option, it'll never get it because the
broker will fail to use a "tight encoding" marshaller to
decode a 'loose encoded' message.
To fix the problem, we always use 'tight encoding' for internal
message converters.
> Openwire not work with different tightEncoding options
> ------------------------------------------------------
>
> Key: ARTEMIS-1424
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1424
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: OpenWire
> Affects Versions: 2.3.0
> Reporter: Howard Gao
> Assignee: Howard Gao
> Fix For: 2.4.0
>
>
> If message senders and receivers uses different
> wireformat.tightEncodingEnabled options, broker will get marshalling problem.
> This is because when openwire messages are converted to core messages, and
> later these core messages converted to openwire messages, the broker uses a
> mashaller that comes with the connection used to carry the messages.
> For example, if a producer sents a message using option
> "wireformat.tightEncodingEnabled=false" and a receiver tries to receive it
> using 'true' for the same option, it'll never get it because the broker will
> fail to use a "tight encoding" marshaller to decode a 'loose encoded' message.
> To fix the problem, we always use 'tight encoding' for internal message
> converters.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
