squakez closed issue #5088: Quartz builds failing to start when using native
builds
URL: https://github.com/apache/camel-k/issues/5088
--
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
gansheer commented on issue #5088:
URL: https://github.com/apache/camel-k/issues/5088#issuecomment-1920740379
@lsergio Thanks for your feedback, I will update the documentation to
indicate the limitation in native mode for now.
--
This is an automated message from the Apache Git Service.
lsergio commented on issue #5088:
URL: https://github.com/apache/camel-k/issues/5088#issuecomment-1919579855
@gansheer It worked for me. Howver, the only issue is that the Cron trait
does not allow me to use timezones. I opened #5121 to handle that.
--
This is an automated message from
lsergio commented on issue #5088:
URL: https://github.com/apache/camel-k/issues/5088#issuecomment-1912652411
@gansheer thanks for the suggestion. I'll give it a try.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
gansheer commented on issue #5088:
URL: https://github.com/apache/camel-k/issues/5088#issuecomment-1912384954
The mechanism used is the following:
- camel-k identifies if the integration start with a timer, cron or quartz
component and creates a cronjob if the cron expression is valid.
gansheer commented on issue #5088:
URL: https://github.com/apache/camel-k/issues/5088#issuecomment-1908835019
Sorry I was not clear, it is clear that there is a bug here. I am just
trying to get to it.
As @squakez suspected something is not working well with the camel-k-runtime
cron
lsergio commented on issue #5088:
URL: https://github.com/apache/camel-k/issues/5088#issuecomment-1908709736
Per https://camel.apache.org/camel-k/2.2.x/traits/cron.html:
The rules for using a Kubernetes CronJob are the following:
cron, quartz: when the cron expression does not
lsergio commented on issue #5088:
URL: https://github.com/apache/camel-k/issues/5088#issuecomment-1908706695
@gansheer My goal is to run the integration every minute.
The main point here is that it works on jvm mode, where the scheduling is
done with a CronJob, which accepts the
gansheer commented on issue #5088:
URL: https://github.com/apache/camel-k/issues/5088#issuecomment-1907755997
@lsergio to clarify what you are trying to do, what does your cron
expression "* * * * *" should mean in terms of execution schedule ? Because in
the end this is not a valid quartz
squakez commented on issue #5088:
URL: https://github.com/apache/camel-k/issues/5088#issuecomment-1906442085
@lsergio let's see if we manage to fix. Once it's fixed we can discuss the
opportunity to backport and if it makes sense to cut a release on a minor.
--
This is an automated
lsergio commented on issue #5088:
URL: https://github.com/apache/camel-k/issues/5088#issuecomment-1906423482
Hi @squakez and @gansheer. Is there any chance of adding this to a 2.2.1
release as well?
--
This is an automated message from the Apache Git Service.
To respond to the message,
gansheer commented on issue #5088:
URL: https://github.com/apache/camel-k/issues/5088#issuecomment-1906336440
@squakez I'll take care of it.
--
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
gansheer commented on issue #5088:
URL: https://github.com/apache/camel-k/issues/5088#issuecomment-1905692487
If I had to hazard a guess, it could be because the cronjob spec expect 5
field in its cron expression while quartz expect 6 to 7. I suspect that the
fact the native version
squakez commented on issue #5088:
URL: https://github.com/apache/camel-k/issues/5088#issuecomment-1905505702
Thanks for reporting. The cronjob logic happens in the Camel K runtime. I
wonder if the failure is because of that by any chance.
--
This is an automated message from the Apache
lsergio commented on issue #5088:
URL: https://github.com/apache/camel-k/issues/5088#issuecomment-1904629660
If I change my expression to `0 * * * * ?`, no CronJob is created and the
application runs successfully. However, this is not desired, as the pod would
be idle, wasting resources,
lsergio opened a new issue, #5088:
URL: https://github.com/apache/camel-k/issues/5088
### What happened?
Consider the following Integration spec:
```
apiVersion: camel.apache.org/v1
kind: Integration
metadata:
name: test-jvm
spec:
sources:
- name:
16 matches
Mail list logo