Re: Camel Endpoint / Consumer startup
You can find the latest SNAPSHOT versions at http://repository.apache.org/content/groups/snapshots/org/apache/camel/. They will be published after a successful Jenkins build, otherwise not... Best, Christian - Software Integration Specialist Apache Member V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer Apache Incubator PMC Member https://www.linkedin.com/pub/christian-mueller/11/551/642 On Fri, Oct 17, 2014 at 5:34 PM, ddewaele ddewa...@gmail.com wrote: OK. We'll test with this on monday first thing. Are Camel snapshots automatically built and published on a remote maven repo somewhere ? If we point to 2.15-SNAPSHOT we should be good to go ? Is there a release schedule available for Camel so we can have a look when 2.15 is scheduled for release ? Thx for committing the fix ! -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Endpoint-Consumer-startup-tp5757635p5757737.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Endpoint / Consumer startup
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 ddewa...@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
Re: Camel Endpoint / Consumer startup
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 (ddewa...@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.
Re: Camel Endpoint / Consumer startup
I'll keep an eye out for the JIRA. Currently created my own MQTT endpoint component that also delays the connection and lets each consumer / producer start a connection. But consider this a hack / workaround. i think the Camel MQTT component needs some attention. But I'm willing to test / help / report / debug issues. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Endpoint-Consumer-startup-tp5757635p5757719.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Endpoint / Consumer startup
Yeah, I cannot agree with you more. Please keep testing and polishing the code if you like, that is how the open source community work :) BTW, I just commit a quick patch for it, you can try it with latest 2.15-SNAPSHOT or check out the master branch code and build it yourself. -- 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:06:25 PM, ddewaele (ddewa...@gmail.com) wrote: I'll keep an eye out for the JIRA. Currently created my own MQTT endpoint component that also delays the connection and lets each consumer / producer start a connection. But consider this a hack / workaround. i think the Camel MQTT component needs some attention. But I'm willing to test / help / report / debug issues. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Endpoint-Consumer-startup-tp5757635p5757719.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Endpoint / Consumer startup
Just had a quick look at the commit, but won't we still have the issue that the endpoint will be creating the connection to the broker (and as a result messages will start flowing). By the time the first consumer will be added messages will be lost. (Camel always needs to start the endpoint first before adding consumers / producers) - The problem is not that the endpoint is not connected by the time consumers are added. - The problem is that the endpoint is already connected *before* consumers are added. Shouldn't it be the responsibility of the consumer / producer of the endpoint to create the connection ? -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Endpoint-Consumer-startup-tp5757635p5757725.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Endpoint / Consumer startup
In my patch MQTTEndpoint doesn’t start the connection until the first Customer or the first Producer is started. We just share the connection throw the MQTTEndpoint. -- 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 7:54:54 PM, ddewaele (ddewa...@gmail.com) wrote: Just had a quick look at the commit, but won't we still have the issue that the endpoint will be creating the connection to the broker (and as a result messages will start flowing). By the time the first consumer will be added messages will be lost. (Camel always needs to start the endpoint first before adding consumers / producers) - The problem is not that the endpoint is not connected by the time consumers are added. - The problem is that the endpoint is already connected *before* consumers are added. Shouldn't it be the responsibility of the consumer / producer of the endpoint to create the connection ? -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Endpoint-Consumer-startup-tp5757635p5757725.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel Endpoint / Consumer startup
OK. We'll test with this on monday first thing. Are Camel snapshots automatically built and published on a remote maven repo somewhere ? If we point to 2.15-SNAPSHOT we should be good to go ? Is there a release schedule available for Camel so we can have a look when 2.15 is scheduled for release ? Thx for committing the fix ! -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Endpoint-Consumer-startup-tp5757635p5757737.html Sent from the Camel - Users mailing list archive at Nabble.com.
Camel Endpoint / Consumer startup
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.
