camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Charles Moulliard <ch0...@gmail.com>
Subject Re: Camel Endpoint / Consumer startup
Date Fri, 17 Oct 2014 06:09:51 GMT
Hi,

If the from("mqtt") component is not able yo establish a connection from
the broker, then no apache camel exchange will be created. The issue could
be if the .to("mqtt') producer tries to publish a message to a broker using
the mqtt protocol. You can imagine to intercept the exception (due to the
absence of the connection) and suspend the current route.

Regards,



On Thu, Oct 16, 2014 at 11:56 PM, ddewaele <ddewaele@gmail.com> wrote:

> I've run into this issue with the MQTTEndpoint where the MQTT endpoint is
> started (causing the MQTT connection to be established). As a result, the
> flow of mqtt messages is started *before* any consumers of that endpoint
> are
> registered.
>
> This puts the guaranteed delivery aspect of MQTT quality of service at
> risk,
> as on a protocol level these messages have been delivered, yet no consumer
> was available to process them.
>
> Is there a way for me to manipulate this behavior, or would this be
> considered a bug in the MQTT endpoint implementation.
>
> https://issues.apache.org/jira/browse/CAMEL-7922
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Endpoint-Consumer-startup-tp5757635.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Charles Moulliard
Apache Committer / Architect @RedHat
Twitter : @cmoulliard | Blog :  http://cmoulliard.github.io

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message