[jira] [Comment Edited] (CAMEL-17641) camel-catalog - Generate metadata for all known implementations of camel SPI interfaces
[ https://issues.apache.org/jira/browse/CAMEL-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828317#comment-17828317 ] Claus Ibsen edited comment on CAMEL-17641 at 3/20/24 6:31 AM: -- TODO: camel-sql aggregation repository *DONE* TODO: fix interfaceType not correct for some of beans *DONE* was (Author: davsclaus): TODO: camel-sql aggregation repository *DONE* TODO: fix interfaceType not correct for some of beans > camel-catalog - Generate metadata for all known implementations of camel SPI > interfaces > --- > > Key: CAMEL-17641 > URL: https://issues.apache.org/jira/browse/CAMEL-17641 > Project: Camel > Issue Type: New Feature > Components: camel-catalog >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.5.0 > > > For example AggregationStrategy can have a set of OOTB impls, and it would be > good to know what we have in camel. > We can make this metadata generated per component then it can be isolated per > component you use - and maybe also have this in the camel-catalog so we have > a single place to look -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20583) Java 21 - Reduce the noise from the ThreadType logger
Claus Ibsen created CAMEL-20583: --- Summary: Java 21 - Reduce the noise from the ThreadType logger Key: CAMEL-20583 URL: https://issues.apache.org/jira/browse/CAMEL-20583 Project: Camel Issue Type: Improvement Components: camel-core Reporter: Claus Ibsen Fix For: 4.5.0 The virtual thread stuff is experimental and we should only log if its enabled explicit and otherwise log at DEBUG level the default level in ThreadType -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-17641) camel-catalog - Generate metadata for all known implementations of camel SPI interfaces
[ https://issues.apache.org/jira/browse/CAMEL-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827138#comment-17827138 ] Claus Ibsen edited comment on CAMEL-17641 at 3/20/24 6:05 AM: -- TODO: mojo to generate json *DONE* TODO: markup various beans such as aggregation strategy *DONE* TODO: copy jsons into camel-catalog *DONE* TODO: markup more beans from other components (camel-zipfile as example) TODO: camel-jbang can use the catalog to map FQN classname to JAR *DONE* TODO: generate configurer for reflection-free *DONE* TODO: markup all aggregation strategies *DONE* TODO: markup all idempotent repositories *DONE* TODO: markup all aggregation repositories *DONE* was (Author: davsclaus): TODO: mojo to generate json *DONE* TODO: markup various beans such as aggregation strategy *DONE* TODO: copy jsons into camel-catalog *DONE* TODO: markup more beans from other components (camel-zipfile as example) TODO: camel-jbang can use the catalog to map FQN classname to JAR *DONE* TODO: generate configurer for reflection-free *DONE* TODO: markup all aggregation strategies *DONE* TODO: markup all idempotent repositories *DONE* TODO: markup all aggregation repositories > camel-catalog - Generate metadata for all known implementations of camel SPI > interfaces > --- > > Key: CAMEL-17641 > URL: https://issues.apache.org/jira/browse/CAMEL-17641 > Project: Camel > Issue Type: New Feature > Components: camel-catalog >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.5.0 > > > For example AggregationStrategy can have a set of OOTB impls, and it would be > good to know what we have in camel. > We can make this metadata generated per component then it can be isolated per > component you use - and maybe also have this in the camel-catalog so we have > a single place to look -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-17641) camel-catalog - Generate metadata for all known implementations of camel SPI interfaces
[ https://issues.apache.org/jira/browse/CAMEL-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828317#comment-17828317 ] Claus Ibsen edited comment on CAMEL-17641 at 3/20/24 6:05 AM: -- TODO: camel-sql aggregation repository *DONE* TODO: fix interfaceType not correct for some of beans was (Author: davsclaus): TODO: camel-sql aggregation repository TODO: fix interfaceType not correct for some of beans > camel-catalog - Generate metadata for all known implementations of camel SPI > interfaces > --- > > Key: CAMEL-17641 > URL: https://issues.apache.org/jira/browse/CAMEL-17641 > Project: Camel > Issue Type: New Feature > Components: camel-catalog >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.5.0 > > > For example AggregationStrategy can have a set of OOTB impls, and it would be > good to know what we have in camel. > We can make this metadata generated per component then it can be isolated per > component you use - and maybe also have this in the camel-catalog so we have > a single place to look -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20582) No encoding is known for map entry value of type for header CamelAzureEventHubsEnqueuedTime
Vishal Bihani created CAMEL-20582:
-
Summary: No encoding is known for map entry value of type for
header CamelAzureEventHubsEnqueuedTime
Key: CAMEL-20582
URL: https://issues.apache.org/jira/browse/CAMEL-20582
Project: Camel
Issue Type: Bug
Components: camel-azure-eventhubs
Affects Versions: 4.4.0
Reporter: Vishal Bihani
Attachments: e1.png, e2.png, logs.txt
Camel azure event hub connector internally sets a header
'{*}CamelAzureEventHubsEnqueuedTime{*}' which is of type
'{*}java.time.Instant{*}'. But the underlying library Apache Qpid Proton does
not support this type which results in error when producing messages to event
hub.
Current workaround is to remove this header from exchange before producing the
message to event hub.
Refer attachments for screenshot and logs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20524) Harmonize camel main configuration properties across runtimes
[ https://issues.apache.org/jira/browse/CAMEL-20524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828457#comment-17828457 ] Guillaume Nodet commented on CAMEL-20524: - Fixed in camel-spring-boot with https://github.com/apache/camel-spring-boot/pull/1113. > Harmonize camel main configuration properties across runtimes > - > > Key: CAMEL-20524 > URL: https://issues.apache.org/jira/browse/CAMEL-20524 > Project: Camel > Issue Type: Improvement > Components: camel-main, camel-quarkus, camel-spring-boot, > camel-spring-boot-starters >Reporter: Luca Burgazzoli >Assignee: Guillaume Nodet >Priority: Minor > > The camel-main module was originally designed to run make it easy to run > camel standalone without the need of a specific runtime (spring-boot, > quarkus, etc), but now camel-main is also a core component of camel-quarkus > and camel-spring-boot. > camel-main also offers a number of properties that can be configured to > configure camel-main, however, the runtimes may use some slight different > property naming/namespaces making things a little bit confusing. > As an example, camel-main defines a camel.main.routes-include-pattern > property to let camel discover routes, however in camel-spring-boot the same > property is camel.springboot..routes-include-pattern > Ideally, runtimes should honor camel-main property and reserve some specific > namespaces (i.e. camel.quarkus camel.springboot) for runtime specific options. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (CAMEL-20524) Harmonize camel main configuration properties across runtimes
[ https://issues.apache.org/jira/browse/CAMEL-20524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-20524 started by Guillaume Nodet. --- > Harmonize camel main configuration properties across runtimes > - > > Key: CAMEL-20524 > URL: https://issues.apache.org/jira/browse/CAMEL-20524 > Project: Camel > Issue Type: Improvement > Components: camel-main, camel-quarkus, camel-spring-boot, > camel-spring-boot-starters >Reporter: Luca Burgazzoli >Assignee: Guillaume Nodet >Priority: Minor > > The camel-main module was originally designed to run make it easy to run > camel standalone without the need of a specific runtime (spring-boot, > quarkus, etc), but now camel-main is also a core component of camel-quarkus > and camel-spring-boot. > camel-main also offers a number of properties that can be configured to > configure camel-main, however, the runtimes may use some slight different > property naming/namespaces making things a little bit confusing. > As an example, camel-main defines a camel.main.routes-include-pattern > property to let camel discover routes, however in camel-spring-boot the same > property is camel.springboot..routes-include-pattern > Ideally, runtimes should honor camel-main property and reserve some specific > namespaces (i.e. camel.quarkus camel.springboot) for runtime specific options. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-20524) Harmonize camel main configuration properties across runtimes
[ https://issues.apache.org/jira/browse/CAMEL-20524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guillaume Nodet reassigned CAMEL-20524: --- Assignee: Guillaume Nodet > Harmonize camel main configuration properties across runtimes > - > > Key: CAMEL-20524 > URL: https://issues.apache.org/jira/browse/CAMEL-20524 > Project: Camel > Issue Type: Improvement > Components: camel-main, camel-quarkus, camel-spring-boot, > camel-spring-boot-starters >Reporter: Luca Burgazzoli >Assignee: Guillaume Nodet >Priority: Minor > > The camel-main module was originally designed to run make it easy to run > camel standalone without the need of a specific runtime (spring-boot, > quarkus, etc), but now camel-main is also a core component of camel-quarkus > and camel-spring-boot. > camel-main also offers a number of properties that can be configured to > configure camel-main, however, the runtimes may use some slight different > property naming/namespaces making things a little bit confusing. > As an example, camel-main defines a camel.main.routes-include-pattern > property to let camel discover routes, however in camel-spring-boot the same > property is camel.springboot..routes-include-pattern > Ideally, runtimes should honor camel-main property and reserve some specific > namespaces (i.e. camel.quarkus camel.springboot) for runtime specific options. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-17641) camel-catalog - Generate metadata for all known implementations of camel SPI interfaces
[ https://issues.apache.org/jira/browse/CAMEL-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828317#comment-17828317 ] Claus Ibsen edited comment on CAMEL-17641 at 3/19/24 3:25 PM: -- TODO: camel-sql aggregation repository TODO: fix interfaceType not correct for some of beans was (Author: davsclaus): TODO: camel-sql aggregation repository > camel-catalog - Generate metadata for all known implementations of camel SPI > interfaces > --- > > Key: CAMEL-17641 > URL: https://issues.apache.org/jira/browse/CAMEL-17641 > Project: Camel > Issue Type: New Feature > Components: camel-catalog >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.5.0 > > > For example AggregationStrategy can have a set of OOTB impls, and it would be > good to know what we have in camel. > We can make this metadata generated per component then it can be isolated per > component you use - and maybe also have this in the camel-catalog so we have > a single place to look -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-20559) camel-jbang-plugin-k run command error on a multi-valued trait property
[
https://issues.apache.org/jira/browse/CAMEL-20559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claudio Miranda resolved CAMEL-20559.
-
Resolution: Fixed
> camel-jbang-plugin-k run command error on a multi-valued trait property
> ---
>
> Key: CAMEL-20559
> URL: https://issues.apache.org/jira/browse/CAMEL-20559
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.4.0
> Environment: Jbang version : 0.114.0
> Camel version: 4.4.0
>Reporter: Gaëlle Fournier
>Assignee: Claudio Miranda
>Priority: Minor
>
> Trying to execute the `run` command with trait property `-t
> toleration.taints=camel.apache.org/master:NoExecute:300` results in the
> following parsing error:
>
> {code:java}
> $ jbang run --deps=org.apache.camel:camel-jbang-plugin-k:4.4.0
> camel@apache/camel k run Test.java -t toleration.enabled=true -t
> toleration.taints=camel.apache.org/master:NoExecute:300
> org.apache.camel.RuntimeCamelException: Failed to parse trait options at
> org.apache.camel.dsl.jbang.core.commands.k.TraitHelper.parseTraits(TraitHelper.java:81)
> at
> org.apache.camel.dsl.jbang.core.commands.k.IntegrationRun.doCall(IntegrationRun.java:237)
> 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:2041) at
> picocli.CommandLine.access$1500(CommandLine.java:148) at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2461)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2453) at
> picocli.CommandLine$RunLast.handle(CommandLine.java:2415) at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2273)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2417) at
> picocli.CommandLine.execute(CommandLine.java:2170) at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:151)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:58)
> at main.CamelJBang.main(CamelJBang.java:36) Caused by:
> com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot construct
> instance of `java.util.ArrayList` (although at least one Creator exists): no
> String-argument constructor/factory method to deserialize from String value
> ('camel.apache.org/master:NoExecute:300') at [Source: REDACTED
> (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 1, column:
> 25] (through reference chain:
> org.apache.camel.v1.integrationspec.Traits["toleration"]->org.apache.camel.v1.integrationspec.traits.Toleration["taints"])
> at
> com.fasterxml.jackson.databind.exc.MismatchedInputException.from(MismatchedInputException.java:63)
> at
> com.fasterxml.jackson.databind.DeserializationContext.reportInputMismatch(DeserializationContext.java:1754)
> at
> com.fasterxml.jackson.databind.DeserializationContext.handleMissingInstantiator(DeserializationContext.java:1379)
> at
> com.fasterxml.jackson.databind.deser.std.StdDeserializer._deserializeFromString(StdDeserializer.java:311)
> at
> com.fasterxml.jackson.databind.deser.std.StringCollectionDeserializer.handleNonArray(StringCollectionDeserializer.java:286)
> at
> com.fasterxml.jackson.databind.deser.std.StringCollectionDeserializer.deserialize(StringCollectionDeserializer.java:194)
> at
> com.fasterxml.jackson.databind.deser.std.StringCollectionDeserializer.deserialize(StringCollectionDeserializer.java:184)
> at
> com.fasterxml.jackson.databind.deser.std.StringCollectionDeserializer.deserialize(StringCollectionDeserializer.java:27)
> at
> com.fasterxml.jackson.databind.deser.impl.MethodProperty.deserializeAndSet(MethodProperty.java:129)
> at
> com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:310)
> at
> com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:177)
> at
> com.fasterxml.jackson.databind.deser.impl.MethodProperty.deserializeAndSet(MethodProperty.java:129)
> at
> com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:310)
> at
> com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:177)
> at
> com.fasterxml.jackson.databind.deser.DefaultDeserializationContext.readRootValue(DefaultDeserializationContext.java:342)
> at
> com.fasterxml.jackson.databind.ObjectReader._bindAndClose(ObjectReader.java:2125)
> at
> com.fasterxml.jackson.databind.ObjectReader.readValue(ObjectReader.java:1566)
> at
> org.apache.camel.dsl.jbang.core.commands.k.TraitHelper.parseTraits(TraitHelper.java:78)
> ... 14
[jira] [Updated] (CAMEL-20576) camel-jbang-plugin-k run command kebab-case parsing invalid
[
https://issues.apache.org/jira/browse/CAMEL-20576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claudio Miranda updated CAMEL-20576:
Description:
The run command ignore the kebab-case trait properties.
The jbang camel k command:
{code:java}
$ camel k run files/Java.java -t affinity.enabled=true -t
"affinity.node-affinity-labels=kubernetes.io/hostname in(minikube)"{code}
will result in the following integration CRD configuration:
{code:java}
traits:
affinity:
enabled: true
podAffinity: false
podAntiAffinity: false{code}
In comparaison the kamel command:
{code:java}
$ kamel run files/Java.java -t affinity.enabled=true -t
"affinity.node-affinity-labels=kubernetes.io/hostname in(minikube)"
{code}
will result in the following integration CRD configuration:
{code:java}
traits:
affinity:
enabled: true
nodeAffinityLabels:
- kubernetes.io/hostname in(minikube){code}
*Note:* using the camel case in the jbang camel k command should be a
workaround after fix https://issues.apache.org/jira/browse/CAMEL-20559:
{code:java}
$ camel k run files/Java.java -t affinity.enabled=true -t
affinity.nodeAffinityLabels='kubernetes.io/hostname=minikube'{code}
was:
The run command ignore the snake-case trait properties.
The jbang camel k command:
{code:java}
$ camel k run files/Java.java -t affinity.enabled=true -t
"affinity.node-affinity-labels=kubernetes.io/hostname in(minikube)"{code}
will result in the following integration CRD configuration:
{code:java}
traits:
affinity:
enabled: true
podAffinity: false
podAntiAffinity: false{code}
In comparaison the kamel command:
{code:java}
$ kamel run files/Java.java -t affinity.enabled=true -t
"affinity.node-affinity-labels=kubernetes.io/hostname in(minikube)"
{code}
will result in the following integration CRD configuration:
{code:java}
traits:
affinity:
enabled: true
nodeAffinityLabels:
- kubernetes.io/hostname in(minikube){code}
*Note:* using the camel case in the jbang camel k command should be a
workaround after fix https://issues.apache.org/jira/browse/CAMEL-20559:
{code:java}
$ camel k run files/Java.java -t affinity.enabled=true -t
affinity.nodeAffinityLabels='kubernetes.io/hostname=minikube'{code}
> camel-jbang-plugin-k run command kebab-case parsing invalid
> ---
>
> Key: CAMEL-20576
> URL: https://issues.apache.org/jira/browse/CAMEL-20576
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.4.0, 4.4.1
> Environment: Jbang version : 0.114.0
> Camel version: 4.4.0
> Camel k: 2.3.0-SNAPSHOT
>Reporter: Gaëlle Fournier
>Assignee: Claudio Miranda
>Priority: Minor
>
> The run command ignore the kebab-case trait properties.
> The jbang camel k command:
> {code:java}
> $ camel k run files/Java.java -t affinity.enabled=true -t
> "affinity.node-affinity-labels=kubernetes.io/hostname in(minikube)"{code}
> will result in the following integration CRD configuration:
> {code:java}
> traits:
> affinity:
> enabled: true
> podAffinity: false
> podAntiAffinity: false{code}
>
> In comparaison the kamel command:
> {code:java}
> $ kamel run files/Java.java -t affinity.enabled=true -t
> "affinity.node-affinity-labels=kubernetes.io/hostname in(minikube)"
> {code}
> will result in the following integration CRD configuration:
> {code:java}
> traits:
> affinity:
> enabled: true
> nodeAffinityLabels:
> - kubernetes.io/hostname in(minikube){code}
>
> *Note:* using the camel case in the jbang camel k command should be a
> workaround after fix https://issues.apache.org/jira/browse/CAMEL-20559:
> {code:java}
> $ camel k run files/Java.java -t affinity.enabled=true -t
> affinity.nodeAffinityLabels='kubernetes.io/hostname=minikube'{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-20576) camel-jbang-plugin-k run command kebab-case parsing invalid
[
https://issues.apache.org/jira/browse/CAMEL-20576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claudio Miranda updated CAMEL-20576:
Summary: camel-jbang-plugin-k run command kebab-case parsing invalid (was:
camel-jbang-plugin-k run command snake-case parsing invalid)
> camel-jbang-plugin-k run command kebab-case parsing invalid
> ---
>
> Key: CAMEL-20576
> URL: https://issues.apache.org/jira/browse/CAMEL-20576
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 4.4.0, 4.4.1
> Environment: Jbang version : 0.114.0
> Camel version: 4.4.0
> Camel k: 2.3.0-SNAPSHOT
>Reporter: Gaëlle Fournier
>Assignee: Claudio Miranda
>Priority: Minor
>
> The run command ignore the snake-case trait properties.
> The jbang camel k command:
> {code:java}
> $ camel k run files/Java.java -t affinity.enabled=true -t
> "affinity.node-affinity-labels=kubernetes.io/hostname in(minikube)"{code}
> will result in the following integration CRD configuration:
> {code:java}
> traits:
> affinity:
> enabled: true
> podAffinity: false
> podAntiAffinity: false{code}
>
> In comparaison the kamel command:
> {code:java}
> $ kamel run files/Java.java -t affinity.enabled=true -t
> "affinity.node-affinity-labels=kubernetes.io/hostname in(minikube)"
> {code}
> will result in the following integration CRD configuration:
> {code:java}
> traits:
> affinity:
> enabled: true
> nodeAffinityLabels:
> - kubernetes.io/hostname in(minikube){code}
>
> *Note:* using the camel case in the jbang camel k command should be a
> workaround after fix https://issues.apache.org/jira/browse/CAMEL-20559:
> {code:java}
> $ camel k run files/Java.java -t affinity.enabled=true -t
> affinity.nodeAffinityLabels='kubernetes.io/hostname=minikube'{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-20581) camel-test-infra-artemis: ensure components use the correct lifecycle for service
[ https://issues.apache.org/jira/browse/CAMEL-20581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-20581. -- Fix Version/s: 4.5.0 Resolution: Fixed Fixed with the linked PR. > camel-test-infra-artemis: ensure components use the correct lifecycle for > service > - > > Key: CAMEL-20581 > URL: https://issues.apache.org/jira/browse/CAMEL-20581 > Project: Camel > Issue Type: Test > Components: camel-test-infra-artemis >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 4.5.0 > > > We still have a few components failing to declare the Artemis service as > static during tests. This can lead to instabilities and flakiness. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-17641) camel-catalog - Generate metadata for all known implementations of camel SPI interfaces
[ https://issues.apache.org/jira/browse/CAMEL-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828317#comment-17828317 ] Claus Ibsen commented on CAMEL-17641: - TODO: camel-sql aggregation repository > camel-catalog - Generate metadata for all known implementations of camel SPI > interfaces > --- > > Key: CAMEL-17641 > URL: https://issues.apache.org/jira/browse/CAMEL-17641 > Project: Camel > Issue Type: New Feature > Components: camel-catalog >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.5.0 > > > For example AggregationStrategy can have a set of OOTB impls, and it would be > good to know what we have in camel. > We can make this metadata generated per component then it can be isolated per > component you use - and maybe also have this in the camel-catalog so we have > a single place to look -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-17641) camel-catalog - Generate metadata for all known implementations of camel SPI interfaces
[ https://issues.apache.org/jira/browse/CAMEL-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17827138#comment-17827138 ] Claus Ibsen edited comment on CAMEL-17641 at 3/19/24 11:49 AM: --- TODO: mojo to generate json *DONE* TODO: markup various beans such as aggregation strategy *DONE* TODO: copy jsons into camel-catalog *DONE* TODO: markup more beans from other components (camel-zipfile as example) TODO: camel-jbang can use the catalog to map FQN classname to JAR *DONE* TODO: generate configurer for reflection-free *DONE* TODO: markup all aggregation strategies *DONE* TODO: markup all idempotent repositories *DONE* TODO: markup all aggregation repositories was (Author: davsclaus): TODO: mojo to generate json *DONE* TODO: markup various beans such as aggregation strategy *DONE* TODO: copy jsons into camel-catalog *DONE* TODO: markup more beans from other components (camel-zipfile as example) TODO: camel-jbang can use the catalog to map FQN classname to JAR *DONE* TODO: generate configurer for reflection-free *DONE* TODO: markup all aggregation strategies *DONE* TODO: markup all idempotent repositories TODO: markup all aggregation repositories > camel-catalog - Generate metadata for all known implementations of camel SPI > interfaces > --- > > Key: CAMEL-17641 > URL: https://issues.apache.org/jira/browse/CAMEL-17641 > Project: Camel > Issue Type: New Feature > Components: camel-catalog >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.5.0 > > > For example AggregationStrategy can have a set of OOTB impls, and it would be > good to know what we have in camel. > We can make this metadata generated per component then it can be isolated per > component you use - and maybe also have this in the camel-catalog so we have > a single place to look -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-20581) camel-test-infra-artemis: ensure components use the correct lifecycle for service
Otavio Rodolfo Piske created CAMEL-20581: Summary: camel-test-infra-artemis: ensure components use the correct lifecycle for service Key: CAMEL-20581 URL: https://issues.apache.org/jira/browse/CAMEL-20581 Project: Camel Issue Type: Test Components: camel-test-infra-artemis Reporter: Otavio Rodolfo Piske Assignee: Otavio Rodolfo Piske We still have a few components failing to declare the Artemis service as static during tests. This can lead to instabilities and flakiness. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-20580) Camel-File: Polls never stop
[
https://issues.apache.org/jira/browse/CAMEL-20580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828238#comment-17828238
]
Cosimo Damiano Prete commented on CAMEL-20580:
--
Hi [~acosentino].
This was clear to me, unfortunately.
I was just explaining to [~davsclaus] why I didn't use a newer version.
> Camel-File: Polls never stop
>
>
> Key: CAMEL-20580
> URL: https://issues.apache.org/jira/browse/CAMEL-20580
> Project: Camel
> Issue Type: Bug
> Components: camel-file
>Affects Versions: 3.14.10
>Reporter: Cosimo Damiano Prete
>Priority: Major
>
> Hi.
> I've the following Camel route that never stops, even on shutdown:
> {code:java}
> from(buildSourceEndpointUri())
> .routeId("selection-files")
> .process(processor)
> .to(buildTargetSftpEndpoint().toString())
> .log(DEBUG, "Selection file '${header:" + FILE_PATH + "}' uploaded to the FTS
> server");
> {code}
> where, `buildSourceEndpointUri` contains:
> {code:java}
> final StringBuilder builder = new StringBuilder();
> builder.append("file:");
> if(!getBaseDirectory().startsWith("/")) builder.append("/");
> builder.append(getBaseDirectory());
> builder.append("?recursive=true");
> builder.append("&flatten=false");
> builder.append("&startingDirectoryMustExist=true");
> builder.append("&noop=true");
> builder.append("&idempotent=true");
> builder.append("&idempotentKey=${file:name}-${file:modified}");
> builder.append("&greedy=true");
> builder.append("&initialDelay=0");
> builder.append("&antInclude=");
> builder.append("*/");
> builder.append(selectionSpace.getDir());
> builder.append("/*.xml");
> return builder.toString();
> {code}
> and, on shutdown, I can see:
> {noformat}
> 2024-03-19 06:57:03,001 INFO
> [org.apache.camel.impl.engine.DefaultShutdownStrategy:691] (Camel
> (tsbulk-sftp-context) thread #272 - ShutdownTask) Waiting as there are still
> 1 inflight and pending exchanges to complete, timeout in 45 seconds.
> Inflights per route: [selection-files = 1]
> 2024-03-19 06:57:48,007 WARN
> [org.apache.camel.impl.engine.DefaultShutdownStrategy:249] (MSC service
> thread 1-7) Timeout occurred during graceful shutdown. Forcing the routes to
> be shutdown now. Notice: some resources may still be running as graceful
> shutdown did not complete successfully.{noformat}
> Do you have any suggestions on why does this happen? Is it maybe a bug in the
> version I'm using?
> Regarding the directory under monitoring, there will be roughly 80 files
> included by the Ant pattern and the app is basically idle after ca. 11:00 AM,
> therefore there should be plenty of time to process those files and it's
> really unacceptable that there are still some at 06:00 AM or so of the day
> after.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20580) Camel-File: Polls never stop
[
https://issues.apache.org/jira/browse/CAMEL-20580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828235#comment-17828235
]
Andrea Cosentino commented on CAMEL-20580:
--
We are not going to release any new version for 3.14.x even if it's Java 8 only.
> Camel-File: Polls never stop
>
>
> Key: CAMEL-20580
> URL: https://issues.apache.org/jira/browse/CAMEL-20580
> Project: Camel
> Issue Type: Bug
> Components: camel-file
>Affects Versions: 3.14.10
>Reporter: Cosimo Damiano Prete
>Priority: Major
>
> Hi.
> I've the following Camel route that never stops, even on shutdown:
> {code:java}
> from(buildSourceEndpointUri())
> .routeId("selection-files")
> .process(processor)
> .to(buildTargetSftpEndpoint().toString())
> .log(DEBUG, "Selection file '${header:" + FILE_PATH + "}' uploaded to the FTS
> server");
> {code}
> where, `buildSourceEndpointUri` contains:
> {code:java}
> final StringBuilder builder = new StringBuilder();
> builder.append("file:");
> if(!getBaseDirectory().startsWith("/")) builder.append("/");
> builder.append(getBaseDirectory());
> builder.append("?recursive=true");
> builder.append("&flatten=false");
> builder.append("&startingDirectoryMustExist=true");
> builder.append("&noop=true");
> builder.append("&idempotent=true");
> builder.append("&idempotentKey=${file:name}-${file:modified}");
> builder.append("&greedy=true");
> builder.append("&initialDelay=0");
> builder.append("&antInclude=");
> builder.append("*/");
> builder.append(selectionSpace.getDir());
> builder.append("/*.xml");
> return builder.toString();
> {code}
> and, on shutdown, I can see:
> {noformat}
> 2024-03-19 06:57:03,001 INFO
> [org.apache.camel.impl.engine.DefaultShutdownStrategy:691] (Camel
> (tsbulk-sftp-context) thread #272 - ShutdownTask) Waiting as there are still
> 1 inflight and pending exchanges to complete, timeout in 45 seconds.
> Inflights per route: [selection-files = 1]
> 2024-03-19 06:57:48,007 WARN
> [org.apache.camel.impl.engine.DefaultShutdownStrategy:249] (MSC service
> thread 1-7) Timeout occurred during graceful shutdown. Forcing the routes to
> be shutdown now. Notice: some resources may still be running as graceful
> shutdown did not complete successfully.{noformat}
> Do you have any suggestions on why does this happen? Is it maybe a bug in the
> version I'm using?
> Regarding the directory under monitoring, there will be roughly 80 files
> included by the Ant pattern and the app is basically idle after ca. 11:00 AM,
> therefore there should be plenty of time to process those files and it's
> really unacceptable that there are still some at 06:00 AM or so of the day
> after.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-20580) Camel-File: Polls never stop
[
https://issues.apache.org/jira/browse/CAMEL-20580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17828233#comment-17828233
]
Cosimo Damiano Prete commented on CAMEL-20580:
--
Hi [~davsclaus].
Unfortunately, 3.14.10 is the last version supporting Java 8 according to this
page: [https://camel.apache.org/manual/what-are-the-dependencies.html]
> Camel-File: Polls never stop
>
>
> Key: CAMEL-20580
> URL: https://issues.apache.org/jira/browse/CAMEL-20580
> Project: Camel
> Issue Type: Bug
> Components: camel-file
>Affects Versions: 3.14.10
>Reporter: Cosimo Damiano Prete
>Priority: Major
>
> Hi.
> I've the following Camel route that never stops, even on shutdown:
> {code:java}
> from(buildSourceEndpointUri())
> .routeId("selection-files")
> .process(processor)
> .to(buildTargetSftpEndpoint().toString())
> .log(DEBUG, "Selection file '${header:" + FILE_PATH + "}' uploaded to the FTS
> server");
> {code}
> where, `buildSourceEndpointUri` contains:
> {code:java}
> final StringBuilder builder = new StringBuilder();
> builder.append("file:");
> if(!getBaseDirectory().startsWith("/")) builder.append("/");
> builder.append(getBaseDirectory());
> builder.append("?recursive=true");
> builder.append("&flatten=false");
> builder.append("&startingDirectoryMustExist=true");
> builder.append("&noop=true");
> builder.append("&idempotent=true");
> builder.append("&idempotentKey=${file:name}-${file:modified}");
> builder.append("&greedy=true");
> builder.append("&initialDelay=0");
> builder.append("&antInclude=");
> builder.append("*/");
> builder.append(selectionSpace.getDir());
> builder.append("/*.xml");
> return builder.toString();
> {code}
> and, on shutdown, I can see:
> {noformat}
> 2024-03-19 06:57:03,001 INFO
> [org.apache.camel.impl.engine.DefaultShutdownStrategy:691] (Camel
> (tsbulk-sftp-context) thread #272 - ShutdownTask) Waiting as there are still
> 1 inflight and pending exchanges to complete, timeout in 45 seconds.
> Inflights per route: [selection-files = 1]
> 2024-03-19 06:57:48,007 WARN
> [org.apache.camel.impl.engine.DefaultShutdownStrategy:249] (MSC service
> thread 1-7) Timeout occurred during graceful shutdown. Forcing the routes to
> be shutdown now. Notice: some resources may still be running as graceful
> shutdown did not complete successfully.{noformat}
> Do you have any suggestions on why does this happen? Is it maybe a bug in the
> version I'm using?
> Regarding the directory under monitoring, there will be roughly 80 files
> included by the Ant pattern and the app is basically idle after ca. 11:00 AM,
> therefore there should be plenty of time to process those files and it's
> really unacceptable that there are still some at 06:00 AM or so of the day
> after.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
