[jira] [Commented] (CAMEL-18327) camel-kafka: Kafka consumer closes when it is paused
[
https://issues.apache.org/jira/browse/CAMEL-18327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601610#comment-17601610
]
rupam commented on CAMEL-18327:
---
The method isKafkaConsumerRunnable() in do while loop should not check if it
is in any suspended or suspending state. That will allow the consumer to
continue try polling for messages, but since the consumer has been paused, the
poll will return empty messages
> camel-kafka: Kafka consumer closes when it is paused
>
>
> Key: CAMEL-18327
> URL: https://issues.apache.org/jira/browse/CAMEL-18327
> Project: Camel
> Issue Type: Task
> Components: camel-kafka
>Affects Versions: 3.17.0
>Reporter: rupam
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 3.18.3, 3.19.0
>
>
>
> In the startPolling() method, if the consumer is suspending, then the
> unsubscribe method is called which permanently closes the consumer
>
> {code:java}
> Duration pollDuration = Duration.ofMillis(pollTimeoutMs);
> while (isKafkaConsumerRunnable() && isConnected() &&
> pollExceptionStrategy.canContinue()) {
> ConsumerRecords allRecords =
> consumer.poll(pollDuration);
> if (consumerListener != null) {
> if (!consumerListener.afterConsume(consumer)) {
> continue;
> }
> }
> ProcessingResult result =
> recordProcessorFacade.processPolledRecords(allRecords);
> if (result.isBreakOnErrorHit()) {
> LOG.debug("We hit an error ... setting flags to force reconnect");
> // force re-connect
> setReconnect(true);
> setConnected(false);
> }
> updateTaskState();
> }
> if (!isConnected()) {
> LOG.debug("Not reconnecting, check whether to auto-commit or not
> ...");
> commitManager.commit();
> }
> safeUnsubscribe();
> } catch (InterruptException e) {{code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18482) camel-core - Pre 3.13 Split EIP behaviour
Jacques Franken created CAMEL-18482:
---
Summary: camel-core - Pre 3.13 Split EIP behaviour
Key: CAMEL-18482
URL: https://issues.apache.org/jira/browse/CAMEL-18482
Project: Camel
Issue Type: Wish
Components: came-core
Reporter: Jacques Franken
We are busy updating some of our deployments to the latest camel LTS, but found
a change in behaviour in split on maps. We've tracked it down to the following
ticket as being a likely cause of the change.
https://issues.apache.org/jira/browse/CAMEL-17101
So my wish item is: Please add an option to .split() to allow processing the
map the "old way".
This is not a "bug" - we all feel that the current behaviour is logically how
the split EIP should work when splitting a single object in a complex map.
Notwithstanding, the old behaviour was really elegant in cases where we had to
split("${body.Map}").
In version 3.12 that allowed us to process the Map as a "record", pass the
record to a bean, do a simpleJdbcinsert() and once the split ended, the body
was restored for the next split().
I asked around Stackoverflow and in zulip for ideas, and we tried a few things
- but eventually found the only way for is significant code modification.
This involves setting a header variable to the sub-map --> and call the bean to
handle SQL insert.
The bean also now has to do some logic. if the header variable is set --> then
it should use the header for insert value. if header is null - then do default
behaviour.
If you need me to provide code examples to illustrate - please let me know.
link to Zulip:
[https://camel.zulipchat.com/#narrow/stream/257301-camel-spring-boot/topic/split.28.29.20change.20in.20behaviour.203.2E13.20onwards]
link to Stack-overflow:
[https://stackoverflow.com/questions/73615483/how-to-return-non-array-json-object-from-apache-camel-split]
Sorry if this is not appropriate way to raise this request. I felt that it was
worth raising officially as it does make for simpler code in some use-cases.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18481) Allow Mail Consumer to handle duplicate/empty attachment filenames
[ https://issues.apache.org/jira/browse/CAMEL-18481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601503#comment-17601503 ] Manuel Shenavai commented on CAMEL-18481: - PR created: https://github.com/apache/camel/pull/8322 > Allow Mail Consumer to handle duplicate/empty attachment filenames > -- > > Key: CAMEL-18481 > URL: https://issues.apache.org/jira/browse/CAMEL-18481 > Project: Camel > Issue Type: Improvement > Components: camel-mail >Affects Versions: 3.19.0 >Reporter: Manuel Shenavai >Priority: Minor > > The mail consumer is not able to process mail attachments that are empty or > if no filename is set. Its also not possible to get all attachments of a mail > if they have the same filename. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18481) Allow Mail Consumer to handle duplicate/empty attachment filenames
[ https://issues.apache.org/jira/browse/CAMEL-18481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manuel Shenavai updated CAMEL-18481: Priority: Minor (was: Major) > Allow Mail Consumer to handle duplicate/empty attachment filenames > -- > > Key: CAMEL-18481 > URL: https://issues.apache.org/jira/browse/CAMEL-18481 > Project: Camel > Issue Type: Improvement > Components: camel-mail >Affects Versions: 3.19.0 >Reporter: Manuel Shenavai >Priority: Minor > > The mail consumer is not able to process mail attachments that are empty or > if no filename is set. Its also not possible to get all attachments of a mail > if they have the same filename. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18481) Allow Mail Consumer to handle duplicate/empty attachment filenames
Manuel Shenavai created CAMEL-18481: --- Summary: Allow Mail Consumer to handle duplicate/empty attachment filenames Key: CAMEL-18481 URL: https://issues.apache.org/jira/browse/CAMEL-18481 Project: Camel Issue Type: Improvement Components: camel-mail Affects Versions: 3.19.0 Reporter: Manuel Shenavai The mail consumer is not able to process mail attachments that are empty or if no filename is set. Its also not possible to get all attachments of a mail if they have the same filename. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18316) camel-core 3.18 not compatible with Jakarta Activation framework 2.0
[ https://issues.apache.org/jira/browse/CAMEL-18316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601485#comment-17601485 ] Soumik Das commented on CAMEL-18316: [~davsclaus] Thanks for the update. > camel-core 3.18 not compatible with Jakarta Activation framework 2.0 > > > Key: CAMEL-18316 > URL: https://issues.apache.org/jira/browse/CAMEL-18316 > Project: Camel > Issue Type: Dependency upgrade > Components: came-core >Affects Versions: 3.18.0 > Environment: JDK 17 >Reporter: Soumik Das >Priority: Major > > We are upgrading from JAF 1.2 to Jakarta Activation (JAF 2.0) for JDK 17. It > turns out camel 3.18 does not support jakarta.activation. When can we expect > an upgrade? -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18480) camel-aws - Dev console for AWS secrets manager
[ https://issues.apache.org/jira/browse/CAMEL-18480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18480. - Resolution: Fixed > camel-aws - Dev console for AWS secrets manager > --- > > Key: CAMEL-18480 > URL: https://issues.apache.org/jira/browse/CAMEL-18480 > Project: Camel > Issue Type: New Feature > Components: camel-aws >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18480) camel-aws - Dev console for AWS secrets manager
Claus Ibsen created CAMEL-18480: --- Summary: camel-aws - Dev console for AWS secrets manager Key: CAMEL-18480 URL: https://issues.apache.org/jira/browse/CAMEL-18480 Project: Camel Issue Type: New Feature Components: camel-aws Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18131) camel-health - Add health checks for components that has extension for connectivity verification
[ https://issues.apache.org/jira/browse/CAMEL-18131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rhuan Rocha updated CAMEL-18131: Description: A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. *Components to update (partial table):* |Component|Done| |AWS2-S3|x| |AWS2-ATHENA| | |AWS2-EKS| | |AWS2-CW| | |AWS2-DDB| | |AWS2-EC2| | |AWS2-EVENTBRIDGE| | |AWS2-IAM| | was:A number of components have the old component extension verification (see aws-s3) - we can migrate that into health-checks. > camel-health - Add health checks for components that has extension for > connectivity verification > > > Key: CAMEL-18131 > URL: https://issues.apache.org/jira/browse/CAMEL-18131 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Assignee: Rhuan Rocha >Priority: Major > Fix For: 3.19.0 > > > A number of components have the old component extension verification (see > aws-s3) - we can migrate that into health-checks. > > *Components to update (partial table):* > |Component|Done| > |AWS2-S3|x| > |AWS2-ATHENA| | > |AWS2-EKS| | > |AWS2-CW| | > |AWS2-DDB| | > |AWS2-EC2| | > |AWS2-EVENTBRIDGE| | > |AWS2-IAM| | -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18478) Support Secrets Reload from Vault/Cloud Service in camel-spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-18478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18478. -- Resolution: Fixed > Support Secrets Reload from Vault/Cloud Service in camel-spring-boot > - > > Key: CAMEL-18478 > URL: https://issues.apache.org/jira/browse/CAMEL-18478 > Project: Camel > Issue Type: Sub-task > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18479) camel-aws - Capture aws secrets in use making refresh no need for declaring the secrets
Claus Ibsen created CAMEL-18479: --- Summary: camel-aws - Capture aws secrets in use making refresh no need for declaring the secrets Key: CAMEL-18479 URL: https://issues.apache.org/jira/browse/CAMEL-18479 Project: Camel Issue Type: Improvement Components: camel-aws Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.19.0 The goal is to avoid need for declaring this https://github.com/apache/camel-examples/blob/main/examples/aws/aws-secrets-manager-reloading/src/main/resources/application.properties#L30 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-17586) Camel mail consumer: Unable to handle multiple attachments with the same filename
[ https://issues.apache.org/jira/browse/CAMEL-17586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601345#comment-17601345 ] Manuel Shenavai commented on CAMEL-17586: - Thanks for considering this request and improving the mail component (y) > Camel mail consumer: Unable to handle multiple attachments with the same > filename > - > > Key: CAMEL-17586 > URL: https://issues.apache.org/jira/browse/CAMEL-17586 > Project: Camel > Issue Type: Improvement > Components: camel-mail >Affects Versions: 3.x >Reporter: Manuel Shenavai >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.19.0 > > > If there is a mail with multiple attachments that have the same name, only > one of the attachments will be added to the attachment map of the exchange. > The other attachments will be ignored and only a warning will be logged. > [https://github.com/mash-sap/camel/blob/main/components/camel-mail/src/main/java/org/apache/camel/component/mail/MailBinding.java#L371] > This will cause data loss. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Work started] (CAMEL-18456) camel-test-infra: investigate consolidating usages of web server and servlets
[ https://issues.apache.org/jira/browse/CAMEL-18456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-18456 started by Otavio Rodolfo Piske. > camel-test-infra: investigate consolidating usages of web server and servlets > - > > Key: CAMEL-18456 > URL: https://issues.apache.org/jira/browse/CAMEL-18456 > Project: Camel > Issue Type: Task > Components: camel-test-infra >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.x > > > There are many tests using Jetty, Undertow, Tomcat and others to run web > servers and/or servlet containers. Investigate consolidating this code into a > test infra module and cleaning up the components. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18477) knative producer with ProducerTemplate is missing the fromRouteId
[
https://issues.apache.org/jira/browse/CAMEL-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601322#comment-17601322
]
Zineb Bendhiba commented on CAMEL-18477:
My mistake I missed the possibility to add those with header
> knative producer with ProducerTemplate is missing the fromRouteId
> -
>
> Key: CAMEL-18477
> URL: https://issues.apache.org/jira/browse/CAMEL-18477
> Project: Camel
> Issue Type: Bug
> Components: camel-knative
>Affects Versions: 3.18.1
>Reporter: Zineb Bendhiba
>Assignee: Zineb Bendhiba
>Priority: Major
> Fix For: 3.18.3, 3.19.0
>
>
> Knative camel producer creates CloudEvents. To have a valid CloudEvent,
> there's the need to have a field named `source`.
> The knative camel producer sets this value by putting the "fromRouteId"
> value. This value is set by DefaultConsumer when creating the extended
> exchange.
> However, when using the knative producer via ProducerTemplate, we miss this
> value. And the event is rejected because source is required by knative.
> Log :
> {code:java}
> {"level":"warn","ts":"2022-09-07T10:28:15.844Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:145","msg":"failed
> to validate extracted event","error":"source: REQUIRED\n"} {code}
> As a temporary fix, we could ask user to override the source value, as in
> this configuration example :
> {code:java}
> {
> "type": "event",
> "name": "YOUR_NAME_EVENT",
> "url": "YOUR_LINK_TO_BROKER",
> "metadata": {
> "camel.endpoint.kind": "sink"
> },
> "ceOverrides": {
> "ce-source": "YOUR_SOURCE_NAME"
> }
> } {code}
> However, it doesn't seem right to suppose in the code this value is coming
> necessarly from a Camel Consumer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18477) knative producer with ProducerTemplate is missing the fromRouteId
[
https://issues.apache.org/jira/browse/CAMEL-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601317#comment-17601317
]
Luca Burgazzoli commented on CAMEL-18477:
-
I'd say that it works as designed as the component tries to se some sensible
defaults but some of the attributes are expected to be set the the user. This
is particularly true for source and event type as those are business attributes
an we cannot reliably compute/derive them.
The idea is that if you need to customize any attribute, then a user should set
one of the CamelCloudEvent* header so with the ProducerTemplate tou should use
sendBodyWithHeader or similar methods
> knative producer with ProducerTemplate is missing the fromRouteId
> -
>
> Key: CAMEL-18477
> URL: https://issues.apache.org/jira/browse/CAMEL-18477
> Project: Camel
> Issue Type: Bug
> Components: camel-knative
>Affects Versions: 3.18.1
>Reporter: Zineb Bendhiba
>Assignee: Zineb Bendhiba
>Priority: Major
> Fix For: 3.18.3, 3.19.0
>
>
> Knative camel producer creates CloudEvents. To have a valid CloudEvent,
> there's the need to have a field named `source`.
> The knative camel producer sets this value by putting the "fromRouteId"
> value. This value is set by DefaultConsumer when creating the extended
> exchange.
> However, when using the knative producer via ProducerTemplate, we miss this
> value. And the event is rejected because source is required by knative.
> Log :
> {code:java}
> {"level":"warn","ts":"2022-09-07T10:28:15.844Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:145","msg":"failed
> to validate extracted event","error":"source: REQUIRED\n"} {code}
> As a temporary fix, we could ask user to override the source value, as in
> this configuration example :
> {code:java}
> {
> "type": "event",
> "name": "YOUR_NAME_EVENT",
> "url": "YOUR_LINK_TO_BROKER",
> "metadata": {
> "camel.endpoint.kind": "sink"
> },
> "ceOverrides": {
> "ce-source": "YOUR_SOURCE_NAME"
> }
> } {code}
> However, it doesn't seem right to suppose in the code this value is coming
> necessarly from a Camel Consumer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18478) Support Secrets Reload from Vault/Cloud Service in camel-spring-boot
[ https://issues.apache.org/jira/browse/CAMEL-18478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino updated CAMEL-18478: - Summary: Support Secrets Reload from Vault/Cloud Service in camel-spring-boot (was: Support Secret Refresh in camel-spring-boot ) > Support Secrets Reload from Vault/Cloud Service in camel-spring-boot > - > > Key: CAMEL-18478 > URL: https://issues.apache.org/jira/browse/CAMEL-18478 > Project: Camel > Issue Type: Sub-task > Components: camel-spring-boot >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18478) Support Secret Refresh in camel-spring-boot
Andrea Cosentino created CAMEL-18478: Summary: Support Secret Refresh in camel-spring-boot Key: CAMEL-18478 URL: https://issues.apache.org/jira/browse/CAMEL-18478 Project: Camel Issue Type: Sub-task Components: camel-spring-boot Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-16488) Investigate test speed up for camel-ftp
[ https://issues.apache.org/jira/browse/CAMEL-16488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-16488. -- Resolution: Fixed The tests were parallelized and the execution time (on my machine) decreased by about 50%. > Investigate test speed up for camel-ftp > --- > > Key: CAMEL-16488 > URL: https://issues.apache.org/jira/browse/CAMEL-16488 > Project: Camel > Issue Type: Task > Components: camel-ftp, tests >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.19.0 > > > Check if we can reduce test duration for camel-ftp by moving some of the > tests to JUnit 5 nested classes. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18477) knative producer with ProducerTemplate is missing the fromRouteId
[
https://issues.apache.org/jira/browse/CAMEL-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601295#comment-17601295
]
Claus Ibsen commented on CAMEL-18477:
-
Also IMHO it should be possible to set a custom source, what if there is a
Camel header set on the Exchange message with CamelCloudEventSource as the key?
> knative producer with ProducerTemplate is missing the fromRouteId
> -
>
> Key: CAMEL-18477
> URL: https://issues.apache.org/jira/browse/CAMEL-18477
> Project: Camel
> Issue Type: Bug
> Components: camel-knative
>Affects Versions: 3.18.1
>Reporter: Zineb Bendhiba
>Assignee: Zineb Bendhiba
>Priority: Major
> Fix For: 3.18.3, 3.19.0
>
>
> Knative camel producer creates CloudEvents. To have a valid CloudEvent,
> there's the need to have a field named `source`.
> The knative camel producer sets this value by putting the "fromRouteId"
> value. This value is set by DefaultConsumer when creating the extended
> exchange.
> However, when using the knative producer via ProducerTemplate, we miss this
> value. And the event is rejected because source is required by knative.
> Log :
> {code:java}
> {"level":"warn","ts":"2022-09-07T10:28:15.844Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:145","msg":"failed
> to validate extracted event","error":"source: REQUIRED\n"} {code}
> As a temporary fix, we could ask user to override the source value, as in
> this configuration example :
> {code:java}
> {
> "type": "event",
> "name": "YOUR_NAME_EVENT",
> "url": "YOUR_LINK_TO_BROKER",
> "metadata": {
> "camel.endpoint.kind": "sink"
> },
> "ceOverrides": {
> "ce-source": "YOUR_SOURCE_NAME"
> }
> } {code}
> However, it doesn't seem right to suppose in the code this value is coming
> necessarly from a Camel Consumer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18477) knative producer with ProducerTemplate is missing the fromRouteId
[
https://issues.apache.org/jira/browse/CAMEL-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601294#comment-17601294
]
Claus Ibsen commented on CAMEL-18477:
-
Maybe you can make the code fallback and use camel context id as source if
route id is empty
> knative producer with ProducerTemplate is missing the fromRouteId
> -
>
> Key: CAMEL-18477
> URL: https://issues.apache.org/jira/browse/CAMEL-18477
> Project: Camel
> Issue Type: Bug
> Components: camel-knative
>Affects Versions: 3.18.1
>Reporter: Zineb Bendhiba
>Assignee: Zineb Bendhiba
>Priority: Major
> Fix For: 3.19.0
>
>
> Knative camel producer creates CloudEvents. To have a valid CloudEvent,
> there's the need to have a field named `source`.
> The knative camel producer sets this value by putting the "fromRouteId"
> value. This value is set by DefaultConsumer when creating the extended
> exchange.
> However, when using the knative producer via ProducerTemplate, we miss this
> value. And the event is rejected because source is required by knative.
> Log :
> {code:java}
> {"level":"warn","ts":"2022-09-07T10:28:15.844Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:145","msg":"failed
> to validate extracted event","error":"source: REQUIRED\n"} {code}
> As a temporary fix, we could ask user to override the source value, as in
> this configuration example :
> {code:java}
> {
> "type": "event",
> "name": "YOUR_NAME_EVENT",
> "url": "YOUR_LINK_TO_BROKER",
> "metadata": {
> "camel.endpoint.kind": "sink"
> },
> "ceOverrides": {
> "ce-source": "YOUR_SOURCE_NAME"
> }
> } {code}
> However, it doesn't seem right to suppose in the code this value is coming
> necessarly from a Camel Consumer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18477) knative producer with ProducerTemplate is missing the fromRouteId
[
https://issues.apache.org/jira/browse/CAMEL-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18477:
Fix Version/s: 3.18.3
> knative producer with ProducerTemplate is missing the fromRouteId
> -
>
> Key: CAMEL-18477
> URL: https://issues.apache.org/jira/browse/CAMEL-18477
> Project: Camel
> Issue Type: Bug
> Components: camel-knative
>Affects Versions: 3.18.1
>Reporter: Zineb Bendhiba
>Assignee: Zineb Bendhiba
>Priority: Major
> Fix For: 3.18.3, 3.19.0
>
>
> Knative camel producer creates CloudEvents. To have a valid CloudEvent,
> there's the need to have a field named `source`.
> The knative camel producer sets this value by putting the "fromRouteId"
> value. This value is set by DefaultConsumer when creating the extended
> exchange.
> However, when using the knative producer via ProducerTemplate, we miss this
> value. And the event is rejected because source is required by knative.
> Log :
> {code:java}
> {"level":"warn","ts":"2022-09-07T10:28:15.844Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:145","msg":"failed
> to validate extracted event","error":"source: REQUIRED\n"} {code}
> As a temporary fix, we could ask user to override the source value, as in
> this configuration example :
> {code:java}
> {
> "type": "event",
> "name": "YOUR_NAME_EVENT",
> "url": "YOUR_LINK_TO_BROKER",
> "metadata": {
> "camel.endpoint.kind": "sink"
> },
> "ceOverrides": {
> "ce-source": "YOUR_SOURCE_NAME"
> }
> } {code}
> However, it doesn't seem right to suppose in the code this value is coming
> necessarly from a Camel Consumer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18473) Knative component : CloudEvents have wrong time format
[
https://issues.apache.org/jira/browse/CAMEL-18473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18473.
-
Resolution: Fixed
> Knative component : CloudEvents have wrong time format
> --
>
> Key: CAMEL-18473
> URL: https://issues.apache.org/jira/browse/CAMEL-18473
> Project: Camel
> Issue Type: Bug
> Components: camel-knative
>Affects Versions: 3.18.1
>Reporter: Zineb Bendhiba
>Assignee: Zineb Bendhiba
>Priority: Major
> Fix For: 3.18.3, 3.19.0
>
>
>
> When trying camel knative component with InMemory channels, we can't see the
> bug because this one doesn't validate the event.
> Outside of this use case when the event is validated on knative, it seems
> that the time has wrong DateFormat.
> For instance, if using the component with a broker, we can't produce an event
> with camel-knative, and this is the log in knative environment :
>
> {code:java}
> {"level":"warn","ts":"2022-09-06T14:35:10.587Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:137","msg":"failed
> to extract event from request","error":"invalid value for time:
> \"22022-08-31T12:00:33.253+02:00\""} {code}
> This is the valid DateFormat, according to [CloudEvents
> spec|[https://github.com/cloudevents/spec]]
>
> {code:java}
> "time" : "2018-04-05T17:31:00Z", {code}
> This corresponds in the Java DateTimeFormatter class to [#ISO_INSTANT].
> However, in camel-knative producer uses [#ISO_OFFSET_DATE_TIME]
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18477) knative producer with ProducerTemplate is missing the fromRouteId
[
https://issues.apache.org/jira/browse/CAMEL-18477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601291#comment-17601291
]
Zineb Bendhiba commented on CAMEL-18477:
[~lburgazzoli] Do you happen to have any opinion on this? I'd be happy to do
the fix
> knative producer with ProducerTemplate is missing the fromRouteId
> -
>
> Key: CAMEL-18477
> URL: https://issues.apache.org/jira/browse/CAMEL-18477
> Project: Camel
> Issue Type: Bug
> Components: camel-knative
>Affects Versions: 3.18.1
>Reporter: Zineb Bendhiba
>Assignee: Zineb Bendhiba
>Priority: Major
> Fix For: 3.19.0
>
>
> Knative camel producer creates CloudEvents. To have a valid CloudEvent,
> there's the need to have a field named `source`.
> The knative camel producer sets this value by putting the "fromRouteId"
> value. This value is set by DefaultConsumer when creating the extended
> exchange.
> However, when using the knative producer via ProducerTemplate, we miss this
> value. And the event is rejected because source is required by knative.
> Log :
> {code:java}
> {"level":"warn","ts":"2022-09-07T10:28:15.844Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:145","msg":"failed
> to validate extracted event","error":"source: REQUIRED\n"} {code}
> As a temporary fix, we could ask user to override the source value, as in
> this configuration example :
> {code:java}
> {
> "type": "event",
> "name": "YOUR_NAME_EVENT",
> "url": "YOUR_LINK_TO_BROKER",
> "metadata": {
> "camel.endpoint.kind": "sink"
> },
> "ceOverrides": {
> "ce-source": "YOUR_SOURCE_NAME"
> }
> } {code}
> However, it doesn't seem right to suppose in the code this value is coming
> necessarly from a Camel Consumer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18477) knative producer with ProducerTemplate is missing the fromRouteId
Zineb Bendhiba created CAMEL-18477:
--
Summary: knative producer with ProducerTemplate is missing the
fromRouteId
Key: CAMEL-18477
URL: https://issues.apache.org/jira/browse/CAMEL-18477
Project: Camel
Issue Type: Bug
Components: camel-knative
Affects Versions: 3.18.1
Reporter: Zineb Bendhiba
Assignee: Zineb Bendhiba
Fix For: 3.19.0
Knative camel producer creates CloudEvents. To have a valid CloudEvent, there's
the need to have a field named `source`.
The knative camel producer sets this value by putting the "fromRouteId" value.
This value is set by DefaultConsumer when creating the extended exchange.
However, when using the knative producer via ProducerTemplate, we miss this
value. And the event is rejected because source is required by knative.
Log :
{code:java}
{"level":"warn","ts":"2022-09-07T10:28:15.844Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:145","msg":"failed
to validate extracted event","error":"source: REQUIRED\n"} {code}
As a temporary fix, we could ask user to override the source value, as in this
configuration example :
{code:java}
{
"type": "event",
"name": "YOUR_NAME_EVENT",
"url": "YOUR_LINK_TO_BROKER",
"metadata": {
"camel.endpoint.kind": "sink"
},
"ceOverrides": {
"ce-source": "YOUR_SOURCE_NAME"
}
} {code}
However, it doesn't seem right to suppose in the code this value is coming
necessarly from a Camel Consumer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18473) Knative component : CloudEvents have wrong time format
[
https://issues.apache.org/jira/browse/CAMEL-18473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18473:
Fix Version/s: 3.19.0
> Knative component : CloudEvents have wrong time format
> --
>
> Key: CAMEL-18473
> URL: https://issues.apache.org/jira/browse/CAMEL-18473
> Project: Camel
> Issue Type: Bug
> Components: camel-knative
>Affects Versions: 3.18.1
>Reporter: Zineb Bendhiba
>Assignee: Zineb Bendhiba
>Priority: Major
> Fix For: 3.18.3, 3.19.0
>
>
>
> When trying camel knative component with InMemory channels, we can't see the
> bug because this one doesn't validate the event.
> Outside of this use case when the event is validated on knative, it seems
> that the time has wrong DateFormat.
> For instance, if using the component with a broker, we can't produce an event
> with camel-knative, and this is the log in knative environment :
>
> {code:java}
> {"level":"warn","ts":"2022-09-06T14:35:10.587Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:137","msg":"failed
> to extract event from request","error":"invalid value for time:
> \"22022-08-31T12:00:33.253+02:00\""} {code}
> This is the valid DateFormat, according to [CloudEvents
> spec|[https://github.com/cloudevents/spec]]
>
> {code:java}
> "time" : "2018-04-05T17:31:00Z", {code}
> This corresponds in the Java DateTimeFormatter class to [#ISO_INSTANT].
> However, in camel-knative producer uses [#ISO_OFFSET_DATE_TIME]
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18475) camel-core - FactoryFinder for period background tasks
[ https://issues.apache.org/jira/browse/CAMEL-18475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601273#comment-17601273 ] Claus Ibsen commented on CAMEL-18475: - PeriodTaskScheduler via extended camel context > camel-core - FactoryFinder for period background tasks > -- > > Key: CAMEL-18475 > URL: https://issues.apache.org/jira/browse/CAMEL-18475 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > We need a plugin that allows to define smaller custom tasks that needs to run > periodically and managed by camel context automatic. > We can use TimerListenerManager to trigger, and then we need the factory > finder annotations to discover/load the plugins -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18475) camel-core - FactoryFinder for period background tasks
[ https://issues.apache.org/jira/browse/CAMEL-18475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18475. - Resolution: Fixed > camel-core - FactoryFinder for period background tasks > -- > > Key: CAMEL-18475 > URL: https://issues.apache.org/jira/browse/CAMEL-18475 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > We need a plugin that allows to define smaller custom tasks that needs to run > periodically and managed by camel context automatic. > We can use TimerListenerManager to trigger, and then we need the factory > finder annotations to discover/load the plugins -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18476) Camel-file component is not able to delete the file after its archived in windows
[
https://issues.apache.org/jira/browse/CAMEL-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramarajan R updated CAMEL-18476:
Description:
I have used
[https://github.com/apache/camel-examples/tree/main/examples/artemis-large-messages]
using AMQ 7.8.0 Broker
Messages are getting processed but after processing the file is unable to
delete from source location, tested in more than 1 windows systems facing the
same
I am using Camel 3.14.3 and Spring boot 2.6.6 using JAVA DSL,
tested with Camel 3.18.1 and Spring boot 2.7.3 also
when running with Camel XML routes are fine but we want to use Java DSL ,
Kindly help.
Raising the concern in Zulip chat earlier.
{{[https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/camel-file.20artemis.20large.20message.20example.20failing.20in.20windows]
}}{{{}tion-poc/inbox0] o.a.c.c.file.GenericFileOnCompletion : Error during
commit. Exchange[7D4CFE29E3F7515-0003]. Caused by:
[org.apache.camel.component.file.GenericFileOperationFailedException - Error
renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx to
C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx]{}}}{{{}org.apache.camel.component.file.GenericFileOperationFailedException:
Error renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx to
C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx{}}}
{{at
org.apache.camel.component.file.FileOperations.renameFile(FileOperations.java:93)
~[camel-file-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:145)
~[camel-file-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:121)
~[camel-file-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.component.file.GenericFileOnCompletion.processStrategyCommit(GenericFileOnCompletion.java:134)
~[camel-file-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.component.file.GenericFileOnCompletion.onCompletion(GenericFileOnCompletion.java:86)
~[camel-file-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.component.file.GenericFileOnCompletion.onComplete(GenericFileOnCompletion.java:60)
~[camel-file-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.support.UnitOfWorkHelper.doneSynchronization(UnitOfWorkHelper.java:104)
~[camel-support-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.support.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:93)
~[camel-support-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.impl.engine.DefaultUnitOfWork.done(DefaultUnitOfWork.java:238)
~[camel-base-engine-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.support.UnitOfWorkHelper.doneUow(UnitOfWorkHelper.java:61)
~[camel-support-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:777)
~[camel-base-engine-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:712)
~[camel-base-engine-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.impl.engine.CamelInternalProcessor$AsyncAfterTask.done(CamelInternalProcessor.java:263)
~[camel-base-engine-3.14.3.jar:3.14.3]}}
{{at org.apache.camel.AsyncCallback.run(AsyncCallback.java:44)
~[camel-api-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193)
~[camel-base-engine-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:64)
~[camel-base-engine-3.14.3.jar:3.14.3]}}
{{at org.apache.camel.processor.Pipeline.process(Pipeline.java:184)
~[camel-core-processor-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:398)
~[camel-base-engine-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:492)
~[camel-file-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:245)
~[camel-file-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:206)
~[camel-file-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:202)
~[camel-support-3.14.3.jar:3.14.3]}}
{{at
org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:116)
~[camel-support-3.14.3.jar:3.14.3]}}
{{at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
~[na:na]}}
{{at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305)
~[na:na]}}
{{at
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305)
~[na:na]}}
{{at
[jira] [Updated] (CAMEL-18476) Camel-file component is not able to delete the file after its archived in windows
[ https://issues.apache.org/jira/browse/CAMEL-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramarajan R updated CAMEL-18476: Summary: Camel-file component is not able to delete the file after its archived in windows (was: Camel-file component is not able to delete the file after its archived) > Camel-file component is not able to delete the file after its archived in > windows > - > > Key: CAMEL-18476 > URL: https://issues.apache.org/jira/browse/CAMEL-18476 > Project: Camel > Issue Type: Bug > Components: camel-file >Affects Versions: 3.14.3, 3.18.1 >Reporter: Ramarajan R >Priority: Minor > Attachments: artemis-large-messages.zip > > > I have used > [https://github.com/apache/camel-examples/tree/main/examples/artemis-large-messages] > using AMQ 7.8.0 Broker > Messages are getting processed but after processing the file is unable to > delete from source location, tested in more than 1 windows systems facing the > same > I am using Camel 3.14.3 and Spring boot 2.6.6 using JAVA DSL, > tested with Camel 3.18.1 and Spring boot 2.7.3 also > when running with Camel XML routes are fine but we want to use Java DSL , > Kindly help. > Raising the concern in Zulip chat earlier. > [https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/camel-file.20artemis.20large.20message.20example.20failing.20in.20windows] > > tion-poc/inbox0] o.a.c.c.file.GenericFileOnCompletion : Error during commit. > Exchange[7D4CFE29E3F7515-0003]. Caused by: > [org.apache.camel.component.file.GenericFileOperationFailedException - Error > renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx to > C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx] > org.apache.camel.component.file.GenericFileOperationFailedException: Error > renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx to > C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx > at > org.apache.camel.component.file.FileOperations.renameFile(FileOperations.java:93) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:145) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:121) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileOnCompletion.processStrategyCommit(GenericFileOnCompletion.java:134) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileOnCompletion.onCompletion(GenericFileOnCompletion.java:86) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileOnCompletion.onComplete(GenericFileOnCompletion.java:60) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.support.UnitOfWorkHelper.doneSynchronization(UnitOfWorkHelper.java:104) > ~[camel-support-3.14.3.jar:3.14.3] > at > org.apache.camel.support.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:93) > ~[camel-support-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.DefaultUnitOfWork.done(DefaultUnitOfWork.java:238) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at > org.apache.camel.support.UnitOfWorkHelper.doneUow(UnitOfWorkHelper.java:61) > ~[camel-support-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:777) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:712) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.CamelInternalProcessor$AsyncAfterTask.done(CamelInternalProcessor.java:263) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at org.apache.camel.AsyncCallback.run(AsyncCallback.java:44) > ~[camel-api-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:64) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at org.apache.camel.processor.Pipeline.process(Pipeline.java:184) > ~[camel-core-processor-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:398) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:492) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:245) >
[jira] [Updated] (CAMEL-18476) Camel-file component is not able to delete the file after its archived
[ https://issues.apache.org/jira/browse/CAMEL-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18476: Priority: Minor (was: Major) > Camel-file component is not able to delete the file after its archived > -- > > Key: CAMEL-18476 > URL: https://issues.apache.org/jira/browse/CAMEL-18476 > Project: Camel > Issue Type: Bug > Components: camel-file >Affects Versions: 3.14.3, 3.18.1 >Reporter: Ramarajan R >Priority: Minor > Attachments: artemis-large-messages.zip > > > I have used > [https://github.com/apache/camel-examples/tree/main/examples/artemis-large-messages] > using AMQ 7.8.0 Broker > Messages are getting processed but after processing the file is unable to > delete from source location, tested in more than 1 windows systems facing the > same > I am using Camel 3.14.3 and Spring boot 2.6.6 using JAVA DSL, > tested with Camel 3.18.1 and Spring boot 2.7.3 also > when running with Camel XML routes are fine but we want to use Java DSL , > Kindly help. > Raising the concern in Zulip chat earlier. > [https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/camel-file.20artemis.20large.20message.20example.20failing.20in.20windows] > > tion-poc/inbox0] o.a.c.c.file.GenericFileOnCompletion : Error during commit. > Exchange[7D4CFE29E3F7515-0003]. Caused by: > [org.apache.camel.component.file.GenericFileOperationFailedException - Error > renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx to > C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx] > org.apache.camel.component.file.GenericFileOperationFailedException: Error > renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx to > C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx > at > org.apache.camel.component.file.FileOperations.renameFile(FileOperations.java:93) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:145) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:121) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileOnCompletion.processStrategyCommit(GenericFileOnCompletion.java:134) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileOnCompletion.onCompletion(GenericFileOnCompletion.java:86) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileOnCompletion.onComplete(GenericFileOnCompletion.java:60) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.support.UnitOfWorkHelper.doneSynchronization(UnitOfWorkHelper.java:104) > ~[camel-support-3.14.3.jar:3.14.3] > at > org.apache.camel.support.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:93) > ~[camel-support-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.DefaultUnitOfWork.done(DefaultUnitOfWork.java:238) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at > org.apache.camel.support.UnitOfWorkHelper.doneUow(UnitOfWorkHelper.java:61) > ~[camel-support-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:777) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:712) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.CamelInternalProcessor$AsyncAfterTask.done(CamelInternalProcessor.java:263) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at org.apache.camel.AsyncCallback.run(AsyncCallback.java:44) > ~[camel-api-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:64) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at org.apache.camel.processor.Pipeline.process(Pipeline.java:184) > ~[camel-core-processor-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:398) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:492) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:245) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:206) > ~[camel-file-3.14.3.jar:3.14.3] > at >
[jira] [Updated] (CAMEL-18476) Camel-file component is not able to delete the file after its archived
[ https://issues.apache.org/jira/browse/CAMEL-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramarajan R updated CAMEL-18476: Description: I have used [https://github.com/apache/camel-examples/tree/main/examples/artemis-large-messages] using AMQ 7.8.0 Broker Messages are getting processed but after processing the file is unable to delete from source location, tested in more than 1 windows systems facing the same I am using Camel 3.14.3 and Spring boot 2.6.6 using JAVA DSL, tested with Camel 3.18.1 and Spring boot 2.7.3 also when running with Camel XML routes are fine but we want to use Java DSL , Kindly help. Raising the concern in Zulip chat earlier. [https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/camel-file.20artemis.20large.20message.20example.20failing.20in.20windows] tion-poc/inbox0] o.a.c.c.file.GenericFileOnCompletion : Error during commit. Exchange[7D4CFE29E3F7515-0003]. Caused by: [org.apache.camel.component.file.GenericFileOperationFailedException - Error renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx to C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx] org.apache.camel.component.file.GenericFileOperationFailedException: Error renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx to C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx at org.apache.camel.component.file.FileOperations.renameFile(FileOperations.java:93) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:145) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:121) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileOnCompletion.processStrategyCommit(GenericFileOnCompletion.java:134) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileOnCompletion.onCompletion(GenericFileOnCompletion.java:86) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileOnCompletion.onComplete(GenericFileOnCompletion.java:60) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.support.UnitOfWorkHelper.doneSynchronization(UnitOfWorkHelper.java:104) ~[camel-support-3.14.3.jar:3.14.3] at org.apache.camel.support.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:93) ~[camel-support-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.DefaultUnitOfWork.done(DefaultUnitOfWork.java:238) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.support.UnitOfWorkHelper.doneUow(UnitOfWorkHelper.java:61) ~[camel-support-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:777) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:712) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.CamelInternalProcessor$AsyncAfterTask.done(CamelInternalProcessor.java:263) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.AsyncCallback.run(AsyncCallback.java:44) ~[camel-api-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:64) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.processor.Pipeline.process(Pipeline.java:184) ~[camel-core-processor-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:398) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:492) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:245) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:206) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:202) ~[camel-support-3.14.3.jar:3.14.3] at org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:116) ~[camel-support-3.14.3.jar:3.14.3] at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[na:na] at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) ~[na:na] at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) ~[na:na] at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[na:na] at
[jira] [Updated] (CAMEL-18476) Camel-file component is not able to delete the file after its archived
[ https://issues.apache.org/jira/browse/CAMEL-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramarajan R updated CAMEL-18476: Attachment: artemis-large-messages.zip > Camel-file component is not able to delete the file after its archived > -- > > Key: CAMEL-18476 > URL: https://issues.apache.org/jira/browse/CAMEL-18476 > Project: Camel > Issue Type: Bug > Components: camel-file >Affects Versions: 3.14.3, 3.18.1 >Reporter: Ramarajan R >Priority: Major > Attachments: artemis-large-messages.zip > > > I have used > [https://github.com/apache/camel-examples/tree/main/examples/artemis-large-messages] > using AMQ 7.8.0 Broker > Messages are getting processed but after processing the file is unable to > delete from source location, tested in more than 1 windows systems facing the > same > I am using Camel 3.14.3 and Spring boot 2.6.6 using JAVA DSL, > when running with Camel XML routes are fine but we want to use Java DSL , > Kindly help. > Raising the concern in Zulip chat earlier. > [https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/camel-file.20artemis.20large.20message.20example.20failing.20in.20windows] > > tion-poc/inbox0] o.a.c.c.file.GenericFileOnCompletion : Error during commit. > Exchange[7D4CFE29E3F7515-0003]. Caused by: > [org.apache.camel.component.file.GenericFileOperationFailedException - Error > renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx to > C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx] > org.apache.camel.component.file.GenericFileOperationFailedException: Error > renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx to > C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx > at > org.apache.camel.component.file.FileOperations.renameFile(FileOperations.java:93) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:145) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:121) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileOnCompletion.processStrategyCommit(GenericFileOnCompletion.java:134) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileOnCompletion.onCompletion(GenericFileOnCompletion.java:86) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileOnCompletion.onComplete(GenericFileOnCompletion.java:60) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.support.UnitOfWorkHelper.doneSynchronization(UnitOfWorkHelper.java:104) > ~[camel-support-3.14.3.jar:3.14.3] > at > org.apache.camel.support.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:93) > ~[camel-support-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.DefaultUnitOfWork.done(DefaultUnitOfWork.java:238) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at > org.apache.camel.support.UnitOfWorkHelper.doneUow(UnitOfWorkHelper.java:61) > ~[camel-support-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:777) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:712) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.CamelInternalProcessor$AsyncAfterTask.done(CamelInternalProcessor.java:263) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at org.apache.camel.AsyncCallback.run(AsyncCallback.java:44) > ~[camel-api-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:64) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at org.apache.camel.processor.Pipeline.process(Pipeline.java:184) > ~[camel-core-processor-3.14.3.jar:3.14.3] > at > org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:398) > ~[camel-base-engine-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:492) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:245) > ~[camel-file-3.14.3.jar:3.14.3] > at > org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:206) > ~[camel-file-3.14.3.jar:3.14.3] > at >
[jira] [Updated] (CAMEL-18476) Camel-file component is not able to delete the file after its archived
[ https://issues.apache.org/jira/browse/CAMEL-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ramarajan R updated CAMEL-18476: Description: I have used [https://github.com/apache/camel-examples/tree/main/examples/artemis-large-messages] using AMQ 7.8.0 Broker Messages are getting processed but after processing the file is unable to delete from source location, tested in more than 1 windows systems facing the same I am using Camel 3.14.3 and Spring boot 2.6.6 using JAVA DSL, when running with Camel XML routes are fine but we want to use Java DSL , Kindly help. Raising the concern in Zulip chat earlier. [https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/camel-file.20artemis.20large.20message.20example.20failing.20in.20windows] tion-poc/inbox0] o.a.c.c.file.GenericFileOnCompletion : Error during commit. Exchange[7D4CFE29E3F7515-0003]. Caused by: [org.apache.camel.component.file.GenericFileOperationFailedException - Error renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx to C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx] org.apache.camel.component.file.GenericFileOperationFailedException: Error renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx to C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx at org.apache.camel.component.file.FileOperations.renameFile(FileOperations.java:93) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:145) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:121) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileOnCompletion.processStrategyCommit(GenericFileOnCompletion.java:134) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileOnCompletion.onCompletion(GenericFileOnCompletion.java:86) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileOnCompletion.onComplete(GenericFileOnCompletion.java:60) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.support.UnitOfWorkHelper.doneSynchronization(UnitOfWorkHelper.java:104) ~[camel-support-3.14.3.jar:3.14.3] at org.apache.camel.support.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:93) ~[camel-support-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.DefaultUnitOfWork.done(DefaultUnitOfWork.java:238) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.support.UnitOfWorkHelper.doneUow(UnitOfWorkHelper.java:61) ~[camel-support-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:777) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:712) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.CamelInternalProcessor$AsyncAfterTask.done(CamelInternalProcessor.java:263) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.AsyncCallback.run(AsyncCallback.java:44) ~[camel-api-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:64) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.processor.Pipeline.process(Pipeline.java:184) ~[camel-core-processor-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:398) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:492) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:245) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:206) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:202) ~[camel-support-3.14.3.jar:3.14.3] at org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:116) ~[camel-support-3.14.3.jar:3.14.3] at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[na:na] at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) ~[na:na] at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) ~[na:na] at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[na:na] at
[jira] [Created] (CAMEL-18476) Camel-file component is not able to delete the file after its archived
Ramarajan R created CAMEL-18476: --- Summary: Camel-file component is not able to delete the file after its archived Key: CAMEL-18476 URL: https://issues.apache.org/jira/browse/CAMEL-18476 Project: Camel Issue Type: Bug Components: camel-file Affects Versions: 3.18.1, 3.14.3 Reporter: Ramarajan R I have used [https://github.com/apache/camel-examples/tree/main/examples/artemis-large-messages] using AMQ 7.8.0 Broker Messages are getting processed but after processing the file is unable to delete from source location tion-poc/inbox0] o.a.c.c.file.GenericFileOnCompletion : Error during commit. Exchange[7D4CFE29E3F7515-0003]. Caused by: [org.apache.camel.component.file.GenericFileOperationFailedException - Error renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx to C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx] org.apache.camel.component.file.GenericFileOperationFailedException: Error renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx to C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx at org.apache.camel.component.file.FileOperations.renameFile(FileOperations.java:93) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:145) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:121) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileOnCompletion.processStrategyCommit(GenericFileOnCompletion.java:134) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileOnCompletion.onCompletion(GenericFileOnCompletion.java:86) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileOnCompletion.onComplete(GenericFileOnCompletion.java:60) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.support.UnitOfWorkHelper.doneSynchronization(UnitOfWorkHelper.java:104) ~[camel-support-3.14.3.jar:3.14.3] at org.apache.camel.support.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:93) ~[camel-support-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.DefaultUnitOfWork.done(DefaultUnitOfWork.java:238) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.support.UnitOfWorkHelper.doneUow(UnitOfWorkHelper.java:61) ~[camel-support-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:777) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:712) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.CamelInternalProcessor$AsyncAfterTask.done(CamelInternalProcessor.java:263) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.AsyncCallback.run(AsyncCallback.java:44) ~[camel-api-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:64) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.processor.Pipeline.process(Pipeline.java:184) ~[camel-core-processor-3.14.3.jar:3.14.3] at org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:398) ~[camel-base-engine-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileConsumer.processExchange(GenericFileConsumer.java:492) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileConsumer.processBatch(GenericFileConsumer.java:245) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.component.file.GenericFileConsumer.poll(GenericFileConsumer.java:206) ~[camel-file-3.14.3.jar:3.14.3] at org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:202) ~[camel-support-3.14.3.jar:3.14.3] at org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:116) ~[camel-support-3.14.3.jar:3.14.3] at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[na:na] at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) ~[na:na] at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) ~[na:na] at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[na:na] at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[na:na] at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na] Caused by: java.io.IOException: Renaming file from
[jira] [Commented] (CAMEL-14880) Create a camel-couchdb3 component
[ https://issues.apache.org/jira/browse/CAMEL-14880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601211#comment-17601211 ] Arcadius Ahouansou commented on CAMEL-14880: Hello [~davsclaus] . It's not yet released :( There is an ongoing discussion on the topic at [https://github.com/lightcouch/LightCouch/issues/80] Feel free to comment there as well. Hopefully, we will get this issue resolved soon > Create a camel-couchdb3 component > - > > Key: CAMEL-14880 > URL: https://issues.apache.org/jira/browse/CAMEL-14880 > Project: Camel > Issue Type: New Feature >Affects Versions: 3.2.0 >Reporter: Alex Dettinger >Priority: Minor > Fix For: 3.x > > > As per the context of > [CAMEL-14822|https://issues.apache.org/jira/browse/CAMEL-14822], the > camel-couchdb component is exposed to the de-facto end of life of the > underlying couchdb library. As such, camel currently offers no support to > couchdb 3.x. > A way of dealing with such situation would be to create a camel-couchdb3 > component on top of [java-cloudant|https://github.com/cloudant/java-cloudant]. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18475) camel-core - FactoryFinder for period background tasks
Claus Ibsen created CAMEL-18475: --- Summary: camel-core - FactoryFinder for period background tasks Key: CAMEL-18475 URL: https://issues.apache.org/jira/browse/CAMEL-18475 Project: Camel Issue Type: New Feature Components: camel-core Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.19.0 We need a plugin that allows to define smaller custom tasks that needs to run periodically and managed by camel context automatic. We can use TimerListenerManager to trigger, and then we need the factory finder annotations to discover/load the plugins -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18267) Vault Support: Trigger a reload of properties from a particular Vault source based on events
[ https://issues.apache.org/jira/browse/CAMEL-18267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18267. - Resolution: Fixed > Vault Support: Trigger a reload of properties from a particular Vault source > based on events > > > Key: CAMEL-18267 > URL: https://issues.apache.org/jira/browse/CAMEL-18267 > Project: Camel > Issue Type: New Feature > Components: camel-core >Reporter: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > > In case of rotation, update, patch etc. We need to trigger a reload. > This might be a service running with the properties source or something we > could enable on-demand. > In this way we could react to events. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18240) [DOCS] FHIR component - documentation issues
[
https://issues.apache.org/jira/browse/CAMEL-18240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18240.
-
Resolution: Fixed
> [DOCS] FHIR component - documentation issues
>
>
> Key: CAMEL-18240
> URL: https://issues.apache.org/jira/browse/CAMEL-18240
> Project: Camel
> Issue Type: Task
> Components: camel-fhir
>Affects Versions: 3.14.0
>Reporter: Mario Majernik
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.18.3, 3.19.0
>
>
> * Api *operation* contains incomplete URL in the description:
> ** {code:java}
> API for extended FHIR operations https://www{code}
> ** Docs:
> https://camel.apache.org/components/3.14.x/fhir-component.html#_api_parameters_13_apis
> * [PROPOSITION] Each API method contains method signatures. They are shown
> as one long string which is not readable very well. I.E.
> **
> {code:java}
> org.hl7.fhir.instance.model.api.IBaseResource
> resourceByUrl(Class resource,
> org.hl7.fhir.instance.model.api.IIdType iUrl, String ifVersionMatches,
> Boolean returnNull, org.hl7.fhir.instance.model.api.IBaseResource
> returnResource, Boolean throwError,
> java.util.Map
> extraParameters); {code}
> Would be much more readable if each parameter would be on separate line:
> *
> **
> {code:java}
> org.hl7.fhir.instance.model.api.IBaseResource
> resourceByUrl(Class resource,
> org.hl7.fhir.instance.model.api.IIdType iUrl,
> String ifVersionMatches,
> Boolean returnNull,
> org.hl7.fhir.instance.model.api.IBaseResource returnResource,
> Boolean throwError,
> java.util.Map
> extraParameters); {code}
> * APIs read, update, validate - their methods are missing descriptions at all
> ** i.e.:
> [https://camel.apache.org/components/3.14.x/fhir-component.html#_api_validate]
> * All API operation's methods - Alias column is always empty --> could be
> erased from tables.
> ** i.e. method resource and its table:
> ***
> https://camel.apache.org/components/3.14.x/fhir-component.html#_api_validate
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18240) [DOCS] FHIR component - documentation issues
[
https://issues.apache.org/jira/browse/CAMEL-18240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601178#comment-17601178
]
Claus Ibsen commented on CAMEL-18240:
-
I created a ticket about the website updates
I have added the missing docs
> [DOCS] FHIR component - documentation issues
>
>
> Key: CAMEL-18240
> URL: https://issues.apache.org/jira/browse/CAMEL-18240
> Project: Camel
> Issue Type: Task
> Components: camel-fhir
>Affects Versions: 3.14.0
>Reporter: Mario Majernik
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.18.3, 3.19.0
>
>
> * Api *operation* contains incomplete URL in the description:
> ** {code:java}
> API for extended FHIR operations https://www{code}
> ** Docs:
> https://camel.apache.org/components/3.14.x/fhir-component.html#_api_parameters_13_apis
> * [PROPOSITION] Each API method contains method signatures. They are shown
> as one long string which is not readable very well. I.E.
> **
> {code:java}
> org.hl7.fhir.instance.model.api.IBaseResource
> resourceByUrl(Class resource,
> org.hl7.fhir.instance.model.api.IIdType iUrl, String ifVersionMatches,
> Boolean returnNull, org.hl7.fhir.instance.model.api.IBaseResource
> returnResource, Boolean throwError,
> java.util.Map
> extraParameters); {code}
> Would be much more readable if each parameter would be on separate line:
> *
> **
> {code:java}
> org.hl7.fhir.instance.model.api.IBaseResource
> resourceByUrl(Class resource,
> org.hl7.fhir.instance.model.api.IIdType iUrl,
> String ifVersionMatches,
> Boolean returnNull,
> org.hl7.fhir.instance.model.api.IBaseResource returnResource,
> Boolean throwError,
> java.util.Map
> extraParameters); {code}
> * APIs read, update, validate - their methods are missing descriptions at all
> ** i.e.:
> [https://camel.apache.org/components/3.14.x/fhir-component.html#_api_validate]
> * All API operation's methods - Alias column is always empty --> could be
> erased from tables.
> ** i.e. method resource and its table:
> ***
> https://camel.apache.org/components/3.14.x/fhir-component.html#_api_validate
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18474) documentation for api-components - Cleaner method signature
Claus Ibsen created CAMEL-18474: --- Summary: documentation for api-components - Cleaner method signature Key: CAMEL-18474 URL: https://issues.apache.org/jira/browse/CAMEL-18474 Project: Camel Issue Type: Improvement Components: documentation Reporter: Claus Ibsen Fix For: 3.x See CAMEL-18240 We can do - method signatures to show with each parameter in a new line, or how a code editor would format the code - only show alias table if there are alias - sort the parameters table according to index in the method signature (instead of a..z) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-15820) Hazelcast : improve search or create HazelcastInstance
[ https://issues.apache.org/jira/browse/CAMEL-15820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601177#comment-17601177 ] Zineb Bendhiba commented on CAMEL-15820: I guess yes, I just don't know how to improve without doing beraking changes > Hazelcast : improve search or create HazelcastInstance > -- > > Key: CAMEL-15820 > URL: https://issues.apache.org/jira/browse/CAMEL-15820 > Project: Camel > Issue Type: Improvement >Reporter: Zineb Bendhiba >Assignee: Zineb Bendhiba >Priority: Minor > > Improve some code in the component, to compile in native mode for > camel-quarkus. > * The 2 methods *getOrCreateHzInstance* and *getOrCreateHzClientInstance* in > the class *HazelcastDefaultComponent*. vs parameters within the Endpoint. > Main point : Use parameters instead of reflection -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18240) [DOCS] FHIR component - documentation issues
[
https://issues.apache.org/jira/browse/CAMEL-18240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18240:
Fix Version/s: 3.18.3
> [DOCS] FHIR component - documentation issues
>
>
> Key: CAMEL-18240
> URL: https://issues.apache.org/jira/browse/CAMEL-18240
> Project: Camel
> Issue Type: Task
> Components: camel-fhir
>Affects Versions: 3.14.0
>Reporter: Mario Majernik
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.18.3, 3.19.0
>
>
> * Api *operation* contains incomplete URL in the description:
> ** {code:java}
> API for extended FHIR operations https://www{code}
> ** Docs:
> https://camel.apache.org/components/3.14.x/fhir-component.html#_api_parameters_13_apis
> * [PROPOSITION] Each API method contains method signatures. They are shown
> as one long string which is not readable very well. I.E.
> **
> {code:java}
> org.hl7.fhir.instance.model.api.IBaseResource
> resourceByUrl(Class resource,
> org.hl7.fhir.instance.model.api.IIdType iUrl, String ifVersionMatches,
> Boolean returnNull, org.hl7.fhir.instance.model.api.IBaseResource
> returnResource, Boolean throwError,
> java.util.Map
> extraParameters); {code}
> Would be much more readable if each parameter would be on separate line:
> *
> **
> {code:java}
> org.hl7.fhir.instance.model.api.IBaseResource
> resourceByUrl(Class resource,
> org.hl7.fhir.instance.model.api.IIdType iUrl,
> String ifVersionMatches,
> Boolean returnNull,
> org.hl7.fhir.instance.model.api.IBaseResource returnResource,
> Boolean throwError,
> java.util.Map
> extraParameters); {code}
> * APIs read, update, validate - their methods are missing descriptions at all
> ** i.e.:
> [https://camel.apache.org/components/3.14.x/fhir-component.html#_api_validate]
> * All API operation's methods - Alias column is always empty --> could be
> erased from tables.
> ** i.e. method resource and its table:
> ***
> https://camel.apache.org/components/3.14.x/fhir-component.html#_api_validate
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18049) Camel Webhook - error to set Webhook URL
[
https://issues.apache.org/jira/browse/CAMEL-18049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zineb Bendhiba resolved CAMEL-18049.
Resolution: Fixed
> Camel Webhook - error to set Webhook URL
>
>
> Key: CAMEL-18049
> URL: https://issues.apache.org/jira/browse/CAMEL-18049
> Project: Camel
> Issue Type: Bug
> Components: camel-webhook
>Reporter: Zineb Bendhiba
>Assignee: Zineb Bendhiba
>Priority: Minor
> Fix For: 3.18.2, 3.19.0
>
>
> The method that is supposed to set the webhook URL seems trying to delete the
> webhook URL.
> refering to this method :
> [https://github.com/apache/camel/blob/f7c953c790337322f9db3ec792a5410e3f6923cb/components/camel-telegram/src/main/java/org/apache/camel/component/telegram/service/TelegramServiceRestBotAPIAdapter.java#L184]
>
> While trying to execute the Spring Boot webhook example here:
> [https://github.com/apache/camel-spring-boot-examples/tree/main/webhook
> :|https://github.com/apache/camel-spring-boot-examples/tree/main/webhook]
> the API responds :
> {code:java}
> WebhookResult{ok=true, result=true, description='Webhook is already deleted'}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18049) Camel Webhook - error to set Webhook URL
[
https://issues.apache.org/jira/browse/CAMEL-18049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zineb Bendhiba updated CAMEL-18049:
---
Fix Version/s: 3.18.2
(was: 3.18.3)
> Camel Webhook - error to set Webhook URL
>
>
> Key: CAMEL-18049
> URL: https://issues.apache.org/jira/browse/CAMEL-18049
> Project: Camel
> Issue Type: Bug
> Components: camel-webhook
>Reporter: Zineb Bendhiba
>Assignee: Zineb Bendhiba
>Priority: Minor
> Fix For: 3.18.2, 3.19.0
>
>
> The method that is supposed to set the webhook URL seems trying to delete the
> webhook URL.
> refering to this method :
> [https://github.com/apache/camel/blob/f7c953c790337322f9db3ec792a5410e3f6923cb/components/camel-telegram/src/main/java/org/apache/camel/component/telegram/service/TelegramServiceRestBotAPIAdapter.java#L184]
>
> While trying to execute the Spring Boot webhook example here:
> [https://github.com/apache/camel-spring-boot-examples/tree/main/webhook
> :|https://github.com/apache/camel-spring-boot-examples/tree/main/webhook]
> the API responds :
> {code:java}
> WebhookResult{ok=true, result=true, description='Webhook is already deleted'}
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work started] (CAMEL-18473) Knative component : CloudEvents have wrong time format
[
https://issues.apache.org/jira/browse/CAMEL-18473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-18473 started by Zineb Bendhiba.
--
> Knative component : CloudEvents have wrong time format
> --
>
> Key: CAMEL-18473
> URL: https://issues.apache.org/jira/browse/CAMEL-18473
> Project: Camel
> Issue Type: Bug
> Components: camel-knative
>Affects Versions: 3.18.1
>Reporter: Zineb Bendhiba
>Assignee: Zineb Bendhiba
>Priority: Major
> Fix For: 3.18.3
>
>
>
> When trying camel knative component with InMemory channels, we can't see the
> bug because this one doesn't validate the event.
> Outside of this use case when the event is validated on knative, it seems
> that the time has wrong DateFormat.
> For instance, if using the component with a broker, we can't produce an event
> with camel-knative, and this is the log in knative environment :
>
> {code:java}
> {"level":"warn","ts":"2022-09-06T14:35:10.587Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:137","msg":"failed
> to extract event from request","error":"invalid value for time:
> \"22022-08-31T12:00:33.253+02:00\""} {code}
> This is the valid DateFormat, according to [CloudEvents
> spec|[https://github.com/cloudevents/spec]]
>
> {code:java}
> "time" : "2018-04-05T17:31:00Z", {code}
> This corresponds in the Java DateTimeFormatter class to [#ISO_INSTANT].
> However, in camel-knative producer uses [#ISO_OFFSET_DATE_TIME]
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18473) Knative component : CloudEvents have wrong time format
[
https://issues.apache.org/jira/browse/CAMEL-18473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zineb Bendhiba updated CAMEL-18473:
---
Description:
When trying camel knative component with InMemory channels, we can't see the
bug because this one doesn't validate the event.
Outside of this use case when the event is validated on knative, it seems that
the time has wrong DateFormat.
For instance, if using the component with a broker, we can't produce an event
with camel-knative, and this is the log in knative environment :
{code:java}
{"level":"warn","ts":"2022-09-06T14:35:10.587Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:137","msg":"failed
to extract event from request","error":"invalid value for time:
\"22022-08-31T12:00:33.253+02:00\""} {code}
This is the valid DateFormat, according to [CloudEvents
spec|[https://github.com/cloudevents/spec]]
{code:java}
"time" : "2018-04-05T17:31:00Z", {code}
This corresponds in the Java DateTimeFormatter class to [#ISO_INSTANT].
However, in camel-knative producer uses [#ISO_OFFSET_DATE_TIME]
was:
When trying camel knative component with InMemory channels, we can't see the
bug because this one doesn't validate the event.
Outside of this use case when the event is validated on knative, it seems that
the time has wrong DateFormat.
For instance, if using the component with a broker, we can't produce an event
with camel-knative, and this is the log in knative environment :
{code:java}
{"level":"warn","ts":"2022-09-06T14:35:10.587Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:137","msg":"failed
to extract event from request","error":"invalid value for time:
\"22022-08-31T12:00:33.253+02:00\""} {code}
This is the valid DateFormat, according to [CloudEvents
spec|[https://github.com/cloudevents/spec]]
{code:java}
"time" : "2018-04-05T17:31:00Z", {code}
This corresponds in the Java DateTimeFormatter class to
[ISO_INSTANT|#ISO_INSTANT].]
However, in camel-knative producer uses
[ISO_OFFSET_DATE_TIME|#ISO_OFFSET_DATE_TIME]],]
> Knative component : CloudEvents have wrong time format
> --
>
> Key: CAMEL-18473
> URL: https://issues.apache.org/jira/browse/CAMEL-18473
> Project: Camel
> Issue Type: Bug
> Components: camel-knative
>Affects Versions: 3.18.1
>Reporter: Zineb Bendhiba
>Assignee: Zineb Bendhiba
>Priority: Major
> Fix For: 3.18.3
>
>
>
> When trying camel knative component with InMemory channels, we can't see the
> bug because this one doesn't validate the event.
> Outside of this use case when the event is validated on knative, it seems
> that the time has wrong DateFormat.
> For instance, if using the component with a broker, we can't produce an event
> with camel-knative, and this is the log in knative environment :
>
> {code:java}
> {"level":"warn","ts":"2022-09-06T14:35:10.587Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:137","msg":"failed
> to extract event from request","error":"invalid value for time:
> \"22022-08-31T12:00:33.253+02:00\""} {code}
> This is the valid DateFormat, according to [CloudEvents
> spec|[https://github.com/cloudevents/spec]]
>
> {code:java}
> "time" : "2018-04-05T17:31:00Z", {code}
> This corresponds in the Java DateTimeFormatter class to [#ISO_INSTANT].
> However, in camel-knative producer uses [#ISO_OFFSET_DATE_TIME]
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18473) Knative component : CloudEvents have wrong time format
[
https://issues.apache.org/jira/browse/CAMEL-18473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zineb Bendhiba updated CAMEL-18473:
---
Description:
When trying camel knative component with InMemory channels, we can't see the
bug because this one doesn't validate the event.
Outside of this use case when the event is validated on knative, it seems that
the time has wrong DateFormat.
For instance, if using the component with a broker, we can't produce an event
with camel-knative, and this is the log in knative environment :
{code:java}
{"level":"warn","ts":"2022-09-06T14:35:10.587Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:137","msg":"failed
to extract event from request","error":"invalid value for time:
\"22022-08-31T12:00:33.253+02:00\""} {code}
This is the valid DateFormat, according to [CloudEvents
spec|[https://github.com/cloudevents/spec]]
{code:java}
"time" : "2018-04-05T17:31:00Z", {code}
This corresponds in the Java DateTimeFormatter class to
[ISO_INSTANT|#ISO_INSTANT].]
However, in camel-knative producer uses
[ISO_OFFSET_DATE_TIME|#ISO_OFFSET_DATE_TIME]],]
was:
When trying camel knative component with InMemory channels, we can't see the
bug because this one doesn't validate the event.
Outside of this use case when the event is validated on knative, it seems that
the time has wrong DateFormat.
For instance, if using the component with a broker, we can't produce an event
with camel-knative, and this is the log in knative environment :
{code:java}
{"level":"warn","ts":"2022-09-06T14:35:10.587Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:137","msg":"failed
to extract event from request","error":"invalid value for time:
\"22022-08-31T12:00:33.253+02:00\""} {code}
This is the valid DateFormat, according to [CloudEvents
spec|[https://github.com/cloudevents/spec]:]
{code:java}
"time" : "2018-04-05T17:31:00Z", {code}
This corresponds in the Java DateTimeFormatter class to
[ISO_INSTANT|[https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html#ISO_INSTANT].]
However, in camel-knative producer uses
[ISO_OFFSET_DATE_TIME|[https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html#ISO_OFFSET_DATE_TIME]|https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html#ISO_OFFSET_DATE_TIME],]
> Knative component : CloudEvents have wrong time format
> --
>
> Key: CAMEL-18473
> URL: https://issues.apache.org/jira/browse/CAMEL-18473
> Project: Camel
> Issue Type: Bug
> Components: camel-knative
>Affects Versions: 3.18.1
>Reporter: Zineb Bendhiba
>Assignee: Zineb Bendhiba
>Priority: Major
> Fix For: 3.18.3
>
>
>
> When trying camel knative component with InMemory channels, we can't see the
> bug because this one doesn't validate the event.
> Outside of this use case when the event is validated on knative, it seems
> that the time has wrong DateFormat.
> For instance, if using the component with a broker, we can't produce an event
> with camel-knative, and this is the log in knative environment :
>
> {code:java}
> {"level":"warn","ts":"2022-09-06T14:35:10.587Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:137","msg":"failed
> to extract event from request","error":"invalid value for time:
> \"22022-08-31T12:00:33.253+02:00\""} {code}
> This is the valid DateFormat, according to [CloudEvents
> spec|[https://github.com/cloudevents/spec]]
>
> {code:java}
> "time" : "2018-04-05T17:31:00Z", {code}
> This corresponds in the Java DateTimeFormatter class to
> [ISO_INSTANT|#ISO_INSTANT].]
> However, in camel-knative producer uses
> [ISO_OFFSET_DATE_TIME|#ISO_OFFSET_DATE_TIME]],]
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18473) Knative component : CloudEvents have wrong time format
Zineb Bendhiba created CAMEL-18473:
--
Summary: Knative component : CloudEvents have wrong time format
Key: CAMEL-18473
URL: https://issues.apache.org/jira/browse/CAMEL-18473
Project: Camel
Issue Type: Bug
Components: camel-knative
Affects Versions: 3.18.1
Reporter: Zineb Bendhiba
Assignee: Zineb Bendhiba
Fix For: 3.18.3
When trying camel knative component with InMemory channels, we can't see the
bug because this one doesn't validate the event.
Outside of this use case when the event is validated on knative, it seems that
the time has wrong DateFormat.
For instance, if using the component with a broker, we can't produce an event
with camel-knative, and this is the log in knative environment :
{code:java}
{"level":"warn","ts":"2022-09-06T14:35:10.587Z","logger":"mt_broker_ingress","caller":"ingress/ingress_handler.go:137","msg":"failed
to extract event from request","error":"invalid value for time:
\"22022-08-31T12:00:33.253+02:00\""} {code}
This is the valid DateFormat, according to [CloudEvents
spec|[https://github.com/cloudevents/spec]:]
{code:java}
"time" : "2018-04-05T17:31:00Z", {code}
This corresponds in the Java DateTimeFormatter class to
[ISO_INSTANT|[https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html#ISO_INSTANT].]
However, in camel-knative producer uses
[ISO_OFFSET_DATE_TIME|[https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html#ISO_OFFSET_DATE_TIME]|https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html#ISO_OFFSET_DATE_TIME],]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18427) Camel Debezium with Postgres on Spring Boot doesn't work
[
https://issues.apache.org/jira/browse/CAMEL-18427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601162#comment-17601162
]
michael elbaz commented on CAMEL-18427:
---
Yeah maybe i don't known camel documentation don't say that
!image-2022-09-07-08-53-06-942.png|width=620,height=281!
By the way with previous camel version is was working not now
> Camel Debezium with Postgres on Spring Boot doesn't work
>
>
> Key: CAMEL-18427
> URL: https://issues.apache.org/jira/browse/CAMEL-18427
> Project: Camel
> Issue Type: Bug
> Components: camel-debezium
>Affects Versions: 3.13.0, 3.18.1
> Environment: Jdk 17
> Windows 10
> Spring boot
>Reporter: michael elbaz
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.18.3, 3.19.0
>
> Attachments: camel-debezium-postgres.zip,
> image-2022-08-24-12-12-27-542.png, image-2022-08-24-12-19-55-853.png,
> image-2022-09-07-08-53-06-942.png
>
>
> From camel 3.13.0 Camel Debezium simply not working is work perfectly with
> camel older than 3.13.0
> (related to this ticket i think
> https://issues.apache.org/jira/browse/CAMEL-17135)
> here the code
> {code:java}
> @Override
> public void configure() throws Exception {
> String DATABASE_READER = "debezium-postgres:localhost?"
> + "databaseHostname=localhost"
> + "=5432"
> + "=postgres"
> + "=test"
> + "=test"
> + "=localhost"
> + "=public"
> + "=public.*"
> + "=/tmp/offset-file-1.dat"
> + "=1"
> + "=pgoutput";
> from(DATABASE_READER)
> .routeId("debeziumPGRoute")
> .log("Response : ${body}");
> }
> {code}
> !image-2022-08-24-12-12-27-542.png|width=949,height=240!
> I check this [changelog|https://camel.apache.org/releases/release-3.13.0/]
> !image-2022-08-24-12-19-55-853.png|width=803,height=402!
> the pom file
> {code:java}
>
> org.apache.camel
> camel-debezium-postgres
>
>
> org.apache.camel.springboot
> camel-debezium-postgres-starter
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18427) Camel Debezium with Postgres on Spring Boot doesn't work
[
https://issues.apache.org/jira/browse/CAMEL-18427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
michael elbaz updated CAMEL-18427:
--
Attachment: image-2022-09-07-08-53-06-942.png
> Camel Debezium with Postgres on Spring Boot doesn't work
>
>
> Key: CAMEL-18427
> URL: https://issues.apache.org/jira/browse/CAMEL-18427
> Project: Camel
> Issue Type: Bug
> Components: camel-debezium
>Affects Versions: 3.13.0, 3.18.1
> Environment: Jdk 17
> Windows 10
> Spring boot
>Reporter: michael elbaz
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.18.3, 3.19.0
>
> Attachments: camel-debezium-postgres.zip,
> image-2022-08-24-12-12-27-542.png, image-2022-08-24-12-19-55-853.png,
> image-2022-09-07-08-53-06-942.png
>
>
> From camel 3.13.0 Camel Debezium simply not working is work perfectly with
> camel older than 3.13.0
> (related to this ticket i think
> https://issues.apache.org/jira/browse/CAMEL-17135)
> here the code
> {code:java}
> @Override
> public void configure() throws Exception {
> String DATABASE_READER = "debezium-postgres:localhost?"
> + "databaseHostname=localhost"
> + "=5432"
> + "=postgres"
> + "=test"
> + "=test"
> + "=localhost"
> + "=public"
> + "=public.*"
> + "=/tmp/offset-file-1.dat"
> + "=1"
> + "=pgoutput";
> from(DATABASE_READER)
> .routeId("debeziumPGRoute")
> .log("Response : ${body}");
> }
> {code}
> !image-2022-08-24-12-12-27-542.png|width=949,height=240!
> I check this [changelog|https://camel.apache.org/releases/release-3.13.0/]
> !image-2022-08-24-12-19-55-853.png|width=803,height=402!
> the pom file
> {code:java}
>
> org.apache.camel
> camel-debezium-postgres
>
>
> org.apache.camel.springboot
> camel-debezium-postgres-starter
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
