Pontus, Thanks for that. Since I already has started implementing a class derived from CronScheduledRoutePolicy, I just finished it. It works by starting a Timer thread in onStart/onResume at the end of the time period, the route is suspended, but then upon the next schedule cron start time, I don't see it being resumed - I wonder if the RoutePolicy itself is being suspend too?
Well, I try it your way also. Thanks, Chris On Wed, Mar 20, 2013 at 4:34 AM, Pontus Ullgren <ullg...@gmail.com> wrote: > Hello, > > On Tue, Mar 19, 2013 at 11:22 PM, Chris Wolf <cwolf.a...@gmail.com> wrote: >> On Mon, Mar 18, 2013 at 4:57 PM, Pontus Ullgren <ullg...@gmail.com> wrote: >>> Hello Chris, >>> >>> On Mon, Mar 18, 2013 at 8:54 PM, Chris Wolf <cwolf.a...@gmail.com> wrote: >>>> Claus, >>>> >>>> I have a few further questions about CronScheduledRoutePolicy. I >>>> noticed that it has setters such as setRouteStartTime, >>>> setRouteStopTime, each which takes a cron expression string. What I'm >>>> looking for is to be able to use a cron expression for the start, but >>>> a relative time length for stop. Otherwise, I need to write code to >>>> parse the start time expression, then calculate a stop time cron >>>> expression. Any ideas? >>>> >>> Depending on your needs you could enable "sendEmptyMessageWhenIdle" on >>> the endpoint and then suspend the route when you receive a empty >>> message. Which means that there is no more files to poll at the >>> moment. >>> You can use the content based route EIP for this. >> >> That is interesting to know, thanks. In my case, the files at the >> remote end are themselves deposited at an irregular rate, but within a >> defined time window, so during that time window, there will be >> intermittent idleness... >>> >>> Another solution would be to write your own RoutePolicy to take care >>> of your needs. >> >> Yes, this sounds like the best approach... >> >> >>> >>> I just started to wonder if it might be possible to combine the >>> CronScheduledRoutePolicy with a SimpleScheduledRoutePolicy. >>> I have _not_ tested this so I'm not sure if it works. It might be that >>> there is a collision in the way they work with Quartz. >>> >>>> Also I see that CronScheduledRoutePolicy has setRouteResumeTime, >>>> setRouteSuspendTime such that for my FTP poll window, I could either >>>> do start/stop or resume/suspend - which is recommended? >>>> >>> I would highly recommend resume/suspend. >>> I've had some thread leak problem with the file component when it was >>> repetitively started/stopped. >> >> Ok, but I guess the first policy callback with be onStart since the >> route will be >> configured with noAutoStartup(), so upon that first onStart, I'll >> suspend then toggle >> between onSuspend/onResume... >> > Yes this is what I do. We have a route that should start 06:30 each > day and then poll all files that are in the folder at that time. > After that it should suspend. > > Here is some pseudo code. > SuspendRouteProcessor is a processor that suspends the route based on route > id. > --- > String cronStr = "* 30 6 * * * ?"; > String input = > "ftp://user@remotehost/inbox?sendEmptyMessageWhenIdle=true&password=secret";; > CronScheduledRoutePolicy scheduledRP = new CronScheduledRoutePolicy(); > scheduledRoutePolicy.setRouteStartTime(cronStr); > scheduledRoutePolicy.setRouteResumeTime(cronStr); > > from(input) > .routeId("input1") > .routePolicy(versionPolicy, scheduledRoutePolicy) > .noAutoStartup() > .choice() > .when(body().isNotNull()) > .to("direct:processFiles") > .end() > .log(LoggingLevel.DEBUG, "All files processed, suspend route") > .process(new SuspendRouteProcessor("input1")) > ; > -- > > The only downside with this is that after the initial start we get a > WARN log message that the route can not be started since it is in > suspend state. > But as long as you can live with the WARN log it works. > >>> >>> // Pontus >>> >>>> Thanks, >>>> >>>> Chris >>>> >>>> On Sat, Mar 2, 2013 at 1:43 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: >>>>> Hi >>>>> >>>>> See about route policy >>>>> http://camel.apache.org/routepolicy >>>>> >>>>> And the scheduled route policy >>>>> http://camel.apache.org/scheduledroutepolicy.html >>>>> >>>>> On Sat, Mar 2, 2013 at 12:15 AM, Chris Wolf <cwolf.a...@gmail.com> wrote: >>>>>> I have a requirement to download files via FTP during a certain time >>>>>> window and according to a schedule. e.g. Only on trading days between >>>>>> 6:30AM and 7:00AM. The FTP component, alone, seems to just do >>>>>> indefinite polling according to delay/initialDelay. >>>>>> >>>>>> From the "Camel In Action" book, chapter 7, I see some examples of >>>>>> sending a text message with the Timer and Quartz components, but I >>>>>> can't quite see how to put that together to implement "kicking off >>>>>> routes at specified intervals", mentioned in the best practices list >>>>>> at the end of that chapter. How would I use quartz to stop/start the >>>>>> FTP component, or the route that it's in? >>>>>> >>>>>> Thanks, >>>>>> >>>>>> Chris >>>>> >>>>> >>>>> >>>>> -- >>>>> Claus Ibsen >>>>> ----------------- >>>>> Red Hat, Inc. >>>>> FuseSource is now part of Red Hat >>>>> Email: cib...@redhat.com >>>>> Web: http://fusesource.com >>>>> Twitter: davsclaus >>>>> Blog: http://davsclaus.com >>>>> Author of Camel in Action: http://www.manning.com/ibsen
