crosscode-nl commented on issue #3019: URL: https://github.com/apache/camel-k/issues/3019#issuecomment-1050649285
I don't think the bug is related to timer calculation. The bug is related to how the concurrency policy works. The Camel route seems to behave like it always is configured Replace. It is dissonant with what is configured in Kubernetes. It does not understand Forbid and Allow. The route will always be aborted and restarted. -- 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
