[jira] [Reopened] (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:all-tabpanel
]
rupam reopened CAMEL-18327:
---
Issue is not resolved as at line number 310, isKafkaRunnable method will return
false and at line number 335 safeUnsubscribe method will be called to kill the
Kafka consumer
> 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.1, 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] [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=17574880#comment-17574880
]
rupam commented on CAMEL-18327:
---
Issue is not resolved as at line number 310, isKafkaRunnable method will return
false and at line number 335 safeUnsubscribe method will be called to kill the
Kafka consumer
> 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.1, 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] [Work started] (CAMEL-18275) onCompletion tasks don't get executed in a pipeline with several SEDA queues
[
https://issues.apache.org/jira/browse/CAMEL-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on CAMEL-18275 started by Karen Lease.
---
> onCompletion tasks don't get executed in a pipeline with several SEDA queues
>
>
> Key: CAMEL-18275
> URL: https://issues.apache.org/jira/browse/CAMEL-18275
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
>Reporter: Eduard Gomoliako
>Assignee: Karen Lease
>Priority: Major
> Fix For: 3.19.0
>
>
> I stumbled upon a problem with not working {{onCompletion}} between the
> routes that pass a message over SEDA queues.
> The route configuration is similar to this simplified version:
>
> {code:java}
> from("direct:a")
> .onCompletion().log("a - done").end()
> .to("seda:b");
> from("seda:b")
> .onCompletion().log("b - done").end()
> .to("seda:c");
> from("seda:c")
> .onCompletion().log("c - done").end()
> .to("seda:d");
> from("seda:d")
> .onCompletion().log("d - done").end()
> .to("mock:end"); {code}
>
> With this configuration, I get only {{"d - done"}} logging.
> I debugged the execution and noticed that the {{onCompletion}} handler from
> "a", "b", and "c" don't get executed because they are route-scoped and get
> attempted to be executed in the scope of the next route.
> This happens because they get handed over from the initial exchange to an
> exchange prepared for the next route. It happens in the
> {{SedaProducer::addToQueue}} method with {{{}copy{}}}parameter defined as
> {{{}true{}}}, which makes the {{::prepareCopy}} method being called, which in
> its turn calls {{ExchangeHelper.createCorrelatedCopy}} with {{handover}}
> defined as {{{}true{}}}.
> It seems to me like a bug, because looking at the routes configuration I'd
> expect different behavior: all the {{onCompletion}} tasks get executed
> reporting on routes finalization. Though maybe I'm missing something here,
> and if this is the case then I would appreciate you guys helping me to find
> out the missing details.
> Here is a [unit test reproducing the
> problem|https://gist.github.com/Gems/7555776feae619ac71ed8d9dd9d4d33e].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Reopened] (CAMEL-18275) onCompletion tasks don't get executed in a pipeline with several SEDA queues
[
https://issues.apache.org/jira/browse/CAMEL-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Lease reopened CAMEL-18275:
-
Assignee: Karen Lease
> onCompletion tasks don't get executed in a pipeline with several SEDA queues
>
>
> Key: CAMEL-18275
> URL: https://issues.apache.org/jira/browse/CAMEL-18275
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
>Reporter: Eduard Gomoliako
>Assignee: Karen Lease
>Priority: Major
> Fix For: 3.19.0
>
>
> I stumbled upon a problem with not working {{onCompletion}} between the
> routes that pass a message over SEDA queues.
> The route configuration is similar to this simplified version:
>
> {code:java}
> from("direct:a")
> .onCompletion().log("a - done").end()
> .to("seda:b");
> from("seda:b")
> .onCompletion().log("b - done").end()
> .to("seda:c");
> from("seda:c")
> .onCompletion().log("c - done").end()
> .to("seda:d");
> from("seda:d")
> .onCompletion().log("d - done").end()
> .to("mock:end"); {code}
>
> With this configuration, I get only {{"d - done"}} logging.
> I debugged the execution and noticed that the {{onCompletion}} handler from
> "a", "b", and "c" don't get executed because they are route-scoped and get
> attempted to be executed in the scope of the next route.
> This happens because they get handed over from the initial exchange to an
> exchange prepared for the next route. It happens in the
> {{SedaProducer::addToQueue}} method with {{{}copy{}}}parameter defined as
> {{{}true{}}}, which makes the {{::prepareCopy}} method being called, which in
> its turn calls {{ExchangeHelper.createCorrelatedCopy}} with {{handover}}
> defined as {{{}true{}}}.
> It seems to me like a bug, because looking at the routes configuration I'd
> expect different behavior: all the {{onCompletion}} tasks get executed
> reporting on routes finalization. Though maybe I'm missing something here,
> and if this is the case then I would appreciate you guys helping me to find
> out the missing details.
> Here is a [unit test reproducing the
> problem|https://gist.github.com/Gems/7555776feae619ac71ed8d9dd9d4d33e].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18343) camel-yaml-dsl - Add route-policy
[ https://issues.apache.org/jira/browse/CAMEL-18343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18343. - Resolution: Fixed > camel-yaml-dsl - Add route-policy > - > > Key: CAMEL-18343 > URL: https://issues.apache.org/jira/browse/CAMEL-18343 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Affects Versions: 3.18.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > So you can configure a custom route policy in yaml-dsl -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18343) camel-yaml-dsl - Add route-policy
Claus Ibsen created CAMEL-18343: --- Summary: camel-yaml-dsl - Add route-policy Key: CAMEL-18343 URL: https://issues.apache.org/jira/browse/CAMEL-18343 Project: Camel Issue Type: Improvement Components: camel-yaml-dsl Affects Versions: 3.18.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.18.1, 3.19.0 So you can configure a custom route policy in yaml-dsl -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18275) onCompletion tasks don't get executed in a pipeline with several SEDA queues
[
https://issues.apache.org/jira/browse/CAMEL-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Lease resolved CAMEL-18275.
-
Resolution: Fixed
> onCompletion tasks don't get executed in a pipeline with several SEDA queues
>
>
> Key: CAMEL-18275
> URL: https://issues.apache.org/jira/browse/CAMEL-18275
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
>Reporter: Eduard Gomoliako
>Priority: Major
> Fix For: 3.19.0
>
>
> I stumbled upon a problem with not working {{onCompletion}} between the
> routes that pass a message over SEDA queues.
> The route configuration is similar to this simplified version:
>
> {code:java}
> from("direct:a")
> .onCompletion().log("a - done").end()
> .to("seda:b");
> from("seda:b")
> .onCompletion().log("b - done").end()
> .to("seda:c");
> from("seda:c")
> .onCompletion().log("c - done").end()
> .to("seda:d");
> from("seda:d")
> .onCompletion().log("d - done").end()
> .to("mock:end"); {code}
>
> With this configuration, I get only {{"d - done"}} logging.
> I debugged the execution and noticed that the {{onCompletion}} handler from
> "a", "b", and "c" don't get executed because they are route-scoped and get
> attempted to be executed in the scope of the next route.
> This happens because they get handed over from the initial exchange to an
> exchange prepared for the next route. It happens in the
> {{SedaProducer::addToQueue}} method with {{{}copy{}}}parameter defined as
> {{{}true{}}}, which makes the {{::prepareCopy}} method being called, which in
> its turn calls {{ExchangeHelper.createCorrelatedCopy}} with {{handover}}
> defined as {{{}true{}}}.
> It seems to me like a bug, because looking at the routes configuration I'd
> expect different behavior: all the {{onCompletion}} tasks get executed
> reporting on routes finalization. Though maybe I'm missing something here,
> and if this is the case then I would appreciate you guys helping me to find
> out the missing details.
> Here is a [unit test reproducing the
> problem|https://gist.github.com/Gems/7555776feae619ac71ed8d9dd9d4d33e].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18275) onCompletion tasks don't get executed in a pipeline with several SEDA queues
[
https://issues.apache.org/jira/browse/CAMEL-18275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karen Lease updated CAMEL-18275:
Fix Version/s: 3.19.0
> onCompletion tasks don't get executed in a pipeline with several SEDA queues
>
>
> Key: CAMEL-18275
> URL: https://issues.apache.org/jira/browse/CAMEL-18275
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.18.0
>Reporter: Eduard Gomoliako
>Priority: Major
> Fix For: 3.19.0
>
>
> I stumbled upon a problem with not working {{onCompletion}} between the
> routes that pass a message over SEDA queues.
> The route configuration is similar to this simplified version:
>
> {code:java}
> from("direct:a")
> .onCompletion().log("a - done").end()
> .to("seda:b");
> from("seda:b")
> .onCompletion().log("b - done").end()
> .to("seda:c");
> from("seda:c")
> .onCompletion().log("c - done").end()
> .to("seda:d");
> from("seda:d")
> .onCompletion().log("d - done").end()
> .to("mock:end"); {code}
>
> With this configuration, I get only {{"d - done"}} logging.
> I debugged the execution and noticed that the {{onCompletion}} handler from
> "a", "b", and "c" don't get executed because they are route-scoped and get
> attempted to be executed in the scope of the next route.
> This happens because they get handed over from the initial exchange to an
> exchange prepared for the next route. It happens in the
> {{SedaProducer::addToQueue}} method with {{{}copy{}}}parameter defined as
> {{{}true{}}}, which makes the {{::prepareCopy}} method being called, which in
> its turn calls {{ExchangeHelper.createCorrelatedCopy}} with {{handover}}
> defined as {{{}true{}}}.
> It seems to me like a bug, because looking at the routes configuration I'd
> expect different behavior: all the {{onCompletion}} tasks get executed
> reporting on routes finalization. Though maybe I'm missing something here,
> and if this is the case then I would appreciate you guys helping me to find
> out the missing details.
> Here is a [unit test reproducing the
> problem|https://gist.github.com/Gems/7555776feae619ac71ed8d9dd9d4d33e].
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Work started] (CAMEL-18341) Upgrade from Codehaus Groovy 3.0.12 to Apache Groovy 4.x
[ https://issues.apache.org/jira/browse/CAMEL-18341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on CAMEL-18341 started by Aurélien Pupier. --- > Upgrade from Codehaus Groovy 3.0.12 to Apache Groovy 4.x > > > Key: CAMEL-18341 > URL: https://issues.apache.org/jira/browse/CAMEL-18341 > Project: Camel > Issue Type: Dependency upgrade >Affects Versions: 3.18.0 >Reporter: Aurélien Pupier >Assignee: Aurélien Pupier >Priority: Major > > Groovy 4.0.0 has been released at the beginning of 2022. it might be nice to > move to the latest version. > There is a long list of features and bug fixes > [http://groovy-lang.org/changelogs/changelog-4.0.0.html] > Maybe worth noticing it contains several fixes related to Java 17: > * [GROOVY-10391] - Default interface methods causing problems with java 17 > and groovy 3.0.9 > * [GROOVY-10405] - @AutoClone breaks in Java17 for File properties > * [GROOVY-10429] - StringBuilder misses setLength method in Java17 > Based on [https://groovy.apache.org/versioning.html] 3.x will have oen or two > bugfixxes release (in fact already 3 happened). So good chances that there > will be only security release of 3.x soon. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18342) camel-core-model - DSL for calling endpoint and set response to header
Claus Ibsen created CAMEL-18342: --- Summary: camel-core-model - DSL for calling endpoint and set response to header Key: CAMEL-18342 URL: https://issues.apache.org/jira/browse/CAMEL-18342 Project: Camel Issue Type: New Feature Components: camel-core Reporter: Claus Ibsen Fix For: 3.x Either we add a special language for calling and endpoint, so you can use DSL today And the dynamic variant And we may need for exchange properties as well (that would mean 4 new EIPs in the model). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (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:all-tabpanel
]
Claus Ibsen resolved CAMEL-18327.
-
Resolution: Fixed
> 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.1, 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] [Updated] (CAMEL-18296) camel-example tag is using snapshot camel version
[ https://issues.apache.org/jira/browse/CAMEL-18296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18296: Fix Version/s: 3.18.2 (was: 3.18.1) > camel-example tag is using snapshot camel version > - > > Key: CAMEL-18296 > URL: https://issues.apache.org/jira/browse/CAMEL-18296 > Project: Camel > Issue Type: Task > Components: examples >Affects Versions: 3.18.0 >Reporter: Aurélien Pupier >Priority: Minor > Fix For: 3.19.0, 3.18.2 > > > see > https://github.com/apache/camel-examples/blob/27d60cbd1f113036df48daffd7edea8375a954aa/examples/pom.xml#L170 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-17947) camel-kafka: fix concurrent access in camel-health
[
https://issues.apache.org/jira/browse/CAMEL-17947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-17947.
-
Resolution: Fixed
> camel-kafka: fix concurrent access in camel-health
> --
>
> Key: CAMEL-17947
> URL: https://issues.apache.org/jira/browse/CAMEL-17947
> Project: Camel
> Issue Type: Task
> Components: camel-health, camel-kafka
>Affects Versions: 3.17.0
>Reporter: Otavio Rodolfo Piske
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
>
> Investigate and fix the issue below:
> {code}
> 1496 │ java.util.ConcurrentModificationException: KafkaConsumer is not safe
> for multi-threaded access
> 1497 │ at
> org.apache.kafka.clients.consumer.KafkaConsumer.acquire(KafkaConsumer.java:2469)
> ~[kafka-clients-3.1.0.jar:?]
> 1498 │ at
> org.apache.kafka.clients.consumer.KafkaConsumer.acquireAndEnsureOpen(KafkaConsumer.java:2453)
> ~[kafka-clients-3.1.0.jar:?]
> 1499 │ at
> org.apache.kafka.clients.consumer.KafkaConsumer.assignment(KafkaConsumer.java:891)
> ~[kafka-clients-3.1.0.jar:?]
> 1500 │ at
> org.apache.camel.component.kafka.KafkaFetchRecords.pause(KafkaFetchRecords.java:518)
> ~[camel-kafka-3.17.0-SNAPSHOT.jar:3.17.0-SNAPSHOT]
> 1501 │ at
> org.apache.camel.component.kafka.KafkaConsumer.doSuspend(KafkaConsumer.java:221)
> ~[camel-kafka-3.17.0-SNAPSHOT.jar:3.17.0-SNAPSHOT]
> 1502 │ at
> org.apache.camel.support.service.BaseService.suspend(BaseService.java:189)
> ~[camel-api-3.17.0-SNAPSHOT.jar:3.17.0-SNAPSHOT]
> 1503 │ at
> org.apache.camel.support.service.ServiceHelper.suspendService(ServiceHelper.java:404)
> ~[camel-api-3.17.0-SNAPSHOT.jar:3.17.0-SNAPSHOT]
> 1504 │ at
> org.apache.camel.impl.engine.DefaultShutdownStrategy.suspendNow(DefaultShutdownStrategy.java:447)
> ~[camel-base-engine-3.17.0-SNAPSHOT.jar:3.17.0-SNAPSHOT]
> 1505 │ at
> org.apache.camel.impl.engine.DefaultShutdownStrategy$ShutdownTask.run(DefaultShutdownStrategy.java:620)
> ~[camel-base-engine-3.17.0-SNAPSHOT.jar:3.17.0-SNAPSHOT]
> 1506 │ at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
> 1507 │ at java.util.concurrent.FutureTask.run(FutureTask.java:264)
> ~[?:?]
> 1508 │ at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
> ~[?:?]
> 1509 │ at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
> ~[?:?]
> 1510 │ at java.lang.Thread.run(Thread.java:833) ~[?:?]
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18338) IMAP MailConsumer NullPointerException due CAMEL-16180
[
https://issues.apache.org/jira/browse/CAMEL-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18338.
-
Resolution: Fixed
Thanks for reporting
> IMAP MailConsumer NullPointerException due CAMEL-16180
> --
>
> Key: CAMEL-18338
> URL: https://issues.apache.org/jira/browse/CAMEL-18338
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 3.18.0
>Reporter: Florian Fiby
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
>
> {{{}2022-08-03 02:57:31.059 WARN 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.camel.component.mail.MailConsumer :
> Error opening mail fol{}}}{{{}der due to GSI5 BAD User is authenticated but
> not connected.. Will re-create connection on next poll{}}}
> This leads to disconnect(). disconnect sets folder to null, which leads to
> NullPointerExceptions afterwards:
> {{2022-08-03 02:57:31.073 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.e.DefaultErrorHandler :
> Failed delivery for (MessageId: 61974526595AC2A-0006 on
> ExchangeId: 61974526595AC2A-0006). Exhausted after delivery
> attempt: 0 caught: null}}
> {{{}Message History (source location and message history is
> disabled){}}}{{{}---{}}}{{{}Source
> ID Processor
> Elapsed (ms){}}}{{
> Custom:XXX.
> from[imaps://outlook.office365.com:993?bridgeError 3}}{{
> ...}}{{ Escalation Route/setHeader1
> setHeader[EscalationSender] 0}}
> {{{}Stacktrace{}}}{{{}---{}}}
> {{java.lang.NullPointerException: null}}{{ at
> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:162)
> ~[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(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:829)
> ~[na:na]}}
> {{2022-08-03 02:57:31.074 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.FatalFallbackErrorHandler :
> Exception occurred while trying to handle previously thrown exception on
> exchangeId: 61974526595AC2A-0006 using: [null].}}
>
> {{2022-08-03 02:57:31.081 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.e.DefaultErrorHandler :
> Failed delivery for (MessageId: 61974526595AC2A-0007 on
> ExchangeId: 61974526595AC2A-0007). Exhausted after delivery
> attempt: 1 caught: java.lang.NullPointerException. Processed by failure
> processor: FatalFallbackErrorHandler[null]}}
> {{{}Message History (source location and message history is
> disabled){}}}{{{}---{}}}{{{}Source
> ID Processor
> Elapsed (ms){}}}{{
> Custom:TTITSupport@forstinger.
> from[imaps://outlook.office365.com:993?bridgeError 3}}
> {{{}Stacktrace{}}}{{{}---{}}}
> {{java.lang.NullPointerException: null}}{{ at
>
[jira] [Assigned] (CAMEL-18338) IMAP MailConsumer NullPointerException due CAMEL-16180
[
https://issues.apache.org/jira/browse/CAMEL-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-18338:
---
Assignee: Claus Ibsen
> IMAP MailConsumer NullPointerException due CAMEL-16180
> --
>
> Key: CAMEL-18338
> URL: https://issues.apache.org/jira/browse/CAMEL-18338
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 3.18.0
>Reporter: Florian Fiby
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
>
> {{{}2022-08-03 02:57:31.059 WARN 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.camel.component.mail.MailConsumer :
> Error opening mail fol{}}}{{{}der due to GSI5 BAD User is authenticated but
> not connected.. Will re-create connection on next poll{}}}
> This leads to disconnect(). disconnect sets folder to null, which leads to
> NullPointerExceptions afterwards:
> {{2022-08-03 02:57:31.073 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.e.DefaultErrorHandler :
> Failed delivery for (MessageId: 61974526595AC2A-0006 on
> ExchangeId: 61974526595AC2A-0006). Exhausted after delivery
> attempt: 0 caught: null}}
> {{{}Message History (source location and message history is
> disabled){}}}{{{}---{}}}{{{}Source
> ID Processor
> Elapsed (ms){}}}{{
> Custom:XXX.
> from[imaps://outlook.office365.com:993?bridgeError 3}}{{
> ...}}{{ Escalation Route/setHeader1
> setHeader[EscalationSender] 0}}
> {{{}Stacktrace{}}}{{{}---{}}}
> {{java.lang.NullPointerException: null}}{{ at
> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:162)
> ~[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(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:829)
> ~[na:na]}}
> {{2022-08-03 02:57:31.074 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.FatalFallbackErrorHandler :
> Exception occurred while trying to handle previously thrown exception on
> exchangeId: 61974526595AC2A-0006 using: [null].}}
>
> {{2022-08-03 02:57:31.081 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.e.DefaultErrorHandler :
> Failed delivery for (MessageId: 61974526595AC2A-0007 on
> ExchangeId: 61974526595AC2A-0007). Exhausted after delivery
> attempt: 1 caught: java.lang.NullPointerException. Processed by failure
> processor: FatalFallbackErrorHandler[null]}}
> {{{}Message History (source location and message history is
> disabled){}}}{{{}---{}}}{{{}Source
> ID Processor
> Elapsed (ms){}}}{{
> Custom:TTITSupport@forstinger.
> from[imaps://outlook.office365.com:993?bridgeError 3}}
> {{{}Stacktrace{}}}{{{}---{}}}
> {{java.lang.NullPointerException: null}}{{ at
>
[jira] [Updated] (CAMEL-18341) Upgrade from Codehaus Groovy 3.0.12 to Apache Groovy 4.x
[ https://issues.apache.org/jira/browse/CAMEL-18341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aurélien Pupier updated CAMEL-18341: Summary: Upgrade from Codehaus Groovy 3.0.12 to Apache Groovy 4.x (was: Upgrade groovy to 4.x) > Upgrade from Codehaus Groovy 3.0.12 to Apache Groovy 4.x > > > Key: CAMEL-18341 > URL: https://issues.apache.org/jira/browse/CAMEL-18341 > Project: Camel > Issue Type: Dependency upgrade >Affects Versions: 3.18.0 >Reporter: Aurélien Pupier >Assignee: Aurélien Pupier >Priority: Major > > Groovy 4.0.0 has been released at the beginning of 2022. it might be nice to > move to the latest version. > There is a long list of features and bug fixes > [http://groovy-lang.org/changelogs/changelog-4.0.0.html] > Maybe worth noticing it contains several fixes related to Java 17: > * [GROOVY-10391] - Default interface methods causing problems with java 17 > and groovy 3.0.9 > * [GROOVY-10405] - @AutoClone breaks in Java17 for File properties > * [GROOVY-10429] - StringBuilder misses setLength method in Java17 > Based on [https://groovy.apache.org/versioning.html] 3.x will have oen or two > bugfixxes release (in fact already 3 happened). So good chances that there > will be only security release of 3.x soon. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-18341) Upgrade groovy to 4.x
[ https://issues.apache.org/jira/browse/CAMEL-18341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aurélien Pupier reassigned CAMEL-18341: --- Assignee: Aurélien Pupier > Upgrade groovy to 4.x > - > > Key: CAMEL-18341 > URL: https://issues.apache.org/jira/browse/CAMEL-18341 > Project: Camel > Issue Type: Dependency upgrade >Affects Versions: 3.18.0 >Reporter: Aurélien Pupier >Assignee: Aurélien Pupier >Priority: Major > > Groovy 4.0.0 has been released at the beginning of 2022. it might be nice to > move to the latest version. > There is a long list of features and bug fixes > [http://groovy-lang.org/changelogs/changelog-4.0.0.html] > Maybe worth noticing it contains several fixes related to Java 17: > * [GROOVY-10391] - Default interface methods causing problems with java 17 > and groovy 3.0.9 > * [GROOVY-10405] - @AutoClone breaks in Java17 for File properties > * [GROOVY-10429] - StringBuilder misses setLength method in Java17 > Based on [https://groovy.apache.org/versioning.html] 3.x will have oen or two > bugfixxes release (in fact already 3 happened). So good chances that there > will be only security release of 3.x soon. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18341) Upgrade groovy to 4.x
[ https://issues.apache.org/jira/browse/CAMEL-18341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574646#comment-17574646 ] Claus Ibsen commented on CAMEL-18341: - spring boot / quarkus / needs to be upgraded to groovy 4.x as well. > Upgrade groovy to 4.x > - > > Key: CAMEL-18341 > URL: https://issues.apache.org/jira/browse/CAMEL-18341 > Project: Camel > Issue Type: Dependency upgrade >Affects Versions: 3.18.0 >Reporter: Aurélien Pupier >Priority: Major > > Groovy 4.0.0 has been released at the beginning of 2022. it might be nice to > move to the latest version. > There is a long list of features and bug fixes > [http://groovy-lang.org/changelogs/changelog-4.0.0.html] > Maybe worth noticing it contains several fixes related to Java 17: > * [GROOVY-10391] - Default interface methods causing problems with java 17 > and groovy 3.0.9 > * [GROOVY-10405] - @AutoClone breaks in Java17 for File properties > * [GROOVY-10429] - StringBuilder misses setLength method in Java17 > Based on [https://groovy.apache.org/versioning.html] 3.x will have oen or two > bugfixxes release (in fact already 3 happened). So good chances that there > will be only security release of 3.x soon. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18341) Upgrade groovy to 4.x
[ https://issues.apache.org/jira/browse/CAMEL-18341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18341: Issue Type: Dependency upgrade (was: Task) > Upgrade groovy to 4.x > - > > Key: CAMEL-18341 > URL: https://issues.apache.org/jira/browse/CAMEL-18341 > Project: Camel > Issue Type: Dependency upgrade >Affects Versions: 3.18.0 >Reporter: Aurélien Pupier >Priority: Major > > Groovy 4.0.0 has been released at the beginning of 2022. it might be nice to > move to the latest version. > There is a long list of features and bug fixes > [http://groovy-lang.org/changelogs/changelog-4.0.0.html] > Maybe worth noticing it contains several fixes related to Java 17: > * [GROOVY-10391] - Default interface methods causing problems with java 17 > and groovy 3.0.9 > * [GROOVY-10405] - @AutoClone breaks in Java17 for File properties > * [GROOVY-10429] - StringBuilder misses setLength method in Java17 > Based on [https://groovy.apache.org/versioning.html] 3.x will have oen or two > bugfixxes release (in fact already 3 happened). So good chances that there > will be only security release of 3.x soon. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18339) camel-joor - Java DSL - Allow compiled classes to be loadable from anywhere in Camel
[ https://issues.apache.org/jira/browse/CAMEL-18339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18339. - Assignee: Claus Ibsen Resolution: Fixed > camel-joor - Java DSL - Allow compiled classes to be loadable from anywhere > in Camel > > > Key: CAMEL-18339 > URL: https://issues.apache.org/jira/browse/CAMEL-18339 > Project: Camel > Issue Type: Improvement > Components: camel-joor >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > See CAMEL-18336 > We can maybe for custom classes (not routes) let them be loadable via a > special classloader that we then share on CamelContext and its class > resolver, so that it can load these classes. > Otherwise you need to use BindToRegistry to share the class via bean ids. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18341) Upgrade groovy to 4.x
Aurélien Pupier created CAMEL-18341: --- Summary: Upgrade groovy to 4.x Key: CAMEL-18341 URL: https://issues.apache.org/jira/browse/CAMEL-18341 Project: Camel Issue Type: Task Affects Versions: 3.18.0 Reporter: Aurélien Pupier Groovy 4.0.0 has been released at the beginning of 2022. it might be nice to move to the latest version. There is a long list of features and bug fixes [http://groovy-lang.org/changelogs/changelog-4.0.0.html] Maybe worth noticing it contains several fixes related to Java 17: * [GROOVY-10391] - Default interface methods causing problems with java 17 and groovy 3.0.9 * [GROOVY-10405] - @AutoClone breaks in Java17 for File properties * [GROOVY-10429] - StringBuilder misses setLength method in Java17 Based on [https://groovy.apache.org/versioning.html] 3.x will have oen or two bugfixxes release (in fact already 3 happened). So good chances that there will be only security release of 3.x soon. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18336) camel-jbang: YAML DSL cannot find classes for local beans
[
https://issues.apache.org/jira/browse/CAMEL-18336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574636#comment-17574636
]
Claus Ibsen commented on CAMEL-18336:
-
I found a way to improve camel joor (java dsl) to make classloading available
outside as well, so your example runs OOTB in next releases
https://issues.apache.org/jira/browse/CAMEL-18339
> camel-jbang: YAML DSL cannot find classes for local beans
> -
>
> Key: CAMEL-18336
> URL: https://issues.apache.org/jira/browse/CAMEL-18336
> Project: Camel
> Issue Type: Bug
> Components: camel-jbang
>Affects Versions: 3.18.0
> Environment: Camel 3.18, Java 11.
>Reporter: Darren Coleman
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.18.1, 3.19.0
>
> Attachments: camel-jbang-yaml-bean.tgz
>
>
> When running a YAML route using camel-jbang, it fails to find the class for a
> Java bean in the same directory. However, the equivalent route written in
> Java DSL runs the route without errors.
> The attached tarball contains a simple bean and equivalent routes in Java and
> YAML.
> To see the failures, run the YAML route:
> {code:bash}
> $ camel run HelloBean.java hello.yaml
> java.lang.RuntimeException: java.lang.ClassNotFoundException: HelloBean
> at
> org.apache.camel.dsl.yaml.deserializers.BeansDeserializer$1.configure(BeansDeserializer.java:67)
> at
> org.apache.camel.dsl.yaml.common.YamlSupport$1.configure(YamlSupport.java:121)
> at
> org.apache.camel.dsl.yaml.YamlRoutesBuilderLoader$1.doConfigure(YamlRoutesBuilderLoader.java:166)
> at
> org.apache.camel.dsl.yaml.YamlRoutesBuilderLoader$1.configure(YamlRoutesBuilderLoader.java:140)
> at
> org.apache.camel.builder.RouteBuilder.checkInitialized(RouteBuilder.java:672)
> at
> org.apache.camel.builder.RouteBuilder.configureRoutes(RouteBuilder.java:618)
> at
> org.apache.camel.builder.RouteBuilder.addRoutesToCamelContext(RouteBuilder.java:554)
> at
> org.apache.camel.impl.engine.AbstractCamelContext.addRoutes(AbstractCamelContext.java:1178)
> at
> org.apache.camel.main.RoutesConfigurer.addDiscoveredRoutes(RoutesConfigurer.java:237)
> at
> org.apache.camel.main.RoutesConfigurer.configureRoutes(RoutesConfigurer.java:212)
> at
> org.apache.camel.main.BaseMainSupport.configureRoutes(BaseMainSupport.java:582)
> at
> org.apache.camel.main.BaseMainSupport.postProcessCamelContext(BaseMainSupport.java:637)
> at
> org.apache.camel.main.MainSupport.initCamelContext(MainSupport.java:403)
> at org.apache.camel.main.KameletMain.doInit(KameletMain.java:227)
> at
> org.apache.camel.support.service.BaseService.init(BaseService.java:83)
> at
> org.apache.camel.support.service.BaseService.start(BaseService.java:111)
> at org.apache.camel.dsl.jbang.core.commands.Run.run(Run.java:560)
> at org.apache.camel.dsl.jbang.core.commands.Run.call(Run.java:199)
> at org.apache.camel.dsl.jbang.core.commands.Run.call(Run.java:72)
> at picocli.CommandLine.executeUserObject(CommandLine.java:1953)
> at picocli.CommandLine.access$1300(CommandLine.java:145)
> at
> picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2358)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2352)
> at picocli.CommandLine$RunLast.handle(CommandLine.java:2314)
> at
> picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2179)
> at picocli.CommandLine$RunLast.execute(CommandLine.java:2316)
> at picocli.CommandLine.execute(CommandLine.java:2078)
> at
> org.apache.camel.dsl.jbang.core.commands.CamelJBangMain.run(CamelJBangMain.java:51)
> at main.CamelJBang.main(CamelJBang.java:37)
> Caused by: java.lang.ClassNotFoundException: HelloBean
> at
> org.apache.camel.impl.engine.DefaultClassResolver.resolveMandatoryClass(DefaultClassResolver.java:87)
> at
> org.apache.camel.support.PropertyBindingSupport.resolveBean(PropertyBindingSupport.java:1519)
> at
> org.apache.camel.dsl.yaml.deserializers.NamedBeanDefinition.newInstance(NamedBeanDefinition.java:64)
> at
> org.apache.camel.dsl.yaml.deserializers.BeansDeserializer$1.configure(BeansDeserializer.java:65)
> ... 28 more
> {code}
> However, the Java route runs without errors:
> {code:bash}
> $ camel run HelloBean.java HelloRoute.javaJ
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-16367) Investigate impact of BinTray/JCenter shutdown
[ https://issues.apache.org/jira/browse/CAMEL-16367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aurélien Pupier resolved CAMEL-16367. - Resolution: Fixed Groovy has been modifyign defaults to avoid the problem in latest 3.0.x version > Investigate impact of BinTray/JCenter shutdown > -- > > Key: CAMEL-16367 > URL: https://issues.apache.org/jira/browse/CAMEL-16367 > Project: Camel > Issue Type: Task > Components: tooling >Affects Versions: 3.8.0 >Reporter: Aurélien Pupier >Priority: Major > > on 1st May 2021, the Bintray/Jcenter service will be shutdown. > I think it will affected through depdency chain Camel Catalog -> Grape -> Ivy > dependencies > Ivy is providing bintray resolver. I think it is set by default. > https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/ > I reported https://issues.apache.org/jira/browse/IVY-1626 a month ago but got > no answer. > Either: > - integrate a version with a fix defaults when available (grape -> groovy) > - provide a config to override the defaults -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18339) camel-joor - Java DSL - Allow compiled classes to be loadable from anywhere in Camel
[ https://issues.apache.org/jira/browse/CAMEL-18339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18339: Fix Version/s: 3.18.1 3.19.0 (was: 3.x) > camel-joor - Java DSL - Allow compiled classes to be loadable from anywhere > in Camel > > > Key: CAMEL-18339 > URL: https://issues.apache.org/jira/browse/CAMEL-18339 > Project: Camel > Issue Type: Improvement > Components: camel-joor >Reporter: Claus Ibsen >Priority: Major > Fix For: 3.18.1, 3.19.0 > > > See CAMEL-18336 > We can maybe for custom classes (not routes) let them be loadable via a > special classloader that we then share on CamelContext and its class > resolver, so that it can load these classes. > Otherwise you need to use BindToRegistry to share the class via bean ids. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18340) implement camel-sapjcoserver component
[ https://issues.apache.org/jira/browse/CAMEL-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Cosentino resolved CAMEL-18340. -- Resolution: Won't Fix > implement camel-sapjcoserver component > --- > > Key: CAMEL-18340 > URL: https://issues.apache.org/jira/browse/CAMEL-18340 > Project: Camel > Issue Type: New Feature >Reporter: WangYan >Priority: Minor > > Hello Camel Riders > I am using many integrations between SAP ABAP <->Camel/JAVA during my daily > work > Therefore I want to implement camel-sapjcoserver component (consumer only) > which can recieve SAP ABAP calls result and wrap it as exchange for next step -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18340) implement camel-sapjcoserver component
[ https://issues.apache.org/jira/browse/CAMEL-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574577#comment-17574577 ] Andrea Cosentino commented on CAMEL-18340: -- It's not possible to add a component based on SAP libraries, they are not compatible with ASF license. The examples are different because we are not releasing them, so we could eventually add a provided dependency, but for released artifacts we cannot do it. So this cannot be done or assigned. If you want to work on 3rd party component with particular licenses you need to look at camel-extras https://github.com/camel-extra/camel-extra > implement camel-sapjcoserver component > --- > > Key: CAMEL-18340 > URL: https://issues.apache.org/jira/browse/CAMEL-18340 > Project: Camel > Issue Type: New Feature >Reporter: WangYan >Priority: Minor > > Hello Camel Riders > I am using many integrations between SAP ABAP <->Camel/JAVA during my daily > work > Therefore I want to implement camel-sapjcoserver component (consumer only) > which can recieve SAP ABAP calls result and wrap it as exchange for next step -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18338) IMAP MailConsumer NullPointerException due CAMEL-16180
[
https://issues.apache.org/jira/browse/CAMEL-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574575#comment-17574575
]
Florian Fiby commented on CAMEL-18338:
--
No, I'm not having enough knowledge about the camel architecture
> IMAP MailConsumer NullPointerException due CAMEL-16180
> --
>
> Key: CAMEL-18338
> URL: https://issues.apache.org/jira/browse/CAMEL-18338
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 3.18.0
>Reporter: Florian Fiby
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
>
> {{{}2022-08-03 02:57:31.059 WARN 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.camel.component.mail.MailConsumer :
> Error opening mail fol{}}}{{{}der due to GSI5 BAD User is authenticated but
> not connected.. Will re-create connection on next poll{}}}
> This leads to disconnect(). disconnect sets folder to null, which leads to
> NullPointerExceptions afterwards:
> {{2022-08-03 02:57:31.073 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.e.DefaultErrorHandler :
> Failed delivery for (MessageId: 61974526595AC2A-0006 on
> ExchangeId: 61974526595AC2A-0006). Exhausted after delivery
> attempt: 0 caught: null}}
> {{{}Message History (source location and message history is
> disabled){}}}{{{}---{}}}{{{}Source
> ID Processor
> Elapsed (ms){}}}{{
> Custom:XXX.
> from[imaps://outlook.office365.com:993?bridgeError 3}}{{
> ...}}{{ Escalation Route/setHeader1
> setHeader[EscalationSender] 0}}
> {{{}Stacktrace{}}}{{{}---{}}}
> {{java.lang.NullPointerException: null}}{{ at
> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:162)
> ~[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(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:829)
> ~[na:na]}}
> {{2022-08-03 02:57:31.074 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.FatalFallbackErrorHandler :
> Exception occurred while trying to handle previously thrown exception on
> exchangeId: 61974526595AC2A-0006 using: [null].}}
>
> {{2022-08-03 02:57:31.081 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.e.DefaultErrorHandler :
> Failed delivery for (MessageId: 61974526595AC2A-0007 on
> ExchangeId: 61974526595AC2A-0007). Exhausted after delivery
> attempt: 1 caught: java.lang.NullPointerException. Processed by failure
> processor: FatalFallbackErrorHandler[null]}}
> {{{}Message History (source location and message history is
> disabled){}}}{{{}---{}}}{{{}Source
> ID Processor
> Elapsed (ms){}}}{{
> Custom:TTITSupport@forstinger.
> from[imaps://outlook.office365.com:993?bridgeError 3}}
> {{{}Stacktrace{}}}{{{}---{}}}
> {{java.lang.NullPointerException:
[jira] [Resolved] (CAMEL-18337) [camel-hyperledger-aries] Add support for /issue-credential/send-proposal
[ https://issues.apache.org/jira/browse/CAMEL-18337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Diesler resolved CAMEL-18337. Resolution: Fixed Done > [camel-hyperledger-aries] Add support for /issue-credential/send-proposal > - > > Key: CAMEL-18337 > URL: https://issues.apache.org/jira/browse/CAMEL-18337 > Project: Camel > Issue Type: Improvement >Reporter: Thomas Diesler >Assignee: Thomas Diesler >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18340) implement camel-sapjcoserver component
[ https://issues.apache.org/jira/browse/CAMEL-18340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574564#comment-17574564 ] WangYan commented on CAMEL-18340: - Please assign the task to me, it seems i am not able to do that by myself :) > implement camel-sapjcoserver component > --- > > Key: CAMEL-18340 > URL: https://issues.apache.org/jira/browse/CAMEL-18340 > Project: Camel > Issue Type: New Feature >Reporter: WangYan >Priority: Minor > > Hello Camel Riders > I am using many integrations between SAP ABAP <->Camel/JAVA during my daily > work > Therefore I want to implement camel-sapjcoserver component (consumer only) > which can recieve SAP ABAP calls result and wrap it as exchange for next step -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18340) implement camel-sapjcoserver component
WangYan created CAMEL-18340: --- Summary: implement camel-sapjcoserver component Key: CAMEL-18340 URL: https://issues.apache.org/jira/browse/CAMEL-18340 Project: Camel Issue Type: New Feature Reporter: WangYan Hello Camel Riders I am using many integrations between SAP ABAP <->Camel/JAVA during my daily work Therefore I want to implement camel-sapjcoserver component (consumer only) which can recieve SAP ABAP calls result and wrap it as exchange for next step -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18338) IMAP MailConsumer NullPointerException due CAMEL-16180
[
https://issues.apache.org/jira/browse/CAMEL-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574536#comment-17574536
]
Claus Ibsen commented on CAMEL-18338:
-
Are you working on a fix as a PR ?
> IMAP MailConsumer NullPointerException due CAMEL-16180
> --
>
> Key: CAMEL-18338
> URL: https://issues.apache.org/jira/browse/CAMEL-18338
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 3.18.0
>Reporter: Florian Fiby
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
>
> {{{}2022-08-03 02:57:31.059 WARN 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.camel.component.mail.MailConsumer :
> Error opening mail fol{}}}{{{}der due to GSI5 BAD User is authenticated but
> not connected.. Will re-create connection on next poll{}}}
> This leads to disconnect(). disconnect sets folder to null, which leads to
> NullPointerExceptions afterwards:
> {{2022-08-03 02:57:31.073 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.e.DefaultErrorHandler :
> Failed delivery for (MessageId: 61974526595AC2A-0006 on
> ExchangeId: 61974526595AC2A-0006). Exhausted after delivery
> attempt: 0 caught: null}}
> {{{}Message History (source location and message history is
> disabled){}}}{{{}---{}}}{{{}Source
> ID Processor
> Elapsed (ms){}}}{{
> Custom:XXX.
> from[imaps://outlook.office365.com:993?bridgeError 3}}{{
> ...}}{{ Escalation Route/setHeader1
> setHeader[EscalationSender] 0}}
> {{{}Stacktrace{}}}{{{}---{}}}
> {{java.lang.NullPointerException: null}}{{ at
> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:162)
> ~[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(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:829)
> ~[na:na]}}
> {{2022-08-03 02:57:31.074 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.FatalFallbackErrorHandler :
> Exception occurred while trying to handle previously thrown exception on
> exchangeId: 61974526595AC2A-0006 using: [null].}}
>
> {{2022-08-03 02:57:31.081 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.e.DefaultErrorHandler :
> Failed delivery for (MessageId: 61974526595AC2A-0007 on
> ExchangeId: 61974526595AC2A-0007). Exhausted after delivery
> attempt: 1 caught: java.lang.NullPointerException. Processed by failure
> processor: FatalFallbackErrorHandler[null]}}
> {{{}Message History (source location and message history is
> disabled){}}}{{{}---{}}}{{{}Source
> ID Processor
> Elapsed (ms){}}}{{
> Custom:TTITSupport@forstinger.
> from[imaps://outlook.office365.com:993?bridgeError 3}}
> {{{}Stacktrace{}}}{{{}---{}}}
> {{java.lang.NullPointerException: null}}{{ at
>
[jira] [Updated] (CAMEL-18338) IMAP MailConsumer NullPointerException due CAMEL-16180
[
https://issues.apache.org/jira/browse/CAMEL-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18338:
Fix Version/s: 3.18.1
3.19.0
> IMAP MailConsumer NullPointerException due CAMEL-16180
> --
>
> Key: CAMEL-18338
> URL: https://issues.apache.org/jira/browse/CAMEL-18338
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 3.18.0
>Reporter: Florian Fiby
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
>
> {{{}2022-08-03 02:57:31.059 WARN 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.camel.component.mail.MailConsumer :
> Error opening mail fol{}}}{{{}der due to GSI5 BAD User is authenticated but
> not connected.. Will re-create connection on next poll{}}}
> This leads to disconnect(). disconnect sets folder to null, which leads to
> NullPointerExceptions afterwards:
> {{2022-08-03 02:57:31.073 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.e.DefaultErrorHandler :
> Failed delivery for (MessageId: 61974526595AC2A-0006 on
> ExchangeId: 61974526595AC2A-0006). Exhausted after delivery
> attempt: 0 caught: null}}
> {{{}Message History (source location and message history is
> disabled){}}}{{{}---{}}}{{{}Source
> ID Processor
> Elapsed (ms){}}}{{
> Custom:XXX.
> from[imaps://outlook.office365.com:993?bridgeError 3}}{{
> ...}}{{ Escalation Route/setHeader1
> setHeader[EscalationSender] 0}}
> {{{}Stacktrace{}}}{{{}---{}}}
> {{java.lang.NullPointerException: null}}{{ at
> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:162)
> ~[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(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:829)
> ~[na:na]}}
> {{2022-08-03 02:57:31.074 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.FatalFallbackErrorHandler :
> Exception occurred while trying to handle previously thrown exception on
> exchangeId: 61974526595AC2A-0006 using: [null].}}
>
> {{2022-08-03 02:57:31.081 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.e.DefaultErrorHandler :
> Failed delivery for (MessageId: 61974526595AC2A-0007 on
> ExchangeId: 61974526595AC2A-0007). Exhausted after delivery
> attempt: 1 caught: java.lang.NullPointerException. Processed by failure
> processor: FatalFallbackErrorHandler[null]}}
> {{{}Message History (source location and message history is
> disabled){}}}{{{}---{}}}{{{}Source
> ID Processor
> Elapsed (ms){}}}{{
> Custom:TTITSupport@forstinger.
> from[imaps://outlook.office365.com:993?bridgeError 3}}
> {{{}Stacktrace{}}}{{{}---{}}}
> {{java.lang.NullPointerException: null}}{{ at
>
[jira] [Commented] (CAMEL-18338) IMAP MailConsumer NullPointerException due CAMEL-16180
[
https://issues.apache.org/jira/browse/CAMEL-18338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17574535#comment-17574535
]
Florian Fiby commented on CAMEL-18338:
--
[~davsclaus] issue is related with commit
e02cb28f4b797561ce2b7580206ca26037dd86a7.
After disconnect folder is null and polling is done anyway which leads to
NullPointerException.
I'm not sure whether the intention was to re-create the connection in this
catch or to exit poll and reopen connection with next poll (comment vs logging).
{{ try {}}
{{ if (!folder.isOpen()) {}}
{{ folder.open(Folder.READ_WRITE);}}
{{ }}}
{{ } catch (MessagingException e) {}}
{{ // some kind of connectivity error, so lets re-create connection}}
{{ String msg = "Error opening mail folder due to " + e.getMessage()
+ ". Will re-create connection on next poll.";}}
{{ LOG.warn(msg);}}
{{ if (LOG.isDebugEnabled()) {}}
{{ LOG.debug(msg, e);}}
{{ }}}
{{ disconnect();}}
{{ }}}
> IMAP MailConsumer NullPointerException due CAMEL-16180
> --
>
> Key: CAMEL-18338
> URL: https://issues.apache.org/jira/browse/CAMEL-18338
> Project: Camel
> Issue Type: Bug
> Components: camel-mail
>Affects Versions: 3.18.0
>Reporter: Florian Fiby
>Priority: Major
> Fix For: 3.18.1, 3.19.0
>
>
> {{{}2022-08-03 02:57:31.059 WARN 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.camel.component.mail.MailConsumer :
> Error opening mail fol{}}}{{{}der due to GSI5 BAD User is authenticated but
> not connected.. Will re-create connection on next poll{}}}
> This leads to disconnect(). disconnect sets folder to null, which leads to
> NullPointerExceptions afterwards:
> {{2022-08-03 02:57:31.073 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.e.DefaultErrorHandler :
> Failed delivery for (MessageId: 61974526595AC2A-0006 on
> ExchangeId: 61974526595AC2A-0006). Exhausted after delivery
> attempt: 0 caught: null}}
> {{{}Message History (source location and message history is
> disabled){}}}{{{}---{}}}{{{}Source
> ID Processor
> Elapsed (ms){}}}{{
> Custom:XXX.
> from[imaps://outlook.office365.com:993?bridgeError 3}}{{
> ...}}{{ Escalation Route/setHeader1
> setHeader[EscalationSender] 0}}
> {{{}Stacktrace{}}}{{{}---{}}}
> {{java.lang.NullPointerException: null}}{{ at
> org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:162)
> ~[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(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:829)
> ~[na:na]}}
> {{2022-08-03 02:57:31.074 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.FatalFallbackErrorHandler :
> Exception occurred while trying to handle previously thrown exception on
> exchangeId: 61974526595AC2A-0006 using: [null].}}
>
> {{2022-08-03 02:57:31.081 ERROR 1 --- [Camel
> (ValuemationCustomerMailboxApplication) thread #7 -
> imaps://outlook.office365.com:993] o.a.c.p.e.DefaultErrorHandler :
> Failed delivery for (MessageId: 61974526595AC2A-0007 on
> ExchangeId: 61974526595AC2A-0007). Exhausted after delivery
>
[jira] [Created] (CAMEL-18339) camel-joor - Java DSL - Allow compiled classes to be loadable from anywhere in Camel
Claus Ibsen created CAMEL-18339: --- Summary: camel-joor - Java DSL - Allow compiled classes to be loadable from anywhere in Camel Key: CAMEL-18339 URL: https://issues.apache.org/jira/browse/CAMEL-18339 Project: Camel Issue Type: Improvement Components: camel-joor Reporter: Claus Ibsen Fix For: 3.x See CAMEL-18336 We can maybe for custom classes (not routes) let them be loadable via a special classloader that we then share on CamelContext and its class resolver, so that it can load these classes. Otherwise you need to use BindToRegistry to share the class via bean ids. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18338) IMAP MailConsumer NullPointerException due CAMEL-16180
Florian Fiby created CAMEL-18338:
Summary: IMAP MailConsumer NullPointerException due CAMEL-16180
Key: CAMEL-18338
URL: https://issues.apache.org/jira/browse/CAMEL-18338
Project: Camel
Issue Type: Bug
Components: camel-mail
Affects Versions: 3.18.0
Reporter: Florian Fiby
{{{}2022-08-03 02:57:31.059 WARN 1 --- [Camel
(ValuemationCustomerMailboxApplication) thread #7 -
imaps://outlook.office365.com:993] o.a.camel.component.mail.MailConsumer :
Error opening mail fol{}}}{{{}der due to GSI5 BAD User is authenticated but not
connected.. Will re-create connection on next poll{}}}
This leads to disconnect(). disconnect sets folder to null, which leads to
NullPointerExceptions afterwards:
{{2022-08-03 02:57:31.073 ERROR 1 --- [Camel
(ValuemationCustomerMailboxApplication) thread #7 -
imaps://outlook.office365.com:993] o.a.c.p.e.DefaultErrorHandler :
Failed delivery for (MessageId: 61974526595AC2A-0006 on ExchangeId:
61974526595AC2A-0006). Exhausted after delivery attempt: 0 caught:
null}}
{{{}Message History (source location and message history is
disabled){}}}{{{}---{}}}{{{}Source
ID Processor
Elapsed (ms){}}}{{
Custom:XXX. from[imaps://outlook.office365.com:993?bridgeError
3}}{{ ...}}{{
Escalation Route/setHeader1 setHeader[EscalationSender]
0}}
{{{}Stacktrace{}}}{{{}---{}}}
{{java.lang.NullPointerException: null}}{{ at
org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:162)
~[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(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:829)
~[na:na]}}
{{2022-08-03 02:57:31.074 ERROR 1 --- [Camel
(ValuemationCustomerMailboxApplication) thread #7 -
imaps://outlook.office365.com:993] o.a.c.p.FatalFallbackErrorHandler :
Exception occurred while trying to handle previously thrown exception on
exchangeId: 61974526595AC2A-0006 using: [null].}}
{{2022-08-03 02:57:31.081 ERROR 1 --- [Camel
(ValuemationCustomerMailboxApplication) thread #7 -
imaps://outlook.office365.com:993] o.a.c.p.e.DefaultErrorHandler :
Failed delivery for (MessageId: 61974526595AC2A-0007 on ExchangeId:
61974526595AC2A-0007). Exhausted after delivery attempt: 1 caught:
java.lang.NullPointerException. Processed by failure processor:
FatalFallbackErrorHandler[null]}}
{{{}Message History (source location and message history is
disabled){}}}{{{}---{}}}{{{}Source
ID Processor
Elapsed (ms){}}}{{
Custom:TTITSupport@forstinger.
from[imaps://outlook.office365.com:993?bridgeError 3}}
{{{}Stacktrace{}}}{{{}---{}}}
{{java.lang.NullPointerException: null}}{{ at
org.apache.camel.component.mail.MailConsumer.poll(MailConsumer.java:189)
~[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
