crosscode-nl opened a new issue #3019: URL: https://github.com/apache/camel-k/issues/3019
When using cron.concurrency-policy with a long running route it does functionally not matter which value is chosen: For example, when running: ```console kamel run timer-schedule.xml -n camel-k --trait cron.concurrency-policy=Allow ``` with route: ````xml <routes xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns="http://camel.apache.org/schema/spring"; xsi:schemaLocation="http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd";> <route> <from uri="timer:tick?period=60000"/> <log message="Work started"/> <loop> <constant>120</constant> <log message="start delay for loop: ${exchangeProperty.CamelLoopIndex}"/> <delay> <constant>60000</constant> </delay> </loop> <log message="Work completed"/> </route> </routes> ``` It will create the cron job with concurrency policy: Allow , but the route will be restarted every minute anyway. Same goes for Forbid. CronJob contains Forbid as concurrency policy, so that works but the route still stops every minute instead of going on. What is the purpose of this trait if for any value this route gets stopped? Do I understand this feature correctly if I expect when Replace is set that the route is stopped and replaced with the new route, but when forbid is chosen nothing should happen to the route and no new route is started, and when allow is chosen that each time 1 minute is reached? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
