骆驼只在错误的时间开始与石英预定的第一条路线

Question

我有一个Spring boot应用程序，其中包含几条camel路由，这些路由应该基于Quartz2的CronTrigger启动。由于某种原因，只有第一个计划的路由才会启动，但它是在最后一个计划的时间启动的。

1. 路由一:mytime-1h
2. 路由二:mytime

/**
* Starts a list of routes that have been scheduled in application.yml
*/
@Component
public class ScheduledRoutesRouteBuilder extends SpringRouteBuilder {

  private static final Logger LOG = LoggerFactory.getLogger(ScheduledRoutesRouteBuilder.class);
  private static final String BEAN_CHECKDB = "bean:checkDBBean?method=getFirstRecord(%s, %s)";

  @Autowired
  private RoutesDefinition routesDefinition;

  @Override
  public void configure() throws Exception {
    routesDefinition.getScheduledRoutes().stream()
    .forEach(route -> createScheduledRoute(route));
}

  private void createScheduledRoute(RouteDefinition aRoute) {
    from(aRoute.getSchedule())
    .routeId(aRoute.getRouteId())
    .log(LoggingLevel.INFO, LOG, "Kickstarting export route: " + aRoute.getRouteId() + " - schedule: " + aRoute.getSchedule())
    .to(String.format(BEAN_CHECKDB, aRoute.getDbTableName(), aRoute.getReferenceDateColumnName()));
    System.out.println("Configured export route: " + aRoute.getRouteId() + " - schedule: " + aRoute.getSchedule());
  }
}

# Schedules
scheduleFirst: 0 39 * * * ?
scheduleSecond: 0 41 * * * ?

scheduledRoutes:
  - routeId: MonthProcessingRoute
      dbTableName: month
      referenceDateColumnName: acceptatiedatum
      schedule: quartz2://CronTrigger?cron=${scheduleFirst}
  - routeId: WeekProcessingRoute
      dbTableName: week
      referenceDateColumnName: acceptatiedatum
      schedule: quartz2://CronTrigger?cron=${scheduleSecond}

已配置导出路由：WeekProcessingRoute-Schedule:Quartz2:/cronTrigger？cron=041***？

2018-03-20 05:37:33信息选拔赛-Spring-Camel Ivana.StartUp---在2.507秒内启动（JVM运行时间为3.238）

2018-03-20 05:41:00信息选拔赛-Spring-Camel Ivana.routebuilders.scheduledRouteBuilder---启动导出路由：MonthProcessingRoute-schedule:quartz2://crontrigger？cron=039***？

在数据库表中找到的最近日期月份：2017-11-05 15:31:00.0

Answer 1

您应该确保为每个Camel路由使用唯一的triggername/groupname。在这两条路由中，您似乎使用了相同的名称crontrigger。将其改为唯一的名称，它应该可以工作。