Hi Claus, Glad to hear about the news of Red Hat working on releasing 1.8. I'll try it later. Thanks!
I've just found a workaround to use trait camel.runtime-version=1.14.0 to override the default version 1.6.x. Though, there is still another blocker on my way in the other mail thread: Poll enrich with mail component will lose attachments (on Camel K 1.10) Regards, Jane -----Original Message----- From: Claus Ibsen <claus.ib...@gmail.com> Sent: Tuesday, September 6, 2022 3:50 PM To: users@camel.apache.org Subject: Re: Camel K 1.6.x Cron Job will shutdown unexpectedly when I use Split EIP Hi Yeah I vaguely remember now something on top of my head that there was such a bug that has since been fixed in Camel. Do you really need to run this as a k8s cron job? You could turn that off and let the pod keep running and let Camel trigger it periodically as a normal Camel app. A workaround is harder to do in Camel K as you then need to "fool" Camel into think its not done and keep running, and then need to "cleanup" when you are really done. And Red Hat is working on releasing a newer Camel K release based on 1.8 Camel K - should be. coming soon. So when its GA you can upgrade to that release. On Tue, Sep 6, 2022 at 9:15 AM Mi Jane 米静 <jane...@universalbeijing.com> wrote: > Dear community, > > I’m trying Camel K and using RedHat operator, which the latest version > is 1.6.x. When I used Split EIP with Cron, I found the Cron Job pods > sometimes shutdown before all the split exchanges were completed. > > Seems the issue is fixed in Camel K later version. Because when I > tried the Community operator with Camel K 1.10.0, it never happen again. > > Is it a known issue? Is there any workaround if I have to use the > RedHat operator with Camel K 1.6.x for now? Thanks! > > Regards, > Jane > > -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
