rabbitmq component not consuming based on throttle and timePeriodmillis configured in the route

"rabbitmq" component is not consuming messages based on throttle and timePeriodMillis configured in the route and its consuming all the messages from queue. We are using bluelock's "spring-amqp" component and we are able consume 1 msg/sec by configuring throttle(1) and timePeriodMillis(1000) eventh

Re: Loop through the files from FTP server and process

The FTP component is a polling consumer, so it will continue to look for files at the location you specify. The FTP component is derived from the File component, so you need to look at the docs for the File component to see the polling configurations. http://camel.apache.org/file2.html

Re: Loop through the files from FTP server and process

Thanks for responding. Use case is get list of filenames from FTP folder and for each file, process the data in BigQuery(Which is done in Java class) and output is copied from Google Storage to FTP server. With the XML above I don't have an understanding that, does it process for each file in l

Using adviceWith in multiple routes

The camel docs advise not to use adviceWith multiple times in the same route, but say that it's OK to use it across multiple routes. However, I'm seeing problems with the latter. If I use the following in my test... context.getRouteDefinition("route1").adviceWith(context, new AdviceWithRou

Re: Spring Boot and Camel 2.17 - HangupSupport Removed!

You do not need to explicit call registerShutdownHook, from camel 2.17 is is on by default so you can make it shorten by using SpringApplication.run(YourMain.class, args). You can find a very simple example here: https://github.com/lburgazzoli/lb-camel/tree/master/camel-samples/camel-samples-spring

Re: Best Strategy to process a large number of rows in File

You may want to tell it to chunk the file then. That's something you can add to the splitter/tokenizer. On Mon, Apr 18, 2016 at 4:12 PM, Michele wrote: > Hi, > > I have different mediations. Each mediation handles an incoming file type > (csv, txt delimited or fixed length) during the prorcessi

Re: Loop through the files from FTP server and process

Can you be more specific about the issue you’re having? It looks like you have the right idea once you complete the ftp URIs and such. BTW - Camel works in pipeline mode by default, so you don’t need the elements in this case. > On Apr 18, 2016, at 2:40 PM, sc wrote: > > I am very new to A

Re: How to stop Camel Context after all files FTP?

You could set the sendEmptyMessageWhenIdle=true and then check the body - if it’s null, you didn’t get another file so you could shutdown. > On Apr 19, 2016, at 7:58 AM, polanki wrote: > > I wrote below code to FTP files from remote server. I need to do FTP only one > time and get all files fro

Re: Spring Boot and Camel 2.17 - HangupSupport Removed!

Hi, thanks for the fast response. Sorry was my fault since i missed that other jira. Didn't read the changelog that far :) The solution provided in CAMEL-9720 seems to work (just tested it) But this definitely should be in the official documentation about Camel and Spring Boot Applications!

How to stop Camel Context after all files FTP?

I wrote below code to FTP files from remote server. I need to do FTP only one time and get all files from remote system. But with below code, I need to specify how much time to wait before stopping the context. Is it possible to specify stop only after all files FTP. { final CamelContext cam

Re: Spring Boot and Camel 2.17 - HangupSupport Removed!

Hello Hubertus, please have a look at: - https://issues.apache.org/jira/browse/CAMEL-9720 - https://github.com/apache/camel/commit/28c83d58db7c50be9aecbcd81b45af5004bcb304 Let us know if it works. --- Luca Burgazzoli On Tue, Apr 19, 2016 at 3:25 PM, Hubertus.Willuhn wrote: > Hello, > > sin

Spring Boot and Camel 2.17 - HangupSupport Removed!

Hello, since the latest update of Camel to Version 2.17 (which I am trying to migrate my Application to) the hangup support for the SpringBootApplicationController was removed from Camel. This ticket refer to that: https://issues.apache.org/jira/browse/CAMEL-9330