[
https://issues.apache.org/jira/browse/AMQ-6972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487258#comment-16487258
]
Marco Carrer commented on AMQ-6972:
-----------------------------------
Thanks for the quick message.
We did try the setOriginalDestination=false on the latest code and it did avoid
to override the "to" address of the AMQP message. Hopefully this can be back
ported into the 5.15 code train so it is released soon.
Even with this workaround, it would be desirable to have an "attribute" of some
sort in the AMQP message where the original MQTT topic is stored and that is
readable via the AMQP Proton client
> Original destination is not accessible via AMQP when using Virtual topics
> -------------------------------------------------------------------------
>
> Key: AMQ-6972
> URL: https://issues.apache.org/jira/browse/AMQ-6972
> Project: ActiveMQ
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 5.15.4
> Reporter: Marco Carrer
> Priority: Major
>
> ActiveMQ MQTT transport is configured for virtual topics -
> transport.subscriptionStrategy=mqtt-virtual-topic-subscriptions. All other
> configuration options are default.
> Messages are published into the broker using MQTT.
> Messages are consumed from the broker using AMQP from the address
> "queue://Consumer.clientA.VirtualTopic.>".
> Messages are correctly received by the AMQP receiver but there is no property
> or annotation in the message which allows the consumer to retrive the
> original MQTT topic on which the message was published to.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
