camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomohisa Igarashi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-7673) subscribeTopicName leaks out as a property and used as a destination for mqtt producer, causes infinite delivery
Date Mon, 11 Aug 2014 06:23:12 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-7673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14092495#comment-14092495
] 

Tomohisa Igarashi commented on CAMEL-7673:
------------------------------------------

I guess the problem is that MQTT consumer and producer are using same property for different
purpose, consumer set its susbcribeTopicName into the property so application can read it
to know the topic name, and producer use the property for destination. I would prefer to use
different property name for those since producer never sends back to the topic which is subscribed
by consumer, otherwise it causes infinite delivery.

> subscribeTopicName leaks out as a property and used as a destination for mqtt producer,
causes infinite delivery
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-7673
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7673
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-mqtt
>    Affects Versions: 2.12.2, 2.14.0
>            Reporter: Tomohisa Igarashi
>            Assignee: Willem Jiang
>
> MQTT consumer sets its subscribeTopicName as a exchange property, and it will be used
by MQTT producer as a destination if it exists in the route.
> If you have a following route:
> {code}
> from("mqtt:input?subscribeTopicName=topicIn")
>         .to("mqtt:output?publishTopicName=topicOut");
> {code}
> MQTT consumer put "topicIn" to "MQTTTopicPropertyName" exchange property, and MQTT producer
uses this property to determine a destination topic to publish. Then MQTT producer ignores
publishTopicName and send a message to "topicIn", so MQTT consumer consumes the message again,
eventually it causes infinite delivery. We need to stop this property to be used as a destination
for producer.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message