[jira] [Updated] (CAMEL-21429) camel-kafka - Upgrade to Kafka 3.9.0
[ https://issues.apache.org/jira/browse/CAMEL-21429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21429: Fix Version/s: 4.x (was: 4.10.0) > camel-kafka - Upgrade to Kafka 3.9.0 > > > Key: CAMEL-21429 > URL: https://issues.apache.org/jira/browse/CAMEL-21429 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-kafka >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.x > > > There may be some new options we can include in the camel-kafka component > https://kafka.apache.org/39/documentation.html#upgrade -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19665) components that are polling can become batch polling
[ https://issues.apache.org/jira/browse/CAMEL-19665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908464#comment-17908464 ] Claus Ibsen commented on CAMEL-19665: - camel-git *DONE* > components that are polling can become batch polling > > > Key: CAMEL-19665 > URL: https://issues.apache.org/jira/browse/CAMEL-19665 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.x > > > There are some components that uses ScheduledPollingConsumer that essentially > do their own kind of batch. > Instead they can be changed to ScheduledBatchPollingConsumer and do batch the > standard Camel way. > - camel-couchbase > - camel-git > - camel-github > - camel-hdfs > - camel-jira > - camel-jt400 > and maybe some others, search for ScheduledPollingConsumer to find more. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19665) components that are polling can become batch polling
[ https://issues.apache.org/jira/browse/CAMEL-19665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19665: Description: There are some components that uses ScheduledPollingConsumer that essentially do their own kind of batch. Instead they can be changed to ScheduledBatchPollingConsumer and do batch the standard Camel way. - camel-couchbase - camel-git - camel-github - camel-hdfs - camel-jira and maybe some others, search for ScheduledPollingConsumer to find more. was: There are some components that uses ScheduledPollingConsumer that essentially do their own kind of batch. Instead they can be changed to ScheduledBatchPollingConsumer and do batch the standard Camel way. - camel-couchbase - camel-git - camel-github - camel-hdfs - camel-jira - camel-jt400 and maybe some others, search for ScheduledPollingConsumer to find more. > components that are polling can become batch polling > > > Key: CAMEL-19665 > URL: https://issues.apache.org/jira/browse/CAMEL-19665 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.x > > > There are some components that uses ScheduledPollingConsumer that essentially > do their own kind of batch. > Instead they can be changed to ScheduledBatchPollingConsumer and do batch the > standard Camel way. > - camel-couchbase > - camel-git > - camel-github > - camel-hdfs > - camel-jira > and maybe some others, search for ScheduledPollingConsumer to find more. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21304) Avoid "Invalid AnsiLogger Stream -> Swapping to default sdt out logger." with Camel JBang kubernetes run
[
https://issues.apache.org/jira/browse/CAMEL-21304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908446#comment-17908446
]
Claus Ibsen commented on CAMEL-21304:
-
Is this still happening with 4.9.0 or 4.8.2 release
> Avoid "Invalid AnsiLogger Stream -> Swapping to default sdt out logger." with
> Camel JBang kubernetes run
>
>
> Key: CAMEL-21304
> URL: https://issues.apache.org/jira/browse/CAMEL-21304
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Aurélien Pupier
>Assignee: Thomas Diesler
>Priority: Minor
>
> {noformat}
> jbang '-Dcamel.jbang.version=4.7.0' camel@apache/camel init TestCreate.java
> jbang '-Dcamel.jbang.version=4.7.0' camel@apache/camel kubernetes run
> TestCreate.java
> {noformat}
>
> leads to have this message:
> {noformat}
> Invalid AnsiLogger Stream -> Swapping to default sdt out logger.
> {noformat}
> Tried also with cluster-type openshift
> it would be better if the AnsiLooger Stream is correctly configured out of
> the box
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-21304) Avoid "Invalid AnsiLogger Stream -> Swapping to default sdt out logger." with Camel JBang kubernetes run
[
https://issues.apache.org/jira/browse/CAMEL-21304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21304:
Fix Version/s: 4.x
> Avoid "Invalid AnsiLogger Stream -> Swapping to default sdt out logger." with
> Camel JBang kubernetes run
>
>
> Key: CAMEL-21304
> URL: https://issues.apache.org/jira/browse/CAMEL-21304
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
>Affects Versions: 4.8.0
>Reporter: Aurélien Pupier
>Assignee: Thomas Diesler
>Priority: Minor
> Fix For: 4.x
>
>
> {noformat}
> jbang '-Dcamel.jbang.version=4.7.0' camel@apache/camel init TestCreate.java
> jbang '-Dcamel.jbang.version=4.7.0' camel@apache/camel kubernetes run
> TestCreate.java
> {noformat}
>
> leads to have this message:
> {noformat}
> Invalid AnsiLogger Stream -> Swapping to default sdt out logger.
> {noformat}
> Tried also with cluster-type openshift
> it would be better if the AnsiLooger Stream is correctly configured out of
> the box
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19665) components that are polling can become batch polling
[ https://issues.apache.org/jira/browse/CAMEL-19665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908461#comment-17908461 ] Claus Ibsen commented on CAMEL-19665: - camel-github *DONE* > components that are polling can become batch polling > > > Key: CAMEL-19665 > URL: https://issues.apache.org/jira/browse/CAMEL-19665 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.x > > > There are some components that uses ScheduledPollingConsumer that essentially > do their own kind of batch. > Instead they can be changed to ScheduledBatchPollingConsumer and do batch the > standard Camel way. > - camel-couchbase > - camel-git > - camel-github > - camel-hdfs > - camel-jira > - camel-jt400 > and maybe some others, search for ScheduledPollingConsumer to find more. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21409) camel-debezium - Add MariaDB connector
[ https://issues.apache.org/jira/browse/CAMEL-21409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21409. - Resolution: Won't Fix it seems mariadb is GPL https://www.apache.org/legal/resolved.html#category-x > camel-debezium - Add MariaDB connector > -- > > Key: CAMEL-21409 > URL: https://issues.apache.org/jira/browse/CAMEL-21409 > Project: Camel > Issue Type: New Feature > Components: camel-debezium >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.x > > > We should add this connector -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20910) Build is failing with mvnd 1.0.0/1.0.1
[
https://issues.apache.org/jira/browse/CAMEL-20910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-20910.
-
Resolution: Fixed
> Build is failing with mvnd 1.0.0/1.0.1
> --
>
> Key: CAMEL-20910
> URL: https://issues.apache.org/jira/browse/CAMEL-20910
> Project: Camel
> Issue Type: Task
> Components: tooling
>Affects Versions: 4.6.0
>Reporter: Adriano Machado
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 4.x
>
>
> Build is failing using mvnd 1.0.0
> {noformat}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3.577 s (Wall Clock)
> [INFO] Finished at: 2024-06-24T23:40:46-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.camel:sync-properties-maven-plugin:4.7.0-SNAPSHOT:sync-properties
> (default) on project camel-dependencies: camelParentPomXml
> /Users/admachad/Opensource/camel/camel-dependencies/${maven.multiModuleProjectDirectory}/parent/pom.xml
> does not exist -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20910) Build is failing with mvnd 1.0.0/1.0.1
[
https://issues.apache.org/jira/browse/CAMEL-20910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908447#comment-17908447
]
Claus Ibsen commented on CAMEL-20910:
-
Works with
Apache Maven Daemon (mvnd) 1.0.2
> Build is failing with mvnd 1.0.0/1.0.1
> --
>
> Key: CAMEL-20910
> URL: https://issues.apache.org/jira/browse/CAMEL-20910
> Project: Camel
> Issue Type: Task
> Components: tooling
>Affects Versions: 4.6.0
>Reporter: Adriano Machado
>Assignee: Guillaume Nodet
>Priority: Minor
> Fix For: 4.x
>
>
> Build is failing using mvnd 1.0.0
> {noformat}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3.577 s (Wall Clock)
> [INFO] Finished at: 2024-06-24T23:40:46-04:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.camel:sync-properties-maven-plugin:4.7.0-SNAPSHOT:sync-properties
> (default) on project camel-dependencies: camelParentPomXml
> /Users/admachad/Opensource/camel/camel-dependencies/${maven.multiModuleProjectDirectory}/parent/pom.xml
> does not exist -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command{noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-21484) DefaultPropertiesLookup loads all props from microprofile config per property value lookup
[
https://issues.apache.org/jira/browse/CAMEL-21484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908430#comment-17908430
]
Claus Ibsen edited comment on CAMEL-21484 at 12/27/24 10:50 AM:
I created a PR where the mp-config is not loadable to avoid this runtime
overhead, and it does not bring value - then its a simple adapter into quarkus
https://github.com/apache/camel/pull/16661
was (Author: davsclaus):
I created a PR where the mp-config is not loadable to avoid this runtime
overhead, and it does not bring value - then its a simple adapter into quarkus
> DefaultPropertiesLookup loads all props from microprofile config per property
> value lookup
> --
>
> Key: CAMEL-21484
> URL: https://issues.apache.org/jira/browse/CAMEL-21484
> Project: Camel
> Issue Type: Improvement
> Components: camel-microprofile-config
>Affects Versions: 4.8.1
>Reporter: Paul Blanchaert
>Priority: Minor
> Fix For: 4.10.0
>
>
> While using quarkus to run camel route, all microprofile properties are
> loaded per lookup of a property value. So when using a modest number of 10
> config values in camel routes, the current lookup loads all properties
> (including environment and system variables) 11 times.
> This happens in the method DefaultPropertiesLookup#
> doLookup(String name, String defaultValue). When a property is found (answer
> != null), then the source is determined: for the
> CamelMicroProfilePropertiesSource, the routine performs the loadProperties()
> function (in the block "ps instanceof LoadablePropertiesSource") to retrieve
> the "source" string for the retrieved value. This is set when "
> prop instanceof OrderedLocationProperties". For this
> CamelMicroProfilePropertiesSource, this prop is not an instanceof
> OrderedLocationProperties, and so the result of the loadProperties call is
> never used and hence should be avoided.
> This can be illustrated with the following setup with 3 mymsg properties:
> route.yaml:
> {{- from:}}
> {{ uri: "timer:myyaml"}}
> {{ steps:}}
> {{ - log:}}
> {{ message: 'Message \{{mymsg}} \{{mymsg2:msg2}} \{{mymsg3:msg3}}
> \{{mymsg4:msg4}}'}}
>
> application.properties:
> {{quarkus.config.log.values=true}}
> {{quarkus.log.level=info}}
> {{quarkus.log.category."org.apache.camel.main".level=DEBUG}}
> {{quarkus.log.category."org.apache.camel.component.properties".level=DEBUG}}
> {{quarkus.log.category."io.smallrye.config".level=DEBUG}}
> {{camel.main.routes-include-pattern=camel/route.yaml}}
> {{mymsg=test1}}
> {{mymsg2=test2}}
> {{mymsg3=test3}}
>
> {{-> % quarkus run -B | grep mymsg}}
> {{2024-11-28 10:22:58,942 DEBUG [org.apa.cam.mai.RoutesConfigurer] (main)
> Adding templated routes into CamelContext from RoutesBuilder: Routes:
> [Route[From[timer:myyaml] -> [Log[Message \{{mymsg}} \{{mymsg2:msg2}}
> \{{mymsg3:msg3}} \{{mymsg4:msg4}}}}
> {{2024-11-28 10:22:58,958 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:12
> with the value test1}}
> {{2024-11-28 10:22:58,960 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:12
> with the value test1}}
> {{2024-11-28 10:22:58,960 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg2 was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:13
> with the value test2}}
> {{2024-11-28 10:22:58,960 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg3 was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:14
> with the value test3}}
> {{2024-11-28 10:22:58,966 DEBUG [org.apa.cam.com.pro.DefaultPropertiesParser]
> (main) Found property: mymsg with value: test1 to be used.}}
> {{2024-11-28 10:22:58,966 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg2 was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:13
> with the value test2}}
> {{2024-11-28 10:22:58,966 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:12
> with the value test1}}
> {{2024-11-28 10:22:58,967 DEBUG [io.sma.config] (main) SRCFG01001: Th
[jira] [Assigned] (CAMEL-21484) DefaultPropertiesLookup loads all props from microprofile config per property value lookup
[
https://issues.apache.org/jira/browse/CAMEL-21484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-21484:
---
Assignee: Claus Ibsen
> DefaultPropertiesLookup loads all props from microprofile config per property
> value lookup
> --
>
> Key: CAMEL-21484
> URL: https://issues.apache.org/jira/browse/CAMEL-21484
> Project: Camel
> Issue Type: Improvement
> Components: camel-microprofile-config
>Affects Versions: 4.8.1
>Reporter: Paul Blanchaert
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 4.10.0
>
>
> While using quarkus to run camel route, all microprofile properties are
> loaded per lookup of a property value. So when using a modest number of 10
> config values in camel routes, the current lookup loads all properties
> (including environment and system variables) 11 times.
> This happens in the method DefaultPropertiesLookup#
> doLookup(String name, String defaultValue). When a property is found (answer
> != null), then the source is determined: for the
> CamelMicroProfilePropertiesSource, the routine performs the loadProperties()
> function (in the block "ps instanceof LoadablePropertiesSource") to retrieve
> the "source" string for the retrieved value. This is set when "
> prop instanceof OrderedLocationProperties". For this
> CamelMicroProfilePropertiesSource, this prop is not an instanceof
> OrderedLocationProperties, and so the result of the loadProperties call is
> never used and hence should be avoided.
> This can be illustrated with the following setup with 3 mymsg properties:
> route.yaml:
> {{- from:}}
> {{ uri: "timer:myyaml"}}
> {{ steps:}}
> {{ - log:}}
> {{ message: 'Message \{{mymsg}} \{{mymsg2:msg2}} \{{mymsg3:msg3}}
> \{{mymsg4:msg4}}'}}
>
> application.properties:
> {{quarkus.config.log.values=true}}
> {{quarkus.log.level=info}}
> {{quarkus.log.category."org.apache.camel.main".level=DEBUG}}
> {{quarkus.log.category."org.apache.camel.component.properties".level=DEBUG}}
> {{quarkus.log.category."io.smallrye.config".level=DEBUG}}
> {{camel.main.routes-include-pattern=camel/route.yaml}}
> {{mymsg=test1}}
> {{mymsg2=test2}}
> {{mymsg3=test3}}
>
> {{-> % quarkus run -B | grep mymsg}}
> {{2024-11-28 10:22:58,942 DEBUG [org.apa.cam.mai.RoutesConfigurer] (main)
> Adding templated routes into CamelContext from RoutesBuilder: Routes:
> [Route[From[timer:myyaml] -> [Log[Message \{{mymsg}} \{{mymsg2:msg2}}
> \{{mymsg3:msg3}} \{{mymsg4:msg4}}}}
> {{2024-11-28 10:22:58,958 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:12
> with the value test1}}
> {{2024-11-28 10:22:58,960 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:12
> with the value test1}}
> {{2024-11-28 10:22:58,960 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg2 was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:13
> with the value test2}}
> {{2024-11-28 10:22:58,960 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg3 was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:14
> with the value test3}}
> {{2024-11-28 10:22:58,966 DEBUG [org.apa.cam.com.pro.DefaultPropertiesParser]
> (main) Found property: mymsg with value: test1 to be used.}}
> {{2024-11-28 10:22:58,966 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg2 was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:13
> with the value test2}}
> {{2024-11-28 10:22:58,966 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:12
> with the value test1}}
> {{2024-11-28 10:22:58,967 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg2 was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:13
> with the value test2}}
> {{2024-11-28 10:22:58,967 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg3 was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/appli
[jira] [Commented] (CAMEL-21484) DefaultPropertiesLookup loads all props from microprofile config per property value lookup
[
https://issues.apache.org/jira/browse/CAMEL-21484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908430#comment-17908430
]
Claus Ibsen commented on CAMEL-21484:
-
I created a PR where the mp-config is not loadable to avoid this runtime
overhead, and it does not bring value - then its a simple adapter into quarkus
> DefaultPropertiesLookup loads all props from microprofile config per property
> value lookup
> --
>
> Key: CAMEL-21484
> URL: https://issues.apache.org/jira/browse/CAMEL-21484
> Project: Camel
> Issue Type: Improvement
> Components: camel-microprofile-config
>Affects Versions: 4.8.1
>Reporter: Paul Blanchaert
>Priority: Minor
> Fix For: 4.10.0
>
>
> While using quarkus to run camel route, all microprofile properties are
> loaded per lookup of a property value. So when using a modest number of 10
> config values in camel routes, the current lookup loads all properties
> (including environment and system variables) 11 times.
> This happens in the method DefaultPropertiesLookup#
> doLookup(String name, String defaultValue). When a property is found (answer
> != null), then the source is determined: for the
> CamelMicroProfilePropertiesSource, the routine performs the loadProperties()
> function (in the block "ps instanceof LoadablePropertiesSource") to retrieve
> the "source" string for the retrieved value. This is set when "
> prop instanceof OrderedLocationProperties". For this
> CamelMicroProfilePropertiesSource, this prop is not an instanceof
> OrderedLocationProperties, and so the result of the loadProperties call is
> never used and hence should be avoided.
> This can be illustrated with the following setup with 3 mymsg properties:
> route.yaml:
> {{- from:}}
> {{ uri: "timer:myyaml"}}
> {{ steps:}}
> {{ - log:}}
> {{ message: 'Message \{{mymsg}} \{{mymsg2:msg2}} \{{mymsg3:msg3}}
> \{{mymsg4:msg4}}'}}
>
> application.properties:
> {{quarkus.config.log.values=true}}
> {{quarkus.log.level=info}}
> {{quarkus.log.category."org.apache.camel.main".level=DEBUG}}
> {{quarkus.log.category."org.apache.camel.component.properties".level=DEBUG}}
> {{quarkus.log.category."io.smallrye.config".level=DEBUG}}
> {{camel.main.routes-include-pattern=camel/route.yaml}}
> {{mymsg=test1}}
> {{mymsg2=test2}}
> {{mymsg3=test3}}
>
> {{-> % quarkus run -B | grep mymsg}}
> {{2024-11-28 10:22:58,942 DEBUG [org.apa.cam.mai.RoutesConfigurer] (main)
> Adding templated routes into CamelContext from RoutesBuilder: Routes:
> [Route[From[timer:myyaml] -> [Log[Message \{{mymsg}} \{{mymsg2:msg2}}
> \{{mymsg3:msg3}} \{{mymsg4:msg4}}}}
> {{2024-11-28 10:22:58,958 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:12
> with the value test1}}
> {{2024-11-28 10:22:58,960 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:12
> with the value test1}}
> {{2024-11-28 10:22:58,960 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg2 was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:13
> with the value test2}}
> {{2024-11-28 10:22:58,960 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg3 was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:14
> with the value test3}}
> {{2024-11-28 10:22:58,966 DEBUG [org.apa.cam.com.pro.DefaultPropertiesParser]
> (main) Found property: mymsg with value: test1 to be used.}}
> {{2024-11-28 10:22:58,966 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg2 was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:13
> with the value test2}}
> {{2024-11-28 10:22:58,966 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:12
> with the value test1}}
> {{2024-11-28 10:22:58,967 DEBUG [io.sma.config] (main) SRCFG01001: The config
> mymsg2 was loaded from
> PropertiesConfigSource[source=jar:file:///private/tmp/test1/target/quarkus-app/app/test1-1.0.0-SNAPSHOT.jar!/application.properties]:13
> with the value test2}}
> {{2024-11-28 10:22:58,967 DEBUG [io.sma.config] (main) SRCFG01001: The config
[jira] [Updated] (CAMEL-21095) camel-core - Make it easier to configure SSL using XML and YAML DSL
[ https://issues.apache.org/jira/browse/CAMEL-21095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-21095: Fix Version/s: 4.10.0 (was: 4.x) > camel-core - Make it easier to configure SSL using XML and YAML DSL > --- > > Key: CAMEL-21095 > URL: https://issues.apache.org/jira/browse/CAMEL-21095 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.10.0 > > > You can configure this in classic XML DSL (spring) (see CAMEL-20774) and in > camel-main/SB you can configure this via properties in camel.ssl. > However it would be great to have it first-class in XML IO and YAML DSL as > well so its easier to configure there also and for tooling. Configure SSL is > complex and this can help with better tooling assistance. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-21102) camel-aws-s3 - Add support for conditional writes in put object calls
[ https://issues.apache.org/jira/browse/CAMEL-21102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908474#comment-17908474 ] Claus Ibsen commented on CAMEL-21102: - Andrea, did we already implement this ? > camel-aws-s3 - Add support for conditional writes in put object calls > - > > Key: CAMEL-21102 > URL: https://issues.apache.org/jira/browse/CAMEL-21102 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Reporter: Claus Ibsen >Priority: Minor > Fix For: 4.x > > > https://aws.amazon.com/about-aws/whats-new/2024/08/amazon-s3-conditional-writes/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19665) components that are polling can become batch polling
[ https://issues.apache.org/jira/browse/CAMEL-19665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19665. - Fix Version/s: 4.10.0 (was: 4.x) Resolution: Fixed > components that are polling can become batch polling > > > Key: CAMEL-19665 > URL: https://issues.apache.org/jira/browse/CAMEL-19665 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.10.0 > > > There are some components that uses ScheduledPollingConsumer that essentially > do their own kind of batch. > Instead they can be changed to ScheduledBatchPollingConsumer and do batch the > standard Camel way. > - camel-couchbase > - camel-git > - camel-github > - camel-hdfs > - camel-jira > and maybe some others, search for ScheduledPollingConsumer to find more. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19665) components that are polling can become batch polling
[ https://issues.apache.org/jira/browse/CAMEL-19665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908473#comment-17908473 ] Claus Ibsen commented on CAMEL-19665: - camel-couchbase *DONE* > components that are polling can become batch polling > > > Key: CAMEL-19665 > URL: https://issues.apache.org/jira/browse/CAMEL-19665 > Project: Camel > Issue Type: Improvement >Reporter: Claus Ibsen >Assignee: Guillaume Nodet >Priority: Major > Fix For: 4.x > > > There are some components that uses ScheduledPollingConsumer that essentially > do their own kind of batch. > Instead they can be changed to ScheduledBatchPollingConsumer and do batch the > standard Camel way. > - camel-couchbase > - camel-git > - camel-github > - camel-hdfs > - camel-jira > and maybe some others, search for ScheduledPollingConsumer to find more. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21480) camel-microprofile-config: Add support in CamelMicroProfilePropertiesSource for multiple profile properties
[ https://issues.apache.org/jira/browse/CAMEL-21480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Blanchaert updated CAMEL-21480: Description: Currently this PropertiesSource allows for properties that include one profile as in "%profile1.config-key=value". The goal is to add support for multiple profile properties, with a comma-separated list of profile names as in "%profile1,profile2.config-key=value". See also: - Quarkus: [multiple-profiles|https://quarkus.io/guides/config-reference#multiple-profiles] - Smallrye: [multiple-profiles|https://smallrye.io/smallrye-config/3.10.1/config/profiles/#multiple-profiles] was: Currently this PropertiesSource allows for properties that include one profile as in "%profile1.config-key=value". The goal is to add support for multiple profile properties, with a comma-separated list of profile names as in "%profile1,%profile2.config-key=value" > camel-microprofile-config: Add support in CamelMicroProfilePropertiesSource > for multiple profile properties > --- > > Key: CAMEL-21480 > URL: https://issues.apache.org/jira/browse/CAMEL-21480 > Project: Camel > Issue Type: Improvement > Components: camel-microprofile-config >Affects Versions: 4.8.1 >Reporter: Paul Blanchaert >Priority: Minor > > Currently this PropertiesSource allows for properties that include one > profile as in "%profile1.config-key=value". > The goal is to add support for multiple profile properties, with a > comma-separated list of profile names as in > "%profile1,profile2.config-key=value". > See also: > - Quarkus: > [multiple-profiles|https://quarkus.io/guides/config-reference#multiple-profiles] > - Smallrye: > [multiple-profiles|https://smallrye.io/smallrye-config/3.10.1/config/profiles/#multiple-profiles] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-21571) camel-mina - Upgrade to 2.2.4
[ https://issues.apache.org/jira/browse/CAMEL-21571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-21571. - Resolution: Fixed > camel-mina - Upgrade to 2.2.4 > - > > Key: CAMEL-21571 > URL: https://issues.apache.org/jira/browse/CAMEL-21571 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-mina >Affects Versions: 4.4.4, 4.8.2 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.4.5, 4.8.3, 4.10.0 > > > h4. [Announce] Apache MINA 2.0.27, 2.1.0 and 2.2.4 release > The MINA project is pleased to announce the MINA 2.2.4, 2.1.10 and 2.0.27 > release. **MINA** applications using unbounded deserialization may allow > **RCE** (see [https://www.cve.org/CVERecord?id=CVE-2024-52046]). Affected > versions: - Apache MINA 2.0 through 2.0.26 - Apache MINA 2.1 through 2.1.9 - > Apache MINA 2.2 through 2.2.3 Description: The *ObjectSerializationDecoder* > in Apache **MINA** uses Java’s native deserialization protocol to process > incoming serialized data but lacks the necessary security checks and > defenses. This vulnerability allows attackers to exploit the deserialization > process by sending specially crafted malicious serialized data, potentially > leading to remote code execution (**RCE**) attacks. This issue affects > **MINA** core versions 2.0.X, 2.1.X and 2.2.X, and is fixed by the releases > 2.0.27, 2.1.10 and 2.2.4. It's also important to note that an application > using **MINA** core library will only be affected if the > *IoBuffer#getObject()* method is called, and this specific method is > potentially called when adding a *ProtocolCodecFilter* instance using the > *ObjectSerializationCodecFactory* class in the filter chain. If your > application is specifically using those classes, you have to upgrade to the > latest version of **MINA** core library. **Upgrading will not be enough: you > also need to explicitly allow the classes the decoder will accept in the > *ObjectSerializationDecoder* instance, using one of the three new methods:** -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-21570) Add Profile to skip Tests for ppc64le Architecture in aws2
[
https://issues.apache.org/jira/browse/CAMEL-21570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-21570:
Fix Version/s: 4.10.0
> Add Profile to skip Tests for ppc64le Architecture in aws2
> ---
>
> Key: CAMEL-21570
> URL: https://issues.apache.org/jira/browse/CAMEL-21570
> Project: Camel
> Issue Type: Task
> Components: camel-spring-boot
>Reporter: Anushka Juli
>Priority: Minor
> Fix For: 4.10.0
>
> Attachments: ppc64le_aws2_cw_main_build_success_logs.txt,
> ppc64le_aws2_ddb_main_build_success_logs.txt,
> ppc64le_aws2_kinesis_main_build_success_logs.txt,
> ppc64le_aws2_s3_main_build_success_logs.txt,
> ppc64le_aws2_sns_main_build_success_logs.txt,
> ppc64le_aws2_sqs_main_build_success_logs.txt, x86_aws2_cw_build.txt,
> x86_aws2_ddb_build.txt, x86_aws2_kinesis_build.txt, x86_aws2_s3_build.txt,
> x86_aws2_sns_build.txt, x86_aws2_sqs_build.txt
>
>
> {*}camel-aws2-cw-starter{*}, {*}camel-aws2-ddb-starter{*},
> {*}camel-aws2-kinesis-starter{*}, {*}camel-aws2-s3-starter{*},
> {*}camel-aws2-sns-starter{*}, *camel-aws2-sqs-starter* modules currently
> fails Upstream CI builds on the ppc64le architecture due to the lack of a
> supported aws-v2 image for ppc64le. To prevent these failures, the test cases
> should be disabled on this architecture
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21570) Add Profile to skip Tests for ppc64le Architecture in aws2
[
https://issues.apache.org/jira/browse/CAMEL-21570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21570.
-
Resolution: Fixed
> Add Profile to skip Tests for ppc64le Architecture in aws2
> ---
>
> Key: CAMEL-21570
> URL: https://issues.apache.org/jira/browse/CAMEL-21570
> Project: Camel
> Issue Type: Task
> Components: camel-spring-boot
>Reporter: Anushka Juli
>Priority: Minor
> Fix For: 4.10.0
>
> Attachments: ppc64le_aws2_cw_main_build_success_logs.txt,
> ppc64le_aws2_ddb_main_build_success_logs.txt,
> ppc64le_aws2_kinesis_main_build_success_logs.txt,
> ppc64le_aws2_s3_main_build_success_logs.txt,
> ppc64le_aws2_sns_main_build_success_logs.txt,
> ppc64le_aws2_sqs_main_build_success_logs.txt, x86_aws2_cw_build.txt,
> x86_aws2_ddb_build.txt, x86_aws2_kinesis_build.txt, x86_aws2_s3_build.txt,
> x86_aws2_sns_build.txt, x86_aws2_sqs_build.txt
>
>
> {*}camel-aws2-cw-starter{*}, {*}camel-aws2-ddb-starter{*},
> {*}camel-aws2-kinesis-starter{*}, {*}camel-aws2-s3-starter{*},
> {*}camel-aws2-sns-starter{*}, *camel-aws2-sqs-starter* modules currently
> fails Upstream CI builds on the ppc64le architecture due to the lack of a
> supported aws-v2 image for ppc64le. To prevent these failures, the test cases
> should be disabled on this architecture
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-21572) Camel JBang with --runtime=spring-boot throw NullPointerException
[
https://issues.apache.org/jira/browse/CAMEL-21572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-21572.
-
Resolution: Fixed
Thanks for reporting and the PR
> Camel JBang with --runtime=spring-boot throw NullPointerException
> -
>
> Key: CAMEL-21572
> URL: https://issues.apache.org/jira/browse/CAMEL-21572
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.8.2, 4.9.0
>Reporter: Bartosz Popiela
>Priority: Minor
> Fix For: 4.8.3, 4.10.0
>
>
> SetHeader with a simple expression causes NullPointerException to be thrown
> because for runtime other than default (kamelet-main) JBang uses Stub instead
> of the actual component which produces null.
> {code:java}
> PS> jbang "-Dcamel.jbang.version=4.8.0" camel@apache/camel run *
> --runtime=spring-boot
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> route-603e at: >>> SetHeader[SampleUUID, simple{This is a sample UUID:
> ${bean:type:java.util.UUID?method=randomUUID}}] <<< in route:
> Route(route-603e)[From[timer:oneTimeTimer?delay=0&repeatCoun... because of
> Cannot invoke "Object.toString()" because "value" is null
> at
> org.apache.camel.reifier.RouteReifier.doCreateRoute(RouteReifier.java:235)
> at
> org.apache.camel.reifier.RouteReifier.createRoute(RouteReifier.java:86)
> at
> org.apache.camel.impl.DefaultModelReifierFactory.createRoute(DefaultModelReifierFactory.java:49)
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:726)
> at
> org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:592)
> at
> org.apache.camel.impl.engine.AbstractCamelContext.doInit(AbstractCamelContext.java:2433)
> at
> org.apache.camel.support.service.BaseService.init(BaseService.java:85)
> at
> org.apache.camel.impl.engine.AbstractCamelContext.init(AbstractCamelContext.java:2068)
> at
> org.apache.camel.support.service.BaseService.start(BaseService.java:115)
> at
> org.apache.camel.impl.engine.AbstractCamelContext.start(AbstractCamelContext.java:2087)
> at
> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:211)
> at org.apache.camel.main.KameletMain.doStart(KameletMain.java:373)
> at
> org.apache.camel.support.service.BaseService.start(BaseService.java:123)
> at
> org.apache.camel.dsl.jbang.core.commands.Run.runKameletMain(Run.java:1348)
> at org.apache.camel.dsl.jbang.core.commands.Run.run(Run.java:864)
> at
> org.apache.camel.dsl.jbang.core.commands.Run.runExport(Run.java:330)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportBaseCommand.runSilently(ExportBaseCommand.java:318)
> at
> org.apache.camel.dsl.jbang.core.commands.ExportSpringBoot.export(ExportSpringBoot.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.Run.runSpringBoot(Run.java:988)
> at org.apache.camel.dsl.jbang.core.commands.Run.run(Run.java:416)
> at org.apache.camel.dsl.jbang.core.commands.Run.doCall(Run.java:319)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:71)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelCommand.call(CamelCommand.java:37)
> at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
> at picocli.CommandLine.access$1500(CommandLine.java:148)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
> at picocli.CommandLine.execute(CommandLine.java:2174)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:173)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:62)
> at main.CamelJBang.main(CamelJBang.java:36)
> Caused by: java.lang.NullPointerException: Cannot invoke "Object.toString()"
> because "value" is null
> at
> org.apache.camel.support.builder.ExpressionBuilder$62.init(ExpressionBuilder.java:2126)
> at
> org.apache.camel.reifier.language.ExpressionReifier.createExpression(ExpressionReifier.java:183)
> at
> org.apache.camel.reifier.AbstractReifier.createExpression(AbstractReifier.java:119)
> at
> org.apache.camel.reifier.SetHeaderReifier.createProcessor(SetHeaderReifier.java:37)
> at
> org.a
