[
https://issues.apache.org/jira/browse/AMQ-6100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272763#comment-15272763
]
ASF subversion and git services commented on AMQ-6100:
------------------------------------------------------
Commit c276e2e652d2964cdc69ebf9b72663f0d985031d in activemq's branch
refs/heads/activemq-5.13.x from [~dejanb]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=c276e2e ]
https://issues.apache.org/jira/browse/AMQ-6100 - Virtual topic message
destination should be the target queue
(cherry picked from commit 4e63ee7cc7c4ed7d1fb8ae916c0984b974c175c0)
> Virtual topic message destination should be the target queue
> ------------------------------------------------------------
>
> Key: AMQ-6100
> URL: https://issues.apache.org/jira/browse/AMQ-6100
> Project: ActiveMQ
> Issue Type: Improvement
> Affects Versions: 5.13.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.14.0, 5.13.4
>
>
> When message is delivered using virtual topic, it will have original topic as
> its JMSDestination property. The better way would be to have this value set
> as OriginalDestination property on ActiveMQMessage object, and use the target
> queue name as the JMSDestination.
> Additionally, the current implementation leads to inconsistency in the broker
> cluster environment as this value is change when forwarding the message over
> the network.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
