[jira] [Updated] (CAMEL-20789) camel-kubernetes - Secrets and Config Maps with binay content should be saved as binary file, instead of String in property resolver
[ https://issues.apache.org/jira/browse/CAMEL-20789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-20789: - Fix Version/s: 4.7.0 > camel-kubernetes - Secrets and Config Maps with binay content should be saved > as binary file, instead of String in property resolver > > > Key: CAMEL-20789 > URL: https://issues.apache.org/jira/browse/CAMEL-20789 > Project: Camel > Issue Type: Improvement > Components: camel-kubernetes >Affects Versions: 4.6.0 >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Minor > Fix For: 4.7.0 > > > Since the content of a Secret or Config Map are dynamically retrieved as > property, it should be useful to have a file path of the downloaded binary > content instead of the String object of the byte[] of a binary content -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20789) camel-kubernetes - Secrets and Config Maps with binay content should be saved as binary file, instead of String in property resolver
[ https://issues.apache.org/jira/browse/CAMEL-20789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-20789. -- Resolution: Fixed > camel-kubernetes - Secrets and Config Maps with binay content should be saved > as binary file, instead of String in property resolver > > > Key: CAMEL-20789 > URL: https://issues.apache.org/jira/browse/CAMEL-20789 > Project: Camel > Issue Type: Improvement > Components: camel-kubernetes >Affects Versions: 4.6.0 >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Minor > Fix For: 4.7.0 > > > Since the content of a Secret or Config Map are dynamically retrieved as > property, it should be useful to have a file path of the downloaded binary > content instead of the String object of the byte[] of a binary content -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18280) Reuse AWS localstack docker image
[ https://issues.apache.org/jira/browse/CAMEL-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847919#comment-17847919 ] Federico Mariani commented on CAMEL-18280: -- I'll create singleton for the slowest ITs ( > 30s), in particular, I managed to halve the execution for DynamoDB, S3, SQS, EventBridge, Kinesis. Some refactoring is needed due to queues and S3 bucket with the same name for different tests, hopefully tomorrow I'll finish and create a PR > Reuse AWS localstack docker image > - > > Key: CAMEL-18280 > URL: https://issues.apache.org/jira/browse/CAMEL-18280 > Project: Camel > Issue Type: Improvement > Components: tests >Reporter: Federico Mariani >Assignee: Federico Mariani >Priority: Minor > Labels: easy, help-wanted > Fix For: 4.x > > > AWS IT tests execution is slow mostly due to localstack docker image > restarts, can the docker image be reused via testcontainer? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20383) camel CI: investigate consolidating Jenkinsfiles
[ https://issues.apache.org/jira/browse/CAMEL-20383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske updated CAMEL-20383: - Fix Version/s: 4.6.0 4.4.2 4.0.5 > camel CI: investigate consolidating Jenkinsfiles > - > > Key: CAMEL-20383 > URL: https://issues.apache.org/jira/browse/CAMEL-20383 > Project: Camel > Issue Type: Task > Components: ci >Reporter: Otavio Rodolfo Piske >Assignee: Vaishnavi R >Priority: Major > Labels: help-wanted > Fix For: 4.0.5, 4.4.2, 4.6.0 > > > As we have been adding more jobs to our CI (including different JDKs versions > + different JDKs versions on different platforms). We might end up with a lot > of duplication and noise on the CI code. > We should investigate a way to consolidate all these CI automation in a > single file (or create reusable code) so it's easier to add/remove > environments. > Ideally, we should do that before duplication becomes a maintenance problem. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20383) camel CI: investigate consolidating Jenkinsfiles
[ https://issues.apache.org/jira/browse/CAMEL-20383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-20383. -- Resolution: Fixed This item has been completed by [~var] and merged by me. We can close this now. > camel CI: investigate consolidating Jenkinsfiles > - > > Key: CAMEL-20383 > URL: https://issues.apache.org/jira/browse/CAMEL-20383 > Project: Camel > Issue Type: Task > Components: ci >Reporter: Otavio Rodolfo Piske >Assignee: Vaishnavi R >Priority: Major > Labels: help-wanted > > As we have been adding more jobs to our CI (including different JDKs versions > + different JDKs versions on different platforms). We might end up with a lot > of duplication and noise on the CI code. > We should investigate a way to consolidate all these CI automation in a > single file (or create reusable code) so it's easier to add/remove > environments. > Ideally, we should do that before duplication becomes a maintenance problem. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20775) camel-hashicorp-vault - configure multiple engines
[
https://issues.apache.org/jira/browse/CAMEL-20775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-20775:
-
Fix Version/s: 4.7.0
(was: 4.x)
> camel-hashicorp-vault - configure multiple engines
> --
>
> Key: CAMEL-20775
> URL: https://issues.apache.org/jira/browse/CAMEL-20775
> Project: Camel
> Issue Type: Improvement
> Components: camel-hashicorp-vault
>Reporter: Federico Mariani
>Assignee: Andrea Cosentino
>Priority: Major
> Fix For: 4.7.0
>
>
> Currently, only one engine can be (easily) configured in the
> camel-hashicorp-vault component.
> It would be nice to configure the engine ala
> \{{hashicorp:engine:path/to/secret}} so that multiple engines can be used in
> the same application. for example, key/value store engine and pki store
> engine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-20383) camel CI: investigate consolidating Jenkinsfiles
[ https://issues.apache.org/jira/browse/CAMEL-20383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske reassigned CAMEL-20383: Assignee: Vaishnavi R > camel CI: investigate consolidating Jenkinsfiles > - > > Key: CAMEL-20383 > URL: https://issues.apache.org/jira/browse/CAMEL-20383 > Project: Camel > Issue Type: Task > Components: ci >Reporter: Otavio Rodolfo Piske >Assignee: Vaishnavi R >Priority: Major > Labels: help-wanted > > As we have been adding more jobs to our CI (including different JDKs versions > + different JDKs versions on different platforms). We might end up with a lot > of duplication and noise on the CI code. > We should investigate a way to consolidate all these CI automation in a > single file (or create reusable code) so it's easier to add/remove > environments. > Ideally, we should do that before duplication becomes a maintenance problem. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20636) Camel Support for EDI (EDIFACT) data format
[ https://issues.apache.org/jira/browse/CAMEL-20636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20636. - Resolution: Duplicate > Camel Support for EDI (EDIFACT) data format > --- > > Key: CAMEL-20636 > URL: https://issues.apache.org/jira/browse/CAMEL-20636 > Project: Camel > Issue Type: New Feature >Reporter: Mohamed Chebbi >Priority: Minor > > due to the use of EDIFACT in Telecom operator a need to support EDI data > format is suggested so apache camel can be used for mediation and > provisioning in such operator. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20789) camel-kubernetes - Secrets and Config Maps with binay content should be saved as binary file, instead of String in property resolver
[ https://issues.apache.org/jira/browse/CAMEL-20789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Carletti updated CAMEL-20789: --- Summary: camel-kubernetes - Secrets and Config Maps with binay content should be saved as binary file, instead of String in property resolver (was: camel-kubernetes - Secrets can Config Maps with binay content should be saved as binary file, instead of String in property resolver) > camel-kubernetes - Secrets and Config Maps with binay content should be saved > as binary file, instead of String in property resolver > > > Key: CAMEL-20789 > URL: https://issues.apache.org/jira/browse/CAMEL-20789 > Project: Camel > Issue Type: Improvement > Components: camel-kubernetes >Affects Versions: 4.6.0 >Reporter: Marco Carletti >Assignee: Marco Carletti >Priority: Minor > > Since the content of a Secret or Config Map are dynamically retrieved as > property, it should be useful to have a file path of the downloaded binary > content instead of the String object of the byte[] of a binary content -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20790) kafka batching consumer polls randomly failing with NPE under load
[
https://issues.apache.org/jira/browse/CAMEL-20790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20790:
Fix Version/s: 4.x
> kafka batching consumer polls randomly failing with NPE under load
> --
>
> Key: CAMEL-20790
> URL: https://issues.apache.org/jira/browse/CAMEL-20790
> Project: Camel
> Issue Type: Bug
> Components: camel-kafka
>Affects Versions: 4.4.2, 4.6.0
>Reporter: Ihar Reznichenka
>Priority: Minor
> Fix For: 4.x
>
> Attachments: KafkaBatchingProcessingManualCommitExchangeListNPEIT.java
>
>
> A camel-kafka batching consumer is randomly catching NPEs.
> This is happening with and w/o manual commit.
> If the consumer is configured with pollOnError=RETRY then it causes lost
> records.
> Please find a test to reproduce the issue attached.
>
>
> {code:java}
> java.lang.NullPointerException: Cannot invoke "java.util.List.add(Object)"
> because "this.exchangeList" is null
> at
> org.apache.camel.component.kafka.consumer.support.batching.KafkaRecordBatchingProcessor.processExchange(KafkaRecordBatchingProcessor.java:137)
> at
> org.apache.camel.component.kafka.consumer.support.batching.KafkaRecordBatchingProcessorFacade.processPolledRecords(KafkaRecordBatchingProcessorFacade.java:59)
> at
> org.apache.camel.component.kafka.KafkaFetchRecords.startPolling(KafkaFetchRecords.java:353)
> at
> org.apache.camel.component.kafka.KafkaFetchRecords.run(KafkaFetchRecords.java:173)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
> at
> java.base/java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:264)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:840) {code}
>
> Please let me know if any additional details are required here.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20790) kafka batching consumer polls randomly failing with NPE under load
Ihar Reznichenka created CAMEL-20790:
Summary: kafka batching consumer polls randomly failing with NPE
under load
Key: CAMEL-20790
URL: https://issues.apache.org/jira/browse/CAMEL-20790
Project: Camel
Issue Type: Bug
Components: camel-kafka
Affects Versions: 4.6.0, 4.4.2
Reporter: Ihar Reznichenka
Attachments: KafkaBatchingProcessingManualCommitExchangeListNPEIT.java
A camel-kafka batching consumer is randomly catching NPEs.
This is happening with and w/o manual commit.
If the consumer is configured with pollOnError=RETRY then it causes lost
records.
Please find a test to reproduce the issue attached.
{code:java}
java.lang.NullPointerException: Cannot invoke "java.util.List.add(Object)"
because "this.exchangeList" is null
at
org.apache.camel.component.kafka.consumer.support.batching.KafkaRecordBatchingProcessor.processExchange(KafkaRecordBatchingProcessor.java:137)
at
org.apache.camel.component.kafka.consumer.support.batching.KafkaRecordBatchingProcessorFacade.processPolledRecords(KafkaRecordBatchingProcessorFacade.java:59)
at
org.apache.camel.component.kafka.KafkaFetchRecords.startPolling(KafkaFetchRecords.java:353)
at
org.apache.camel.component.kafka.KafkaFetchRecords.run(KafkaFetchRecords.java:173)
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at
java.base/java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:264)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java)
at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:840) {code}
Please let me know if any additional details are required here.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-20789) camel-kubernetes - Secrets can Config Maps with binay content should be saved as binary file, instead of String in property resolver
Marco Carletti created CAMEL-20789: -- Summary: camel-kubernetes - Secrets can Config Maps with binay content should be saved as binary file, instead of String in property resolver Key: CAMEL-20789 URL: https://issues.apache.org/jira/browse/CAMEL-20789 Project: Camel Issue Type: Improvement Components: camel-kubernetes Affects Versions: 4.6.0 Reporter: Marco Carletti Assignee: Marco Carletti Since the content of a Secret or Config Map are dynamically retrieved as property, it should be useful to have a file path of the downloaded binary content instead of the String object of the byte[] of a binary content -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18280) Reuse AWS localstack docker image
[ https://issues.apache.org/jira/browse/CAMEL-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Federico Mariani reassigned CAMEL-18280: Assignee: Federico Mariani > Reuse AWS localstack docker image > - > > Key: CAMEL-18280 > URL: https://issues.apache.org/jira/browse/CAMEL-18280 > Project: Camel > Issue Type: Improvement > Components: tests >Reporter: Federico Mariani >Assignee: Federico Mariani >Priority: Minor > Labels: easy, help-wanted > Fix For: 4.x > > > AWS IT tests execution is slow mostly due to localstack docker image > restarts, can the docker image be reused via testcontainer? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (CAMEL-18280) Reuse AWS localstack docker image
[ https://issues.apache.org/jira/browse/CAMEL-18280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-18280 started by Federico Mariani. > Reuse AWS localstack docker image > - > > Key: CAMEL-18280 > URL: https://issues.apache.org/jira/browse/CAMEL-18280 > Project: Camel > Issue Type: Improvement > Components: tests >Reporter: Federico Mariani >Assignee: Federico Mariani >Priority: Minor > Labels: easy, help-wanted > Fix For: 4.x > > > AWS IT tests execution is slow mostly due to localstack docker image > restarts, can the docker image be reused via testcontainer? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20217) Provide option to create a Pipe file through Camel Jbang init
[
https://issues.apache.org/jira/browse/CAMEL-20217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20217.
-
Fix Version/s: 4.7.0
Assignee: Claus Ibsen
Resolution: Fixed
> Provide option to create a Pipe file through Camel Jbang init
> -
>
> Key: CAMEL-20217
> URL: https://issues.apache.org/jira/browse/CAMEL-20217
> Project: Camel
> Issue Type: New Feature
> Components: camel-jbang
>Reporter: Aurélien Pupier
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.7.0
>
>
> it would be convenient to provide an option of Camel Jbang init to create a
> Pipe file.
> There is currently an option --integration to create a Camel K integration,
> maybe we can add an exclusive option --pipe
> What would be the content of the file?
> proposal:
> {noformat}
> apiVersion: camel.apache.org/v1
> kind: Pipe
> metadata:
> name: my-pipe // maybe use the name of the file here?
> spec:
> source:
> ref:
> kind: Kamelet
> apiVersion: camel.apache.org/v1
> name: timer-source
> properties:
> message: hello
> sink:
> ref:
> kind: Kamelet
> apiVersion: camel.apache.org/v1
> name: log-sink
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20407) camel-datasonnet - Add support for variables
[ https://issues.apache.org/jira/browse/CAMEL-20407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20407. - Fix Version/s: 4.7.0 (was: 4.x) Assignee: Claus Ibsen Resolution: Fixed > camel-datasonnet - Add support for variables > > > Key: CAMEL-20407 > URL: https://issues.apache.org/jira/browse/CAMEL-20407 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.7.0 > > > So you can use variables also. > See the CML.java file -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20786) Resolve Camel Property Placeholders in properties file/system
[
https://issues.apache.org/jira/browse/CAMEL-20786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847789#comment-17847789
]
Claus Ibsen commented on CAMEL-20786:
-
Ups sorry I attached a new file sb-base64
> Resolve Camel Property Placeholders in properties file/system
> -
>
> Key: CAMEL-20786
> URL: https://issues.apache.org/jira/browse/CAMEL-20786
> Project: Camel
> Issue Type: New Feature
>Reporter: Federico Mariani
>Priority: Major
> Attachments: sb-base64.zip, sb-props.zip
>
>
> It would be nice to resolve Camel Property placeholders, for example, Azure
> Vault, in application.properties files, system properties, and so on. I think
> that plain Camel, Camel Spring Boot and Camel Quarkus may benefit from it,
> for example, I'd be able to do the following, given the
> application.properties file:
> {code:java}
> mypassword={{azure:pass}}
> {code}
> at runtime, the actual password is used and resolved using the
> camel-azure-key-vault component
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20786) Resolve Camel Property Placeholders in properties file/system
[
https://issues.apache.org/jira/browse/CAMEL-20786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-20786:
Attachment: sb-base64.zip
> Resolve Camel Property Placeholders in properties file/system
> -
>
> Key: CAMEL-20786
> URL: https://issues.apache.org/jira/browse/CAMEL-20786
> Project: Camel
> Issue Type: New Feature
>Reporter: Federico Mariani
>Priority: Major
> Attachments: sb-base64.zip, sb-props.zip
>
>
> It would be nice to resolve Camel Property placeholders, for example, Azure
> Vault, in application.properties files, system properties, and so on. I think
> that plain Camel, Camel Spring Boot and Camel Quarkus may benefit from it,
> for example, I'd be able to do the following, given the
> application.properties file:
> {code:java}
> mypassword={{azure:pass}}
> {code}
> at runtime, the actual password is used and resolved using the
> camel-azure-key-vault component
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20786) Resolve Camel Property Placeholders in properties file/system
[
https://issues.apache.org/jira/browse/CAMEL-20786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847787#comment-17847787
]
Federico Mariani commented on CAMEL-20786:
--
I am sorry [~davsclaus] the attachment contains only an empty folder
> Resolve Camel Property Placeholders in properties file/system
> -
>
> Key: CAMEL-20786
> URL: https://issues.apache.org/jira/browse/CAMEL-20786
> Project: Camel
> Issue Type: New Feature
>Reporter: Federico Mariani
>Priority: Major
> Attachments: sb-props.zip
>
>
> It would be nice to resolve Camel Property placeholders, for example, Azure
> Vault, in application.properties files, system properties, and so on. I think
> that plain Camel, Camel Spring Boot and Camel Quarkus may benefit from it,
> for example, I'd be able to do the following, given the
> application.properties file:
> {code:java}
> mypassword={{azure:pass}}
> {code}
> at runtime, the actual password is used and resolved using the
> camel-azure-key-vault component
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20244) camel-core - Supervising route controller should default be DOWN during restarting and exhaust phase
[ https://issues.apache.org/jira/browse/CAMEL-20244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-20244. - Resolution: Fixed > camel-core - Supervising route controller should default be DOWN during > restarting and exhaust phase > > > Key: CAMEL-20244 > URL: https://issues.apache.org/jira/browse/CAMEL-20244 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > See CAMEL-20242 > And this example > https://github.com/apache/camel-kamelets-examples/tree/main/jbang/route-controller > You need to turn on 2 options to make the controller report DOWN for routes > that are failing to startup or failed after X attempts. > This is more intuitive. Users that need to do as before or some other reason > can turn these options off. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20244) camel-core - Supervising route controller should default be DOWN during restarting and exhaust phase
[ https://issues.apache.org/jira/browse/CAMEL-20244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-20244: --- Assignee: Claus Ibsen > camel-core - Supervising route controller should default be DOWN during > restarting and exhaust phase > > > Key: CAMEL-20244 > URL: https://issues.apache.org/jira/browse/CAMEL-20244 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > See CAMEL-20242 > And this example > https://github.com/apache/camel-kamelets-examples/tree/main/jbang/route-controller > You need to turn on 2 options to make the controller report DOWN for routes > that are failing to startup or failed after X attempts. > This is more intuitive. Users that need to do as before or some other reason > can turn these options off. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-20244) camel-core - Supervising route controller should default be DOWN during restarting and exhaust phase
[ https://issues.apache.org/jira/browse/CAMEL-20244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-20244: Fix Version/s: 4.7.0 (was: 4.x) > camel-core - Supervising route controller should default be DOWN during > restarting and exhaust phase > > > Key: CAMEL-20244 > URL: https://issues.apache.org/jira/browse/CAMEL-20244 > Project: Camel > Issue Type: Improvement > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.7.0 > > > See CAMEL-20242 > And this example > https://github.com/apache/camel-kamelets-examples/tree/main/jbang/route-controller > You need to turn on 2 options to make the controller report DOWN for routes > that are failing to startup or failed after X attempts. > This is more intuitive. Users that need to do as before or some other reason > can turn these options off. -- This message was sent by Atlassian Jira (v8.20.10#820010)
