You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2013/05/26 14:08:20 UTC
[jira] [Updated] (CAMEL-5929) camel-quartz - Add temporal window
activation to route policies
[ https://issues.apache.org/jira/browse/CAMEL-5929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-5929:
-------------------------------
Fix Version/s: Future
Summary: camel-quartz - Add temporal window activation to route policies (was: Add temporal window activation to route policies)
> camel-quartz - Add temporal window activation to route policies
> ---------------------------------------------------------------
>
> Key: CAMEL-5929
> URL: https://issues.apache.org/jira/browse/CAMEL-5929
> Project: Camel
> Issue Type: New Feature
> Components: camel-core, camel-quartz
> Affects Versions: 2.10.3
> Reporter: Philip Glebow
> Labels: features
> Fix For: Future
>
>
> I have several routes that run at different times during the business day. A
> CronScheduledRoutePolicy is used to control the polling schedule. For
> example, the system polls for a file via FTP between 14:00 and 15:00 each
> week day - the file is not guaranteed to be there prior to that time per our
> SLA with the vendor.
> The route policy is in place so that the system does not constantly badger
> the FTP server with useless requests.
> However, from time to time, we need to restart our server. What I've
> observed is that if the server is restarted at 14:30, the route must be
> manually enabled via JMX. We actually have 20-30 routes and this is a
> burden for our support team; they often miss a route or two.
> What I'd like to have is a policy that says "run this route every n minutes
> from 14:00 - 15:00 each weekday" - and have it activated even we restart the
> server at 14:30.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira