[jira] [Updated] (CAMEL-18208) vault: allow to retrieve a specific secret version/revision
[
https://issues.apache.org/jira/browse/CAMEL-18208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-18208:
-
Fix Version/s: 3.19.0
> vault: allow to retrieve a specific secret version/revision
> ---
>
> Key: CAMEL-18208
> URL: https://issues.apache.org/jira/browse/CAMEL-18208
> Project: Camel
> Issue Type: Improvement
>Reporter: Luca Burgazzoli
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 3.19.0
>
>
> The vaults for which we have support in Apache Camel support versioned
> secrets (i.e. [1][2]) and it would be very useful to have an option to
> include the verison/revision of the secret in the vault property syntax, as
> example:
> {{aws:username@123}}
> This would mean to get the secret named username and version 123 from the
> aws vault.
> [1]
> https://docs.aws.amazon.com/secretsmanager/latest/apireference/API_GetSecretValue.html
> [2]
> https://learn.hashicorp.com/tutorials/vault/versioned-kv#step-7-configure-automatic-data-deletion
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18208) vault: allow to retrieve a specific secret version/revision
[
https://issues.apache.org/jira/browse/CAMEL-18208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-18208.
--
Resolution: Fixed
> vault: allow to retrieve a specific secret version/revision
> ---
>
> Key: CAMEL-18208
> URL: https://issues.apache.org/jira/browse/CAMEL-18208
> Project: Camel
> Issue Type: Improvement
>Reporter: Luca Burgazzoli
>Assignee: Andrea Cosentino
>Priority: Minor
> Fix For: 3.19.0
>
>
> The vaults for which we have support in Apache Camel support versioned
> secrets (i.e. [1][2]) and it would be very useful to have an option to
> include the verison/revision of the secret in the vault property syntax, as
> example:
> {{aws:username@123}}
> This would mean to get the secret named username and version 123 from the
> aws vault.
> [1]
> https://docs.aws.amazon.com/secretsmanager/latest/apireference/API_GetSecretValue.html
> [2]
> https://learn.hashicorp.com/tutorials/vault/versioned-kv#step-7-configure-automatic-data-deletion
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-17688) Support ability to load properties from Vault/Secrets cloud services - Hashicorp Vault
[ https://issues.apache.org/jira/browse/CAMEL-17688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-17688. -- Resolution: Fixed > Support ability to load properties from Vault/Secrets cloud services - > Hashicorp Vault > -- > > Key: CAMEL-17688 > URL: https://issues.apache.org/jira/browse/CAMEL-17688 > Project: Camel > Issue Type: Sub-task >Reporter: Andrea Cosentino >Assignee: Andrea Cosentino >Priority: Major > Fix For: 3.19.0 > > > We need an Hashicorp Vault component, based on spring vault library. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18270) IMAP skipFailedMessage=true, but route blocked if mail is moved while download
[
https://issues.apache.org/jira/browse/CAMEL-18270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino updated CAMEL-18270:
-
Priority: Major (was: Critical)
> IMAP skipFailedMessage=true, but route blocked if mail is moved while download
> --
>
> Key: CAMEL-18270
> URL: https://issues.apache.org/jira/browse/CAMEL-18270
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 3.18.0
>Reporter: Florian Fiby
>Priority: Major
>
>
> Our imap mail route on the production system gets blocked when someone or an
> other systems moves / deletes an email from the inbox, while the camel mail
> route is loading the mail. As we do not have full control on the mailboxes we
> enabled skipFailedMessage but the issue remains.
> The following exception is written is the log, but the mail consumer is
> blocked. The issue can only be resolved by a restart of the service.
> {code:java}
> 2022-07-14 09:17:28.714 WARN 5465 --- [fice365.com:993]
> o.a.c.i.engine.DefaultReactiveExecutor : Error executing reactive work due
> to Error accessing headers due to: Cannot load header. This exception is
> ignored.
> org.apache.camel.RuntimeCamelException: Error accessing headers due to:
> Cannot load header
> at
> org.apache.camel.component.mail.MailMessage.populateInitialHeaders(MailMessage.java:107)
> ~[camel-mail-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.DefaultMessage.createHeaders(DefaultMessage.java:331)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.DefaultMessage.hasHeaders(DefaultMessage.java:305)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.AbstractExchange.copy(AbstractExchange.java:140)
> ~[camel-support-3.18.0.jar:3.18.0]
> at org.apache.camel.support.DefaultExchange.copy(DefaultExchange.java:27)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.ExchangeHelper.createCopy(ExchangeHelper.java:322)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.defensiveCopyExchangeIfNeeded(RedeliveryErrorHandler.java:304)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.prepare(RedeliveryErrorHandler.java:680)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.PrototypeTaskFactory.acquire(PrototypeTaskFactory.java:29)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:210)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:399)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at
> org.apache.camel.processor.Pipeline$PipelineTask.run(Pipeline.java:109)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:189)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:61)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:184)
> ~[camel-core-processor-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:399)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at
> org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:83)
> ~[camel-base-engine-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.AsyncProcessorSupport.process(AsyncProcessorSupport.java:41)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.component.mail.MailConsumer.processExchange(MailConsumer.java:451)
> ~[camel-mail-3.18.0.jar:3.18.0]
> at
> org.apache.camel.component.mail.MailConsumer.processBatch(MailConsumer.java:260)
> ~[camel-mail-3.18.0.jar:3.18.0]
> at
> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:165)
> ~[camel-mail-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:202)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:116)
> ~[camel-support-3.18.0.jar:3.18.0]
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> ~[na:na]
> at
> java.base/java.util.concurrent.FutureTask.runAndReset$$$capture(FutureTask.java:305)
> ~[na:na]
> at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java)
[jira] [Updated] (CAMEL-18270) IMAP skipFailedMessage=true, but route blocked if mail is moved while download
[
https://issues.apache.org/jira/browse/CAMEL-18270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Fiby updated CAMEL-18270:
-
Description:
Our imap mail route on the production system gets blocked when someone or an
other systems moves / deletes an email from the inbox, while the camel mail
route is loading the mail. As we do not have full control on the mailboxes we
enabled skipFailedMessage but the issue remains.
The following exception is written is the log, but the mail consumer is
blocked. The issue can only be resolved by a restart of the service.
{code:java}
2022-07-14 09:17:28.714 WARN 5465 --- [fice365.com:993]
o.a.c.i.engine.DefaultReactiveExecutor : Error executing reactive work due to
Error accessing headers due to: Cannot load header. This exception is ignored.
org.apache.camel.RuntimeCamelException: Error accessing headers due to: Cannot
load header
at
org.apache.camel.component.mail.MailMessage.populateInitialHeaders(MailMessage.java:107)
~[camel-mail-3.18.0.jar:3.18.0]
at
org.apache.camel.support.DefaultMessage.createHeaders(DefaultMessage.java:331)
~[camel-support-3.18.0.jar:3.18.0]
at
org.apache.camel.support.DefaultMessage.hasHeaders(DefaultMessage.java:305)
~[camel-support-3.18.0.jar:3.18.0]
at
org.apache.camel.support.AbstractExchange.copy(AbstractExchange.java:140)
~[camel-support-3.18.0.jar:3.18.0]
at org.apache.camel.support.DefaultExchange.copy(DefaultExchange.java:27)
~[camel-support-3.18.0.jar:3.18.0]
at
org.apache.camel.support.ExchangeHelper.createCopy(ExchangeHelper.java:322)
~[camel-support-3.18.0.jar:3.18.0]
at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.defensiveCopyExchangeIfNeeded(RedeliveryErrorHandler.java:304)
~[camel-core-processor-3.18.0.jar:3.18.0]
at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.prepare(RedeliveryErrorHandler.java:680)
~[camel-core-processor-3.18.0.jar:3.18.0]
at
org.apache.camel.processor.PrototypeTaskFactory.acquire(PrototypeTaskFactory.java:29)
~[camel-core-processor-3.18.0.jar:3.18.0]
at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:210)
~[camel-core-processor-3.18.0.jar:3.18.0]
at
org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:399)
~[camel-base-engine-3.18.0.jar:3.18.0]
at org.apache.camel.processor.Pipeline$PipelineTask.run(Pipeline.java:109)
~[camel-core-processor-3.18.0.jar:3.18.0]
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:189)
~[camel-base-engine-3.18.0.jar:3.18.0]
at
org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:61)
~[camel-base-engine-3.18.0.jar:3.18.0]
at org.apache.camel.processor.Pipeline.process(Pipeline.java:184)
~[camel-core-processor-3.18.0.jar:3.18.0]
at
org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:399)
~[camel-base-engine-3.18.0.jar:3.18.0]
at
org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:83)
~[camel-base-engine-3.18.0.jar:3.18.0]
at
org.apache.camel.support.AsyncProcessorSupport.process(AsyncProcessorSupport.java:41)
~[camel-support-3.18.0.jar:3.18.0]
at
org.apache.camel.component.mail.MailConsumer.processExchange(MailConsumer.java:451)
~[camel-mail-3.18.0.jar:3.18.0]
at
org.apache.camel.component.mail.MailConsumer.processBatch(MailConsumer.java:260)
~[camel-mail-3.18.0.jar:3.18.0]
at org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:165)
~[camel-mail-3.18.0.jar:3.18.0]
at
org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:202)
~[camel-support-3.18.0.jar:3.18.0]
at
org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:116)
~[camel-support-3.18.0.jar:3.18.0]
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
~[na:na]
at
java.base/java.util.concurrent.FutureTask.runAndReset$$$capture(FutureTask.java:305)
~[na:na]
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java)
~[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:829) ~[na:na]
Caused by: javax.mail.MessagingException: Cannot load header
at com.sun.mail.imap.IMAPMessage.loadHeaders(IMAPMessage.java:1583)
~[jakarta.mail-1.6.5.jar:1.6.5]
at
[jira] [Updated] (CAMEL-18271) [Camel Spring Boot Examples] Infinispan example cannot be built
[
https://issues.apache.org/jira/browse/CAMEL-18271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Carletti updated CAMEL-18271:
---
Description:
Since dependency _infinispan-core_ has been replaced with _infinispan-commons_
in the _camel-infinispan-common_ component
([commit|https://github.com/apache/camel/commit/f0d22792803a221a016092f606fe49c326f23492]),
the artifact _org.apache.camel:camel-infinispan_ doesn't contain anymore the
dependency _org.infinispan:infinispan-core_
maven dependency tree for 3.17.0-SNAPSHOT (starting from
{_}org.apache.camel.springboot:camel-infinispan-starter{_})
{code:bash}
+-
org.apache.camel.springboot:camel-infinispan-starter:jar:3.17.0-SNAPSHOT:compile
| \- org.apache.camel:camel-infinispan:jar:3.17.0-SNAPSHOT:compile
| +- org.apache.camel:camel-infinispan-common:jar:3.17.0-SNAPSHOT:compile
| | +- org.infinispan:infinispan-core:jar:12.1.11.Final:compile
| | | +- org.jgroups:jgroups:jar:4.2.12.Final:compile
| | | +- com.github.ben-manes.caffeine:caffeine:jar:2.9.3:compile
.
{code}
maven dependency tree for 3.18.0 (starting from
{_}org.apache.camel.springboot:camel-infinispan-starter{_})
{code:bash}
+- org.apache.camel.springboot:camel-infinispan-starter:jar:3.18.0:compile
| \- org.apache.camel:camel-infinispan:jar:3.18.0:compile
| +- org.apache.camel:camel-infinispan-common:jar:3.18.0:compile
| | +- org.infinispan:infinispan-commons:jar:13.0.10.Final:compile
| | | +- com.github.ben-manes.caffeine:caffeine:jar:2.9.3:compile
.
{code}
this change causes the
[camel-example-spring-boot-infinispan|https://github.com/apache/camel-spring-boot-examples/tree/main/infinispan]
compilation failure because of the usage of the class
_org.infinispan.configuration.cache.CacheMode_ packaged into _infinispan-core_
dependency
([import|https://github.com/apache/camel-spring-boot-examples/blob/main/infinispan/src/main/java/org/apache/camel/example/springboot/infinispan/Application.java#L31])
was:
Since dependency _infinispan-core_ has been replaced with _infinispan-commons_
in the _camel-infinispan-common_ component
([commit|https://github.com/apache/camel/commit/f0d22792803a221a016092f606fe49c326f23492]),
the artifact _org.apache.camel:camel-infinispan_ doesn't contains anymore the
dependency _org.infinispan:infinispan-core_
maven dependency tree for 3.17.0-SNAPSHOT (starting from
{_}org.apache.camel.springboot:camel-infinispan-starter{_})
{code:bash}
+-
org.apache.camel.springboot:camel-infinispan-starter:jar:3.17.0-SNAPSHOT:compile
| \- org.apache.camel:camel-infinispan:jar:3.17.0-SNAPSHOT:compile
| +- org.apache.camel:camel-infinispan-common:jar:3.17.0-SNAPSHOT:compile
| | +- org.infinispan:infinispan-core:jar:12.1.11.Final:compile
| | | +- org.jgroups:jgroups:jar:4.2.12.Final:compile
| | | +- com.github.ben-manes.caffeine:caffeine:jar:2.9.3:compile
.
{code}
maven dependency tree for 3.18.0 (starting from
{_}org.apache.camel.springboot:camel-infinispan-starter{_})
{code:bash}
+- org.apache.camel.springboot:camel-infinispan-starter:jar:3.18.0:compile
| \- org.apache.camel:camel-infinispan:jar:3.18.0:compile
| +- org.apache.camel:camel-infinispan-common:jar:3.18.0:compile
| | +- org.infinispan:infinispan-commons:jar:13.0.10.Final:compile
| | | +- com.github.ben-manes.caffeine:caffeine:jar:2.9.3:compile
.
{code}
this change causes the
[camel-example-spring-boot-infinispan|https://github.com/apache/camel-spring-boot-examples/tree/main/infinispan]
compilation failure because of the usage of the class
_org.infinispan.configuration.cache.CacheMode_ packaged into _infinispan-core_
dependency
([import|https://github.com/apache/camel-spring-boot-examples/blob/main/infinispan/src/main/java/org/apache/camel/example/springboot/infinispan/Application.java#L31])
> [Camel Spring Boot Examples] Infinispan example cannot be built
> ---
>
> Key: CAMEL-18271
> URL: https://issues.apache.org/jira/browse/CAMEL-18271
> Project: Camel
> Issue Type: Bug
> Components: camel-infinispan, examples
>Affects Versions: 3.18.0
>Reporter: Marco Carletti
>Priority: Major
>
> Since dependency _infinispan-core_ has been replaced with
> _infinispan-commons_ in the _camel-infinispan-common_ component
> ([commit|https://github.com/apache/camel/commit/f0d22792803a221a016092f606fe49c326f23492]),
> the artifact _org.apache.camel:camel-infinispan_ doesn't contain anymore the
> dependency _org.infinispan:infinispan-core_
> maven dependency tree for 3.17.0-SNAPSHOT (starting from
> {_}org.apache.camel.springboot:camel-infinispan-starter{_})
> {code:bash}
> +-
> org.apache.camel.springboot:camel-infinispan-starter:jar:3.17.0-SNAPSHOT:compile
> | \-
[jira] [Created] (CAMEL-18271) [Camel Spring Boot Examples] Infinispan example cannot be built
Marco Carletti created CAMEL-18271:
--
Summary: [Camel Spring Boot Examples] Infinispan example cannot be
built
Key: CAMEL-18271
URL: https://issues.apache.org/jira/browse/CAMEL-18271
Project: Camel
Issue Type: Bug
Components: camel-infinispan, examples
Affects Versions: 3.18.0
Reporter: Marco Carletti
Since dependency _infinispan-core_ has been replaced with _infinispan-commons_
in the _camel-infinispan-common_ component
([commit|https://github.com/apache/camel/commit/f0d22792803a221a016092f606fe49c326f23492]),
the artifact _org.apache.camel:camel-infinispan_ doesn't contains anymore the
dependency _org.infinispan:infinispan-core_
maven dependency tree for 3.17.0-SNAPSHOT (starting from
{_}org.apache.camel.springboot:camel-infinispan-starter{_})
{code:bash}
+-
org.apache.camel.springboot:camel-infinispan-starter:jar:3.17.0-SNAPSHOT:compile
| \- org.apache.camel:camel-infinispan:jar:3.17.0-SNAPSHOT:compile
| +- org.apache.camel:camel-infinispan-common:jar:3.17.0-SNAPSHOT:compile
| | +- org.infinispan:infinispan-core:jar:12.1.11.Final:compile
| | | +- org.jgroups:jgroups:jar:4.2.12.Final:compile
| | | +- com.github.ben-manes.caffeine:caffeine:jar:2.9.3:compile
.
{code}
maven dependency tree for 3.18.0 (starting from
{_}org.apache.camel.springboot:camel-infinispan-starter{_})
{code:bash}
+- org.apache.camel.springboot:camel-infinispan-starter:jar:3.18.0:compile
| \- org.apache.camel:camel-infinispan:jar:3.18.0:compile
| +- org.apache.camel:camel-infinispan-common:jar:3.18.0:compile
| | +- org.infinispan:infinispan-commons:jar:13.0.10.Final:compile
| | | +- com.github.ben-manes.caffeine:caffeine:jar:2.9.3:compile
.
{code}
this change causes the
[camel-example-spring-boot-infinispan|https://github.com/apache/camel-spring-boot-examples/tree/main/infinispan]
compilation failure because of the usage of the class
_org.infinispan.configuration.cache.CacheMode_ packaged into _infinispan-core_
dependency
([import|https://github.com/apache/camel-spring-boot-examples/blob/main/infinispan/src/main/java/org/apache/camel/example/springboot/infinispan/Application.java#L31])
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18270) IMAP skipFailedMessage=true, but route blocked if mail is moved while download
Florian Fiby created CAMEL-18270:
Summary: IMAP skipFailedMessage=true, but route blocked if mail is
moved while download
Key: CAMEL-18270
URL: https://issues.apache.org/jira/browse/CAMEL-18270
Project: Camel
Issue Type: Bug
Components: camel-mail
Affects Versions: 3.18.0
Reporter: Florian Fiby
Our imap mail route on the production system gets blocked when someone or an
other systems moves / deletes an email from the inbox, while the camel mail
route is loading the mail. As we do not have full control on the mailboxes we
enabled skipFailedMessage but the issue remains.
The following exception is written is the log, but the mail consumer is
blocked. The issue can only be resolved by a restart of the service.
{code:java}
2022-07-14 09:17:28.714 WARN 5465 --- [fice365.com:993]
o.a.c.i.engine.DefaultReactiveExecutor : Error executing reactive work due to
Error accessing headers due to: Cannot load header. This exception is ignored.
org.apache.camel.RuntimeCamelException: Error accessing headers due to: Cannot
load header
at
org.apache.camel.component.mail.MailMessage.populateInitialHeaders(MailMessage.java:107)
~[camel-mail-3.18.0.jar:3.18.0]
at
org.apache.camel.support.DefaultMessage.createHeaders(DefaultMessage.java:331)
~[camel-support-3.18.0.jar:3.18.0]
at
org.apache.camel.support.DefaultMessage.hasHeaders(DefaultMessage.java:305)
~[camel-support-3.18.0.jar:3.18.0]
at
org.apache.camel.support.AbstractExchange.copy(AbstractExchange.java:140)
~[camel-support-3.18.0.jar:3.18.0]
at org.apache.camel.support.DefaultExchange.copy(DefaultExchange.java:27)
~[camel-support-3.18.0.jar:3.18.0]
at
org.apache.camel.support.ExchangeHelper.createCopy(ExchangeHelper.java:322)
~[camel-support-3.18.0.jar:3.18.0]
at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.defensiveCopyExchangeIfNeeded(RedeliveryErrorHandler.java:304)
~[camel-core-processor-3.18.0.jar:3.18.0]
at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryTask.prepare(RedeliveryErrorHandler.java:680)
~[camel-core-processor-3.18.0.jar:3.18.0]
at
org.apache.camel.processor.PrototypeTaskFactory.acquire(PrototypeTaskFactory.java:29)
~[camel-core-processor-3.18.0.jar:3.18.0]
at
org.apache.camel.processor.errorhandler.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:210)
~[camel-core-processor-3.18.0.jar:3.18.0]
at
org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:399)
~[camel-base-engine-3.18.0.jar:3.18.0]
at org.apache.camel.processor.Pipeline$PipelineTask.run(Pipeline.java:109)
~[camel-core-processor-3.18.0.jar:3.18.0]
at
org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:189)
~[camel-base-engine-3.18.0.jar:3.18.0]
at
org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:61)
~[camel-base-engine-3.18.0.jar:3.18.0]
at org.apache.camel.processor.Pipeline.process(Pipeline.java:184)
~[camel-core-processor-3.18.0.jar:3.18.0]
at
org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:399)
~[camel-base-engine-3.18.0.jar:3.18.0]
at
org.apache.camel.impl.engine.DefaultAsyncProcessorAwaitManager.process(DefaultAsyncProcessorAwaitManager.java:83)
~[camel-base-engine-3.18.0.jar:3.18.0]
at
org.apache.camel.support.AsyncProcessorSupport.process(AsyncProcessorSupport.java:41)
~[camel-support-3.18.0.jar:3.18.0]
at
org.apache.camel.component.mail.MailConsumer.processExchange(MailConsumer.java:451)
~[camel-mail-3.18.0.jar:3.18.0]
at
org.apache.camel.component.mail.MailConsumer.processBatch(MailConsumer.java:260)
~[camel-mail-3.18.0.jar:3.18.0]
at org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:165)
~[camel-mail-3.18.0.jar:3.18.0]
at
org.apache.camel.support.ScheduledPollConsumer.doRun(ScheduledPollConsumer.java:202)
~[camel-support-3.18.0.jar:3.18.0]
at
org.apache.camel.support.ScheduledPollConsumer.run(ScheduledPollConsumer.java:116)
~[camel-support-3.18.0.jar:3.18.0]
at
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
~[na:na]
at
java.base/java.util.concurrent.FutureTask.runAndReset$$$capture(FutureTask.java:305)
~[na:na]
at java.base/java.util.concurrent.FutureTask.runAndReset(FutureTask.java)
~[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:829) ~[na:na]
Caused by:
