You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/05/05 17:00:17 UTC
[jira] [Commented] (AMQ-6281) CompositeDestination copyMessage
configuration is no longer valid
[ https://issues.apache.org/jira/browse/AMQ-6281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272632#comment-15272632 ]
ASF subversion and git services commented on AMQ-6281:
------------------------------------------------------
Commit 5096463b00c4f470b108760f6849f9a0433b6fa0 in activemq's branch refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=5096463 ]
https://issues.apache.org/jira/browse/AMQ-6281
Deprecate the copyMessage option and remove usage, always copy a
forwarded message.
> CompositeDestination copyMessage configuration is no longer valid
> -----------------------------------------------------------------
>
> Key: AMQ-6281
> URL: https://issues.apache.org/jira/browse/AMQ-6281
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.13.0, 5.11.4, 5.13.1, 5.12.3, 5.13.2, 5.13.3
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 5.14.0
>
>
> The configuration value *copyMessage* in CompositeDestination is no longer valid, the messages always need to be copied so their destination value can be updated before being routed through the broker.
> We can deprecate this option and ignore it in the current code base.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)