We can force camel to start the connection when the consumer is stared, it can fix the issue that you hit.
BTW, the patch is on the way, please keep an eye on the JIRA comments :) -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On October 17, 2014 at 5:56:46 AM, ddewaele ([email protected]) 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. >
