[jira] [Commented] (CAMEL-19719) camel-core - Infinite loop when maximumRedeliveries > 0
[
https://issues.apache.org/jira/browse/CAMEL-19719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751897#comment-17751897
]
Claus Ibsen commented on CAMEL-19719:
-
M1 works and M2 fails
> camel-core - Infinite loop when maximumRedeliveries > 0
> ---
>
> Key: CAMEL-19719
> URL: https://issues.apache.org/jira/browse/CAMEL-19719
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.20.3, 3.21.0, 4.0-M2
>Reporter: Jean Lepropre
>Assignee: Claus Ibsen
>Priority: Critical
> Fix For: 3.20.7, 3.21.1, 3.22.0, 4.0.0
>
> Attachments: test.camel.yaml
>
>
> Using the attached YAML file with Camel (JBang) *3.20.2* gives:
> {noformat}
> 2023-08-07 15:50:51.498 INFO 22092 --- [ main]
> org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.2 is starting
> 2023-08-07 15:50:51.670 INFO 22092 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 22092.
> Started by in
> 2023-08-07 15:50:51.693 INFO 22092 --- [ main]
> mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
> 2023-08-07 15:50:54.143 INFO 22092 --- [ main]
> .download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-activemq:3.20.2 (took: 1s520ms)
> 2023-08-07 15:50:54.356 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) is starting
> 2023-08-07 15:50:54.694 INFO 22092 --- [ main]
> .core.spi.resolver.ResolverProvider : Using the default address resolver as
> the dns resolver could not be loaded
> 2023-08-07 15:50:55.003 INFO 22092 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> 2023-08-07 15:50:55.135 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Routes startup (started:1)
> 2023-08-07 15:50:55.136 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Started route-4ec8
> (activemq://)
> 2023-08-07 15:50:55.137 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) started in
> 1s78ms (build:111ms init:195ms start:772ms JVM-uptime:4s)
> 2023-08-07 15:51:28.671 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 0 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:29.695 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 1 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:30.715 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 2 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:30.735 INFO 22092 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> {noformat}
> While using the same file with Camel (JBang) *3.20.3* leads to an infinite
> loop:
> {noformat}
> 2023-08-07 15:52:42.843 INFO 24144 --- [ main]
> org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.3 is starting
> 2023-08-07 15:52:43.012 INFO 24144 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 24144.
> Started by in
> 2023-08-07 15:52:43.036 INFO 24144 --- [ main]
> mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
> 2023-08-07 15:52:45.390 INFO 24144 --- [ main]
> .download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-activemq:3.20.3 (took: 1s501ms)
> 2023-08-07 15:52:45.596 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.3 (test) is starting
> 2023-08-07 15:52:45.892 INFO 24144 --- [ main]
> .core.spi.resolver.ResolverProvider : Using the default address resolver as
> the dns resolver could not be loaded
> 2023-08-07 15:52:46.222 INFO 24144 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> 2023-08-07 15:52:46.287 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Routes startup (started:1)
> 2023-08-07 15:52:46.288
[jira] [Updated] (CAMEL-19719) camel-core - Infinite loop when maximumRedeliveries > 0
[
https://issues.apache.org/jira/browse/CAMEL-19719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19719:
Affects Version/s: 4.0-M2
> camel-core - Infinite loop when maximumRedeliveries > 0
> ---
>
> Key: CAMEL-19719
> URL: https://issues.apache.org/jira/browse/CAMEL-19719
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.20.3, 3.21.0, 4.0-M2
>Reporter: Jean Lepropre
>Assignee: Claus Ibsen
>Priority: Critical
> Fix For: 3.20.7, 3.21.1, 3.22.0, 4.0.0
>
> Attachments: test.camel.yaml
>
>
> Using the attached YAML file with Camel (JBang) *3.20.2* gives:
> {noformat}
> 2023-08-07 15:50:51.498 INFO 22092 --- [ main]
> org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.2 is starting
> 2023-08-07 15:50:51.670 INFO 22092 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 22092.
> Started by in
> 2023-08-07 15:50:51.693 INFO 22092 --- [ main]
> mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
> 2023-08-07 15:50:54.143 INFO 22092 --- [ main]
> .download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-activemq:3.20.2 (took: 1s520ms)
> 2023-08-07 15:50:54.356 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) is starting
> 2023-08-07 15:50:54.694 INFO 22092 --- [ main]
> .core.spi.resolver.ResolverProvider : Using the default address resolver as
> the dns resolver could not be loaded
> 2023-08-07 15:50:55.003 INFO 22092 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> 2023-08-07 15:50:55.135 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Routes startup (started:1)
> 2023-08-07 15:50:55.136 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Started route-4ec8
> (activemq://)
> 2023-08-07 15:50:55.137 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) started in
> 1s78ms (build:111ms init:195ms start:772ms JVM-uptime:4s)
> 2023-08-07 15:51:28.671 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 0 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:29.695 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 1 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:30.715 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 2 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:30.735 INFO 22092 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> {noformat}
> While using the same file with Camel (JBang) *3.20.3* leads to an infinite
> loop:
> {noformat}
> 2023-08-07 15:52:42.843 INFO 24144 --- [ main]
> org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.3 is starting
> 2023-08-07 15:52:43.012 INFO 24144 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 24144.
> Started by in
> 2023-08-07 15:52:43.036 INFO 24144 --- [ main]
> mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
> 2023-08-07 15:52:45.390 INFO 24144 --- [ main]
> .download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-activemq:3.20.3 (took: 1s501ms)
> 2023-08-07 15:52:45.596 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.3 (test) is starting
> 2023-08-07 15:52:45.892 INFO 24144 --- [ main]
> .core.spi.resolver.ResolverProvider : Using the default address resolver as
> the dns resolver could not be loaded
> 2023-08-07 15:52:46.222 INFO 24144 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> 2023-08-07 15:52:46.287 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Routes startup (started:1)
> 2023-08-07 15:52:46.288 INFO 24144 --- [ main]
>
[jira] [Commented] (CAMEL-19720) camel-test-infra: service initialization failure does not provide sufficient details
[
https://issues.apache.org/jira/browse/CAMEL-19720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751895#comment-17751895
]
Otavio Rodolfo Piske commented on CAMEL-19720:
--
It is done, but I am waiting for the CI job to finish before closing this:
https://ci-builds.apache.org/job/Camel/job/Camel%20JDK17/job/main/1087/
> camel-test-infra: service initialization failure does not provide sufficient
> details
>
>
> Key: CAMEL-19720
> URL: https://issues.apache.org/jira/browse/CAMEL-19720
> Project: Camel
> Issue Type: Bug
> Components: camel-test-infra
>Affects Versions: 4.0-RC2
>Reporter: Otavio Rodolfo Piske
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 4.0.0
>
>
> When a service fails to initialize, sometimes the only information available
> on the logs is:
> {code:java}
> java.util.NoSuchElementException: No value present
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19720) camel-test-infra: service initialization failure does not provide sufficient details
[
https://issues.apache.org/jira/browse/CAMEL-19720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751893#comment-17751893
]
Claus Ibsen commented on CAMEL-19720:
-
Is this done
> camel-test-infra: service initialization failure does not provide sufficient
> details
>
>
> Key: CAMEL-19720
> URL: https://issues.apache.org/jira/browse/CAMEL-19720
> Project: Camel
> Issue Type: Bug
> Components: camel-test-infra
>Affects Versions: 4.0-RC2
>Reporter: Otavio Rodolfo Piske
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 4.0.0
>
>
> When a service fails to initialize, sometimes the only information available
> on the logs is:
> {code:java}
> java.util.NoSuchElementException: No value present
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19722) camel-etcd3 - Upgrade jedtc to 0.7.6
Claus Ibsen created CAMEL-19722: --- Summary: camel-etcd3 - Upgrade jedtc to 0.7.6 Key: CAMEL-19722 URL: https://issues.apache.org/jira/browse/CAMEL-19722 Project: Camel Issue Type: Dependency upgrade Reporter: Claus Ibsen This gives a test error. Works with 0.7.5 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19597) Upgrade dependencies before 4.0 GA
[ https://issues.apache.org/jira/browse/CAMEL-19597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19597. - Resolution: Fixed > Upgrade dependencies before 4.0 GA > -- > > Key: CAMEL-19597 > URL: https://issues.apache.org/jira/browse/CAMEL-19597 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0.0 > > > Lets see if we can upgrade some more of these dependencies > https://gist.github.com/jamesnetherton/023a95668adbed8beb3271667ee398f4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19719) Infinite loop when maximumRedeliveries > 0
[
https://issues.apache.org/jira/browse/CAMEL-19719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751789#comment-17751789
]
Claus Ibsen commented on CAMEL-19719:
-
Yeah this is a bit weird we haven't see this reported before, or that some of
the core unit tests didn't fail before.
> Infinite loop when maximumRedeliveries > 0
> --
>
> Key: CAMEL-19719
> URL: https://issues.apache.org/jira/browse/CAMEL-19719
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.20.3, 3.21.0
>Reporter: Jean Lepropre
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.20.7, 3.21.1, 3.22.0, 4.0.0
>
> Attachments: test.camel.yaml
>
>
> Using the attached YAML file with Camel (JBang) *3.20.2* gives:
> {noformat}
> 2023-08-07 15:50:51.498 INFO 22092 --- [ main]
> org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.2 is starting
> 2023-08-07 15:50:51.670 INFO 22092 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 22092.
> Started by in
> 2023-08-07 15:50:51.693 INFO 22092 --- [ main]
> mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
> 2023-08-07 15:50:54.143 INFO 22092 --- [ main]
> .download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-activemq:3.20.2 (took: 1s520ms)
> 2023-08-07 15:50:54.356 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) is starting
> 2023-08-07 15:50:54.694 INFO 22092 --- [ main]
> .core.spi.resolver.ResolverProvider : Using the default address resolver as
> the dns resolver could not be loaded
> 2023-08-07 15:50:55.003 INFO 22092 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> 2023-08-07 15:50:55.135 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Routes startup (started:1)
> 2023-08-07 15:50:55.136 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Started route-4ec8
> (activemq://)
> 2023-08-07 15:50:55.137 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) started in
> 1s78ms (build:111ms init:195ms start:772ms JVM-uptime:4s)
> 2023-08-07 15:51:28.671 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 0 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:29.695 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 1 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:30.715 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 2 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:30.735 INFO 22092 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> {noformat}
> While using the same file with Camel (JBang) *3.20.3* leads to an infinite
> loop:
> {noformat}
> 2023-08-07 15:52:42.843 INFO 24144 --- [ main]
> org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.3 is starting
> 2023-08-07 15:52:43.012 INFO 24144 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 24144.
> Started by in
> 2023-08-07 15:52:43.036 INFO 24144 --- [ main]
> mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
> 2023-08-07 15:52:45.390 INFO 24144 --- [ main]
> .download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-activemq:3.20.3 (took: 1s501ms)
> 2023-08-07 15:52:45.596 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.3 (test) is starting
> 2023-08-07 15:52:45.892 INFO 24144 --- [ main]
> .core.spi.resolver.ResolverProvider : Using the default address resolver as
> the dns resolver could not be loaded
> 2023-08-07 15:52:46.222 INFO 24144 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> 2023-08-07 15:52:46.287 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext
[jira] [Updated] (CAMEL-19719) camel-core - Infinite loop when maximumRedeliveries > 0
[
https://issues.apache.org/jira/browse/CAMEL-19719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19719:
Summary: camel-core - Infinite loop when maximumRedeliveries > 0 (was:
Infinite loop when maximumRedeliveries > 0)
> camel-core - Infinite loop when maximumRedeliveries > 0
> ---
>
> Key: CAMEL-19719
> URL: https://issues.apache.org/jira/browse/CAMEL-19719
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.20.3, 3.21.0
>Reporter: Jean Lepropre
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.20.7, 3.21.1, 3.22.0, 4.0.0
>
> Attachments: test.camel.yaml
>
>
> Using the attached YAML file with Camel (JBang) *3.20.2* gives:
> {noformat}
> 2023-08-07 15:50:51.498 INFO 22092 --- [ main]
> org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.2 is starting
> 2023-08-07 15:50:51.670 INFO 22092 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 22092.
> Started by in
> 2023-08-07 15:50:51.693 INFO 22092 --- [ main]
> mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
> 2023-08-07 15:50:54.143 INFO 22092 --- [ main]
> .download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-activemq:3.20.2 (took: 1s520ms)
> 2023-08-07 15:50:54.356 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) is starting
> 2023-08-07 15:50:54.694 INFO 22092 --- [ main]
> .core.spi.resolver.ResolverProvider : Using the default address resolver as
> the dns resolver could not be loaded
> 2023-08-07 15:50:55.003 INFO 22092 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> 2023-08-07 15:50:55.135 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Routes startup (started:1)
> 2023-08-07 15:50:55.136 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Started route-4ec8
> (activemq://)
> 2023-08-07 15:50:55.137 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) started in
> 1s78ms (build:111ms init:195ms start:772ms JVM-uptime:4s)
> 2023-08-07 15:51:28.671 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 0 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:29.695 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 1 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:30.715 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 2 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:30.735 INFO 22092 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> {noformat}
> While using the same file with Camel (JBang) *3.20.3* leads to an infinite
> loop:
> {noformat}
> 2023-08-07 15:52:42.843 INFO 24144 --- [ main]
> org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.3 is starting
> 2023-08-07 15:52:43.012 INFO 24144 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 24144.
> Started by in
> 2023-08-07 15:52:43.036 INFO 24144 --- [ main]
> mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
> 2023-08-07 15:52:45.390 INFO 24144 --- [ main]
> .download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-activemq:3.20.3 (took: 1s501ms)
> 2023-08-07 15:52:45.596 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.3 (test) is starting
> 2023-08-07 15:52:45.892 INFO 24144 --- [ main]
> .core.spi.resolver.ResolverProvider : Using the default address resolver as
> the dns resolver could not be loaded
> 2023-08-07 15:52:46.222 INFO 24144 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> 2023-08-07 15:52:46.287 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Routes
[jira] [Updated] (CAMEL-19719) camel-core - Infinite loop when maximumRedeliveries > 0
[
https://issues.apache.org/jira/browse/CAMEL-19719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19719:
Priority: Critical (was: Major)
> camel-core - Infinite loop when maximumRedeliveries > 0
> ---
>
> Key: CAMEL-19719
> URL: https://issues.apache.org/jira/browse/CAMEL-19719
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.20.3, 3.21.0
>Reporter: Jean Lepropre
>Assignee: Claus Ibsen
>Priority: Critical
> Fix For: 3.20.7, 3.21.1, 3.22.0, 4.0.0
>
> Attachments: test.camel.yaml
>
>
> Using the attached YAML file with Camel (JBang) *3.20.2* gives:
> {noformat}
> 2023-08-07 15:50:51.498 INFO 22092 --- [ main]
> org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.2 is starting
> 2023-08-07 15:50:51.670 INFO 22092 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 22092.
> Started by in
> 2023-08-07 15:50:51.693 INFO 22092 --- [ main]
> mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
> 2023-08-07 15:50:54.143 INFO 22092 --- [ main]
> .download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-activemq:3.20.2 (took: 1s520ms)
> 2023-08-07 15:50:54.356 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) is starting
> 2023-08-07 15:50:54.694 INFO 22092 --- [ main]
> .core.spi.resolver.ResolverProvider : Using the default address resolver as
> the dns resolver could not be loaded
> 2023-08-07 15:50:55.003 INFO 22092 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> 2023-08-07 15:50:55.135 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Routes startup (started:1)
> 2023-08-07 15:50:55.136 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Started route-4ec8
> (activemq://)
> 2023-08-07 15:50:55.137 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) started in
> 1s78ms (build:111ms init:195ms start:772ms JVM-uptime:4s)
> 2023-08-07 15:51:28.671 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 0 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:29.695 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 1 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:30.715 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 2 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:30.735 INFO 22092 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> {noformat}
> While using the same file with Camel (JBang) *3.20.3* leads to an infinite
> loop:
> {noformat}
> 2023-08-07 15:52:42.843 INFO 24144 --- [ main]
> org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.3 is starting
> 2023-08-07 15:52:43.012 INFO 24144 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 24144.
> Started by in
> 2023-08-07 15:52:43.036 INFO 24144 --- [ main]
> mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
> 2023-08-07 15:52:45.390 INFO 24144 --- [ main]
> .download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-activemq:3.20.3 (took: 1s501ms)
> 2023-08-07 15:52:45.596 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.3 (test) is starting
> 2023-08-07 15:52:45.892 INFO 24144 --- [ main]
> .core.spi.resolver.ResolverProvider : Using the default address resolver as
> the dns resolver could not be loaded
> 2023-08-07 15:52:46.222 INFO 24144 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> 2023-08-07 15:52:46.287 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Routes startup (started:1)
> 2023-08-07 15:52:46.288 INFO 24144 --- [ main]
>
[jira] [Updated] (CAMEL-19719) Infinite loop when maximumRedeliveries > 0
[
https://issues.apache.org/jira/browse/CAMEL-19719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19719:
Fix Version/s: 3.20.7
3.21.1
3.22.0
> Infinite loop when maximumRedeliveries > 0
> --
>
> Key: CAMEL-19719
> URL: https://issues.apache.org/jira/browse/CAMEL-19719
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.20.3, 3.21.0
>Reporter: Jean Lepropre
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.20.7, 3.21.1, 3.22.0, 4.0.0
>
> Attachments: test.camel.yaml
>
>
> Using the attached YAML file with Camel (JBang) *3.20.2* gives:
> {noformat}
> 2023-08-07 15:50:51.498 INFO 22092 --- [ main]
> org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.2 is starting
> 2023-08-07 15:50:51.670 INFO 22092 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 22092.
> Started by in
> 2023-08-07 15:50:51.693 INFO 22092 --- [ main]
> mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
> 2023-08-07 15:50:54.143 INFO 22092 --- [ main]
> .download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-activemq:3.20.2 (took: 1s520ms)
> 2023-08-07 15:50:54.356 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) is starting
> 2023-08-07 15:50:54.694 INFO 22092 --- [ main]
> .core.spi.resolver.ResolverProvider : Using the default address resolver as
> the dns resolver could not be loaded
> 2023-08-07 15:50:55.003 INFO 22092 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> 2023-08-07 15:50:55.135 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Routes startup (started:1)
> 2023-08-07 15:50:55.136 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Started route-4ec8
> (activemq://)
> 2023-08-07 15:50:55.137 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) started in
> 1s78ms (build:111ms init:195ms start:772ms JVM-uptime:4s)
> 2023-08-07 15:51:28.671 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 0 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:29.695 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 1 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:30.715 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 2 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:30.735 INFO 22092 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> {noformat}
> While using the same file with Camel (JBang) *3.20.3* leads to an infinite
> loop:
> {noformat}
> 2023-08-07 15:52:42.843 INFO 24144 --- [ main]
> org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.3 is starting
> 2023-08-07 15:52:43.012 INFO 24144 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 24144.
> Started by in
> 2023-08-07 15:52:43.036 INFO 24144 --- [ main]
> mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
> 2023-08-07 15:52:45.390 INFO 24144 --- [ main]
> .download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-activemq:3.20.3 (took: 1s501ms)
> 2023-08-07 15:52:45.596 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.3 (test) is starting
> 2023-08-07 15:52:45.892 INFO 24144 --- [ main]
> .core.spi.resolver.ResolverProvider : Using the default address resolver as
> the dns resolver could not be loaded
> 2023-08-07 15:52:46.222 INFO 24144 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> 2023-08-07 15:52:46.287 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Routes startup (started:1)
> 2023-08-07 15:52:46.288 INFO 24144 --- [
[jira] [Updated] (CAMEL-19719) Infinite loop when maximumRedeliveries > 0
[
https://issues.apache.org/jira/browse/CAMEL-19719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-19719:
Fix Version/s: 4.0.0
> Infinite loop when maximumRedeliveries > 0
> --
>
> Key: CAMEL-19719
> URL: https://issues.apache.org/jira/browse/CAMEL-19719
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.20.3, 3.21.0
>Reporter: Jean Lepropre
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.0.0
>
> Attachments: test.camel.yaml
>
>
> Using the attached YAML file with Camel (JBang) *3.20.2* gives:
> {noformat}
> 2023-08-07 15:50:51.498 INFO 22092 --- [ main]
> org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.2 is starting
> 2023-08-07 15:50:51.670 INFO 22092 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 22092.
> Started by in
> 2023-08-07 15:50:51.693 INFO 22092 --- [ main]
> mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
> 2023-08-07 15:50:54.143 INFO 22092 --- [ main]
> .download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-activemq:3.20.2 (took: 1s520ms)
> 2023-08-07 15:50:54.356 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) is starting
> 2023-08-07 15:50:54.694 INFO 22092 --- [ main]
> .core.spi.resolver.ResolverProvider : Using the default address resolver as
> the dns resolver could not be loaded
> 2023-08-07 15:50:55.003 INFO 22092 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> 2023-08-07 15:50:55.135 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Routes startup (started:1)
> 2023-08-07 15:50:55.136 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Started route-4ec8
> (activemq://)
> 2023-08-07 15:50:55.137 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) started in
> 1s78ms (build:111ms init:195ms start:772ms JVM-uptime:4s)
> 2023-08-07 15:51:28.671 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 0 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:29.695 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 1 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:30.715 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 2 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:30.735 INFO 22092 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> {noformat}
> While using the same file with Camel (JBang) *3.20.3* leads to an infinite
> loop:
> {noformat}
> 2023-08-07 15:52:42.843 INFO 24144 --- [ main]
> org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.3 is starting
> 2023-08-07 15:52:43.012 INFO 24144 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 24144.
> Started by in
> 2023-08-07 15:52:43.036 INFO 24144 --- [ main]
> mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
> 2023-08-07 15:52:45.390 INFO 24144 --- [ main]
> .download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-activemq:3.20.3 (took: 1s501ms)
> 2023-08-07 15:52:45.596 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.3 (test) is starting
> 2023-08-07 15:52:45.892 INFO 24144 --- [ main]
> .core.spi.resolver.ResolverProvider : Using the default address resolver as
> the dns resolver could not be loaded
> 2023-08-07 15:52:46.222 INFO 24144 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> 2023-08-07 15:52:46.287 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Routes startup (started:1)
> 2023-08-07 15:52:46.288 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Started route-4ec8
>
[jira] [Assigned] (CAMEL-19719) Infinite loop when maximumRedeliveries > 0
[
https://issues.apache.org/jira/browse/CAMEL-19719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-19719:
---
Assignee: Claus Ibsen
> Infinite loop when maximumRedeliveries > 0
> --
>
> Key: CAMEL-19719
> URL: https://issues.apache.org/jira/browse/CAMEL-19719
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.20.3, 3.21.0
>Reporter: Jean Lepropre
>Assignee: Claus Ibsen
>Priority: Major
> Attachments: test.camel.yaml
>
>
> Using the attached YAML file with Camel (JBang) *3.20.2* gives:
> {noformat}
> 2023-08-07 15:50:51.498 INFO 22092 --- [ main]
> org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.2 is starting
> 2023-08-07 15:50:51.670 INFO 22092 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 22092.
> Started by in
> 2023-08-07 15:50:51.693 INFO 22092 --- [ main]
> mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
> 2023-08-07 15:50:54.143 INFO 22092 --- [ main]
> .download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-activemq:3.20.2 (took: 1s520ms)
> 2023-08-07 15:50:54.356 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) is starting
> 2023-08-07 15:50:54.694 INFO 22092 --- [ main]
> .core.spi.resolver.ResolverProvider : Using the default address resolver as
> the dns resolver could not be loaded
> 2023-08-07 15:50:55.003 INFO 22092 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> 2023-08-07 15:50:55.135 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Routes startup (started:1)
> 2023-08-07 15:50:55.136 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Started route-4ec8
> (activemq://)
> 2023-08-07 15:50:55.137 INFO 22092 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) started in
> 1s78ms (build:111ms init:195ms start:772ms JVM-uptime:4s)
> 2023-08-07 15:51:28.671 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 0 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:29.695 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 1 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:30.715 WARN 22092 --- [ntloop-thread-1]
> ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
> ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
> attempt: 2 caught:
> io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection
> refused: no further information: localhost/127.0.0.1:8080
> 2023-08-07 15:51:30.735 INFO 22092 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> {noformat}
> While using the same file with Camel (JBang) *3.20.3* leads to an infinite
> loop:
> {noformat}
> 2023-08-07 15:52:42.843 INFO 24144 --- [ main]
> org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.3 is starting
> 2023-08-07 15:52:43.012 INFO 24144 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 24144.
> Started by in
> 2023-08-07 15:52:43.036 INFO 24144 --- [ main]
> mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
> 2023-08-07 15:52:45.390 INFO 24144 --- [ main]
> .download.MavenDependencyDownloader : Downloaded:
> org.apache.camel:camel-activemq:3.20.3 (took: 1s501ms)
> 2023-08-07 15:52:45.596 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Apache Camel 3.20.3 (test) is starting
> 2023-08-07 15:52:45.892 INFO 24144 --- [ main]
> .core.spi.resolver.ResolverProvider : Using the default address resolver as
> the dns resolver could not be loaded
> 2023-08-07 15:52:46.222 INFO 24144 --- [ActiveMQ Task-1]
> ransport.failover.FailoverTransport : Successfully connected to
> tcp://localhost:61616
> 2023-08-07 15:52:46.287 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Routes startup (started:1)
> 2023-08-07 15:52:46.288 INFO 24144 --- [ main]
> el.impl.engine.AbstractCamelContext : Started route-4ec8
> (activemq://)
>
[jira] [Commented] (CAMEL-19597) Upgrade dependencies before 4.0 GA
[ https://issues.apache.org/jira/browse/CAMEL-19597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751776#comment-17751776 ] Claus Ibsen commented on CAMEL-19597: - > io.etcd:jetcd-launcher ( from 0.7.5 to 0.7.6 ), io.etcd:jetcd-core ( from > 0.7.5 to 0.7.6 ) This causes a test failure > Upgrade dependencies before 4.0 GA > -- > > Key: CAMEL-19597 > URL: https://issues.apache.org/jira/browse/CAMEL-19597 > Project: Camel > Issue Type: Dependency upgrade >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0.0 > > > Lets see if we can upgrade some more of these dependencies > https://gist.github.com/jamesnetherton/023a95668adbed8beb3271667ee398f4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19721) camel-activemq - ActiveMQ component should use jakarta based connection pool
[ https://issues.apache.org/jira/browse/CAMEL-19721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19721. - Resolution: Fixed > camel-activemq - ActiveMQ component should use jakarta based connection pool > > > Key: CAMEL-19721 > URL: https://issues.apache.org/jira/browse/CAMEL-19721 > Project: Camel > Issue Type: Improvement > Components: camel-activemq >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0.0 > > > The old code is using activemq-pool which is still javax JMS based so does > not work with Jakarta and Camel v4. > We should change the code to use a jakarat JMS pool like Artemis uses. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19626) camel-google - Upgrade from 1.32.x to 2.x
[ https://issues.apache.org/jira/browse/CAMEL-19626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19626. - Resolution: Fixed > camel-google - Upgrade from 1.32.x to 2.x > - > > Key: CAMEL-19626 > URL: https://issues.apache.org/jira/browse/CAMEL-19626 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-google >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.0.0 > > > The API based components in camel-google (drive, sheets, calendar, etc.) are > in need of updating to latest versions from Google. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19721) camel-activemq - ActiveMQ component should use jakarta based connection pool
[ https://issues.apache.org/jira/browse/CAMEL-19721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19721: Component/s: camel-activemq > camel-activemq - ActiveMQ component should use jakarta based connection pool > > > Key: CAMEL-19721 > URL: https://issues.apache.org/jira/browse/CAMEL-19721 > Project: Camel > Issue Type: Improvement > Components: camel-activemq >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0.0 > > > The old code is using activemq-pool which is still javax JMS based so does > not work with Jakarta and Camel v4. > We should change the code to use a jakarat JMS pool like Artemis uses. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19721) camel-activemq - ActiveMQ component should use jakarta based connection pool
[
https://issues.apache.org/jira/browse/CAMEL-19721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751769#comment-17751769
]
Claus Ibsen commented on CAMEL-19721:
-
This also makes it possible to run camel-jbang with camel-activemq with Camel 4
{code}
~/Downloads ❯ camel run test.camel.yaml
2023-08-07 20:11:29.812 INFO 59570 --- [ main]
org.apache.camel.main.MainSupport : Apache Camel (JBang) 4.0.0-SNAPSHOT is
starting
2023-08-07 20:11:29.925 INFO 59570 --- [ main]
org.apache.camel.main.MainSupport : Using Java 17.0.5 with PID 59570. Started
by davsclaus in /Users/davsclaus/Downloads
2023-08-07 20:11:30.588 INFO 59570 --- [ main]
mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
2023-08-07 20:11:30.681 INFO 59570 --- [ main]
el.impl.engine.AbstractCamelContext : Apache Camel 4.0.0-SNAPSHOT (test) is
starting
2023-08-07 20:11:30.811 INFO 59570 --- [ main]
.core.spi.resolver.ResolverProvider : Using the default address resolver as the
dns resolver could not be loaded
2023-08-07 20:11:31.025 WARN 59570 --- [ActiveMQ Task-1]
ransport.failover.FailoverTransport : Failed to connect to
[tcp://localhost:61616] after: 1 attempt(s) with Connection refused, continuing
to retry.
2023-08-07 20:11:36.184 WARN 59570 --- [ActiveMQ Task-1]
ransport.failover.FailoverTransport : Failed to connect to
[tcp://localhost:61616] after: 10 attempt(s) with Connection refused,
continuing to retry.
{code}
The output above start up but since I dont have a local ActiveMQ 5.x running it
fails to connect.
Without this PR then you will get class loader errors.
> camel-activemq - ActiveMQ component should use jakarta based connection pool
>
>
> Key: CAMEL-19721
> URL: https://issues.apache.org/jira/browse/CAMEL-19721
> Project: Camel
> Issue Type: Improvement
>Reporter: Claus Ibsen
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 4.0.0
>
>
> The old code is using activemq-pool which is still javax JMS based so does
> not work with Jakarta and Camel v4.
> We should change the code to use a jakarat JMS pool like Artemis uses.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19721) camel-activemq - ActiveMQ component should use jakarta based connection pool
Claus Ibsen created CAMEL-19721: --- Summary: camel-activemq - ActiveMQ component should use jakarta based connection pool Key: CAMEL-19721 URL: https://issues.apache.org/jira/browse/CAMEL-19721 Project: Camel Issue Type: Improvement Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 4.0.0 The old code is using activemq-pool which is still javax JMS based so does not work with Jakarta and Camel v4. We should change the code to use a jakarat JMS pool like Artemis uses. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-12317) Provide integration with AWS Step Functions
[ https://issues.apache.org/jira/browse/CAMEL-12317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12317: Fix Version/s: 4.0.0 (was: 4.1.0) > Provide integration with AWS Step Functions > --- > > Key: CAMEL-12317 > URL: https://issues.apache.org/jira/browse/CAMEL-12317 > Project: Camel > Issue Type: New Feature > Components: camel-aws >Reporter: Christian Müller >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.0.0 > > > Provide integration with AWS Step Functions: > [https://aws.amazon.com/step-functions/] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19720) camel-test-infra: service initialization failure does not provide sufficient details
[
https://issues.apache.org/jira/browse/CAMEL-19720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-19720:
-
Fix Version/s: 4.0.0
> camel-test-infra: service initialization failure does not provide sufficient
> details
>
>
> Key: CAMEL-19720
> URL: https://issues.apache.org/jira/browse/CAMEL-19720
> Project: Camel
> Issue Type: Bug
> Components: camel-test-infra
>Reporter: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 4.0.0
>
>
> When a service fails to initialize, sometimes the only information available
> on the logs is:
> {code:java}
> java.util.NoSuchElementException: No value present
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19720) camel-test-infra: service initialization failure does not provide sufficient details
[
https://issues.apache.org/jira/browse/CAMEL-19720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-19720:
-
Affects Version/s: 4.0-RC2
> camel-test-infra: service initialization failure does not provide sufficient
> details
>
>
> Key: CAMEL-19720
> URL: https://issues.apache.org/jira/browse/CAMEL-19720
> Project: Camel
> Issue Type: Bug
> Components: camel-test-infra
>Affects Versions: 4.0-RC2
>Reporter: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 4.0.0
>
>
> When a service fails to initialize, sometimes the only information available
> on the logs is:
> {code:java}
> java.util.NoSuchElementException: No value present
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-19720) camel-test-infra: service initialization failure does not provide sufficient details
[
https://issues.apache.org/jira/browse/CAMEL-19720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske reassigned CAMEL-19720:
Assignee: Otavio Rodolfo Piske
> camel-test-infra: service initialization failure does not provide sufficient
> details
>
>
> Key: CAMEL-19720
> URL: https://issues.apache.org/jira/browse/CAMEL-19720
> Project: Camel
> Issue Type: Bug
> Components: camel-test-infra
>Affects Versions: 4.0-RC2
>Reporter: Otavio Rodolfo Piske
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 4.0.0
>
>
> When a service fails to initialize, sometimes the only information available
> on the logs is:
> {code:java}
> java.util.NoSuchElementException: No value present
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19720) camel-test-infra: service initialization failure does not provide sufficient details
[
https://issues.apache.org/jira/browse/CAMEL-19720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-19720:
-
Component/s: camel-test-infra
> camel-test-infra: service initialization failure does not provide sufficient
> details
>
>
> Key: CAMEL-19720
> URL: https://issues.apache.org/jira/browse/CAMEL-19720
> Project: Camel
> Issue Type: Bug
> Components: camel-test-infra
>Reporter: Otavio Rodolfo Piske
>Priority: Major
>
> When a service fails to initialize, sometimes the only information available
> on the logs is:
> {code:java}
> java.util.NoSuchElementException: No value present
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19720) camel-test-infra: service initialization failure does not provide sufficient details
Otavio Rodolfo Piske created CAMEL-19720:
Summary: camel-test-infra: service initialization failure does not
provide sufficient details
Key: CAMEL-19720
URL: https://issues.apache.org/jira/browse/CAMEL-19720
Project: Camel
Issue Type: Task
Reporter: Otavio Rodolfo Piske
When a service fails to initialize, sometimes the only information available on
the logs is:
{code:java}
java.util.NoSuchElementException: No value present
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-19720) camel-test-infra: service initialization failure does not provide sufficient details
[
https://issues.apache.org/jira/browse/CAMEL-19720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske updated CAMEL-19720:
-
Issue Type: Bug (was: Task)
> camel-test-infra: service initialization failure does not provide sufficient
> details
>
>
> Key: CAMEL-19720
> URL: https://issues.apache.org/jira/browse/CAMEL-19720
> Project: Camel
> Issue Type: Bug
>Reporter: Otavio Rodolfo Piske
>Priority: Major
>
> When a service fails to initialize, sometimes the only information available
> on the logs is:
> {code:java}
> java.util.NoSuchElementException: No value present
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-19618) camel-box - Upgrade to v4
[ https://issues.apache.org/jira/browse/CAMEL-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19618. - Resolution: Fixed > camel-box - Upgrade to v4 > - > > Key: CAMEL-19618 > URL: https://issues.apache.org/jira/browse/CAMEL-19618 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-box >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.0.0 > > > We use an older v2 java-sdk and should upgrade to v4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19719) Infinite loop when maximumRedeliveries > 0
[
https://issues.apache.org/jira/browse/CAMEL-19719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean Lepropre updated CAMEL-19719:
--
Description:
Using the attached YAML file with Camel (JBang) *3.20.2* gives:
{noformat}
2023-08-07 15:50:51.498 INFO 22092 --- [ main]
org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.2 is starting
2023-08-07 15:50:51.670 INFO 22092 --- [ main]
org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 22092. Started
by in
2023-08-07 15:50:51.693 INFO 22092 --- [ main]
mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
2023-08-07 15:50:54.143 INFO 22092 --- [ main]
.download.MavenDependencyDownloader : Downloaded:
org.apache.camel:camel-activemq:3.20.2 (took: 1s520ms)
2023-08-07 15:50:54.356 INFO 22092 --- [ main]
el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) is starting
2023-08-07 15:50:54.694 INFO 22092 --- [ main]
.core.spi.resolver.ResolverProvider : Using the default address resolver as the
dns resolver could not be loaded
2023-08-07 15:50:55.003 INFO 22092 --- [ActiveMQ Task-1]
ransport.failover.FailoverTransport : Successfully connected to
tcp://localhost:61616
2023-08-07 15:50:55.135 INFO 22092 --- [ main]
el.impl.engine.AbstractCamelContext : Routes startup (started:1)
2023-08-07 15:50:55.136 INFO 22092 --- [ main]
el.impl.engine.AbstractCamelContext : Started route-4ec8
(activemq://)
2023-08-07 15:50:55.137 INFO 22092 --- [ main]
el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) started in
1s78ms (build:111ms init:195ms start:772ms JVM-uptime:4s)
2023-08-07 15:51:28.671 WARN 22092 --- [ntloop-thread-1]
ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
attempt: 0 caught: io.netty.channel.AbstractChannel$AnnotatedConnectException:
Connection refused: no further information: localhost/127.0.0.1:8080
2023-08-07 15:51:29.695 WARN 22092 --- [ntloop-thread-1]
ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
attempt: 1 caught: io.netty.channel.AbstractChannel$AnnotatedConnectException:
Connection refused: no further information: localhost/127.0.0.1:8080
2023-08-07 15:51:30.715 WARN 22092 --- [ntloop-thread-1]
ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
attempt: 2 caught: io.netty.channel.AbstractChannel$AnnotatedConnectException:
Connection refused: no further information: localhost/127.0.0.1:8080
2023-08-07 15:51:30.735 INFO 22092 --- [ActiveMQ Task-1]
ransport.failover.FailoverTransport : Successfully connected to
tcp://localhost:61616
{noformat}
While using the same file with Camel (JBang) *3.20.3* leads to an infinite loop:
{noformat}
2023-08-07 15:52:42.843 INFO 24144 --- [ main]
org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.3 is starting
2023-08-07 15:52:43.012 INFO 24144 --- [ main]
org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 24144. Started
by in
2023-08-07 15:52:43.036 INFO 24144 --- [ main]
mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
2023-08-07 15:52:45.390 INFO 24144 --- [ main]
.download.MavenDependencyDownloader : Downloaded:
org.apache.camel:camel-activemq:3.20.3 (took: 1s501ms)
2023-08-07 15:52:45.596 INFO 24144 --- [ main]
el.impl.engine.AbstractCamelContext : Apache Camel 3.20.3 (test) is starting
2023-08-07 15:52:45.892 INFO 24144 --- [ main]
.core.spi.resolver.ResolverProvider : Using the default address resolver as the
dns resolver could not be loaded
2023-08-07 15:52:46.222 INFO 24144 --- [ActiveMQ Task-1]
ransport.failover.FailoverTransport : Successfully connected to
tcp://localhost:61616
2023-08-07 15:52:46.287 INFO 24144 --- [ main]
el.impl.engine.AbstractCamelContext : Routes startup (started:1)
2023-08-07 15:52:46.288 INFO 24144 --- [ main]
el.impl.engine.AbstractCamelContext : Started route-4ec8
(activemq://)
2023-08-07 15:52:46.289 INFO 24144 --- [ main]
el.impl.engine.AbstractCamelContext : Apache Camel 3.20.3 (test) started in
985ms (build:105ms init:189ms start:691ms JVM-uptime:4s)
2023-08-07 15:52:58.955 WARN 24144 --- [ntloop-thread-1]
ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
1D22091EB3FABD1- on ExchangeId:
1D22091EB3FABD1-). On delivery attempt: 0 caught:
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused:
no further information: localhost/127.0.0.1:8080
2023-08-07 15:52:59.967 WARN 24144 --- [ntloop-thread-1]
[jira] [Created] (CAMEL-19719) Infinite loop when maximumRedeliveries > 0
Jean Lepropre created CAMEL-19719:
-
Summary: Infinite loop when maximumRedeliveries > 0
Key: CAMEL-19719
URL: https://issues.apache.org/jira/browse/CAMEL-19719
Project: Camel
Issue Type: Bug
Components: came-core
Affects Versions: 3.21.0, 3.20.3
Reporter: Jean Lepropre
Attachments: test.camel.yaml
Using the attached YAML file with Camel (JBang) *3.20.2* gives:
{noformat}
2023-08-07 15:50:51.498 INFO 22092 --- [ main]
org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.2 is starting
2023-08-07 15:50:51.670 INFO 22092 --- [ main]
org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 22092. Started
by in
2023-08-07 15:50:51.693 INFO 22092 --- [ main]
mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
2023-08-07 15:50:54.143 INFO 22092 --- [ main]
.download.MavenDependencyDownloader : Downloaded:
org.apache.camel:camel-activemq:3.20.2 (took: 1s520ms)
2023-08-07 15:50:54.356 INFO 22092 --- [ main]
el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) is starting
2023-08-07 15:50:54.694 INFO 22092 --- [ main]
.core.spi.resolver.ResolverProvider : Using the default address resolver as the
dns resolver could not be loaded
2023-08-07 15:50:55.003 INFO 22092 --- [ActiveMQ Task-1]
ransport.failover.FailoverTransport : Successfully connected to
tcp://localhost:61616
2023-08-07 15:50:55.135 INFO 22092 --- [ main]
el.impl.engine.AbstractCamelContext : Routes startup (started:1)
2023-08-07 15:50:55.136 INFO 22092 --- [ main]
el.impl.engine.AbstractCamelContext : Started route-4ec8
(activemq://)
2023-08-07 15:50:55.137 INFO 22092 --- [ main]
el.impl.engine.AbstractCamelContext : Apache Camel 3.20.2 (test) started in
1s78ms (build:111ms init:195ms start:772ms JVM-uptime:4s)
2023-08-07 15:51:28.671 WARN 22092 --- [ntloop-thread-1]
ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
attempt: 0 caught: io.netty.channel.AbstractChannel$AnnotatedConnectException:
Connection refused: no further information: localhost/127.0.0.1:8080
2023-08-07 15:51:29.695 WARN 22092 --- [ntloop-thread-1]
ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
attempt: 1 caught: io.netty.channel.AbstractChannel$AnnotatedConnectException:
Connection refused: no further information: localhost/127.0.0.1:8080
2023-08-07 15:51:30.715 WARN 22092 --- [ntloop-thread-1]
ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
ID: on ExchangeId: F91414B5DF3A8FC-). On delivery
attempt: 2 caught: io.netty.channel.AbstractChannel$AnnotatedConnectException:
Connection refused: no further information: localhost/127.0.0.1:8080
2023-08-07 15:51:30.735 INFO 22092 --- [ActiveMQ Task-1]
ransport.failover.FailoverTransport : Successfully connected to
tcp://localhost:61616
{noformat}
While using the same file with Camel (JBang) *3.20.3* leads to an infinite loop:
{noformat}
2023-08-07 15:52:42.843 INFO 24144 --- [ main]
org.apache.camel.main.MainSupport : Apache Camel (JBang) 3.20.3 is starting
2023-08-07 15:52:43.012 INFO 24144 --- [ main]
org.apache.camel.main.MainSupport : Using Java 17.0.7 with PID 24144. Started
by in
2023-08-07 15:52:43.036 INFO 24144 --- [ main]
mel.cli.connector.LocalCliConnector : Camel CLI enabled (local)
2023-08-07 15:52:45.390 INFO 24144 --- [ main]
.download.MavenDependencyDownloader : Downloaded:
org.apache.camel:camel-activemq:3.20.3 (took: 1s501ms)
2023-08-07 15:52:45.596 INFO 24144 --- [ main]
el.impl.engine.AbstractCamelContext : Apache Camel 3.20.3 (test) is starting
2023-08-07 15:52:45.892 INFO 24144 --- [ main]
.core.spi.resolver.ResolverProvider : Using the default address resolver as the
dns resolver could not be loaded
2023-08-07 15:52:46.222 INFO 24144 --- [ActiveMQ Task-1]
ransport.failover.FailoverTransport : Successfully connected to
tcp://localhost:61616
2023-08-07 15:52:46.287 INFO 24144 --- [ main]
el.impl.engine.AbstractCamelContext : Routes startup (started:1)
2023-08-07 15:52:46.288 INFO 24144 --- [ main]
el.impl.engine.AbstractCamelContext : Started route-4ec8
(activemq://)
2023-08-07 15:52:46.289 INFO 24144 --- [ main]
el.impl.engine.AbstractCamelContext : Apache Camel 3.20.3 (test) started in
985ms (build:105ms init:189ms start:691ms JVM-uptime:4s)
2023-08-07 15:52:58.955 WARN 24144 --- [ntloop-thread-1]
ssor.errorhandler.DeadLetterChannel : Failed delivery for (MessageId:
1D22091EB3FABD1- on ExchangeId:
1D22091EB3FABD1-). On delivery
[jira] [Updated] (CAMEL-19626) camel-google - Upgrade from 1.32.x to 2.x
[ https://issues.apache.org/jira/browse/CAMEL-19626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19626: Fix Version/s: 4.0.0 > camel-google - Upgrade from 1.32.x to 2.x > - > > Key: CAMEL-19626 > URL: https://issues.apache.org/jira/browse/CAMEL-19626 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-google >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.0.0 > > > The API based components in camel-google (drive, sheets, calendar, etc.) are > in need of updating to latest versions from Google. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-19626) camel-google - Upgrade from 1.32.x to 2.x
[ https://issues.apache.org/jira/browse/CAMEL-19626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-19626: --- Assignee: Claus Ibsen > camel-google - Upgrade from 1.32.x to 2.x > - > > Key: CAMEL-19626 > URL: https://issues.apache.org/jira/browse/CAMEL-19626 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-google >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > > The API based components in camel-google (drive, sheets, calendar, etc.) are > in need of updating to latest versions from Google. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19703) [yaml dsl] remove kebab-case schema definition
[ https://issues.apache.org/jira/browse/CAMEL-19703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aurélien Pupier updated CAMEL-19703: Attachment: chooseVersionOfYamlSchema.mp4 > [yaml dsl] remove kebab-case schema definition > -- > > Key: CAMEL-19703 > URL: https://issues.apache.org/jira/browse/CAMEL-19703 > Project: Camel > Issue Type: Task > Components: camel-yaml-dsl >Reporter: Luca Burgazzoli >Priority: Minor > Fix For: 4.0.0 > > Attachments: chooseVersionOfYamlSchema.mp4 > > > As today there are two schema for the YAML dsl: > - one that uses camelCase > - one that uses kebab-case > since the kebab-case is a leftover from an initial version and was meant to > be removed, we can take finally remove it now that we are moving to a new > major release. > once removed we also need to update the [schemastore > repository|https://github.com/SchemaStore/schemastore/blob/14f6880f5e6520beb1889f404589008fda1bd09f/src/api/json/catalog.json#L745-L750] > to point to the right schema -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19703) [yaml dsl] remove kebab-case schema definition
[ https://issues.apache.org/jira/browse/CAMEL-19703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751690#comment-17751690 ] Aurélien Pupier commented on CAMEL-19703: - VS Code support it, there is a specific command, which is also available through UI to select in the list of defined versions: [^chooseVersionOfYamlSchema.mp4] > [yaml dsl] remove kebab-case schema definition > -- > > Key: CAMEL-19703 > URL: https://issues.apache.org/jira/browse/CAMEL-19703 > Project: Camel > Issue Type: Task > Components: camel-yaml-dsl >Reporter: Luca Burgazzoli >Priority: Minor > Fix For: 4.0.0 > > Attachments: chooseVersionOfYamlSchema.mp4 > > > As today there are two schema for the YAML dsl: > - one that uses camelCase > - one that uses kebab-case > since the kebab-case is a leftover from an initial version and was meant to > be removed, we can take finally remove it now that we are moving to a new > major release. > once removed we also need to update the [schemastore > repository|https://github.com/SchemaStore/schemastore/blob/14f6880f5e6520beb1889f404589008fda1bd09f/src/api/json/catalog.json#L745-L750] > to point to the right schema -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19647) camel-platform-http-main - Use 503 for health check DOWN
[ https://issues.apache.org/jira/browse/CAMEL-19647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otavio Rodolfo Piske resolved CAMEL-19647. -- Resolution: Fixed Resolved with the linked PRs. > camel-platform-http-main - Use 503 for health check DOWN > > > Key: CAMEL-19647 > URL: https://issues.apache.org/jira/browse/CAMEL-19647 > Project: Camel > Issue Type: Improvement >Affects Versions: 4.0-RC2 >Reporter: Claus Ibsen >Assignee: Otavio Rodolfo Piske >Priority: Minor > Labels: easy > Fix For: 4.0.0 > > > SB uses 503 instead of 500 for health check failed. Lets do the same for > camel-main -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19618) camel-box - Upgrade to v4
[ https://issues.apache.org/jira/browse/CAMEL-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-19618: Fix Version/s: 4.0.0 > camel-box - Upgrade to v4 > - > > Key: CAMEL-19618 > URL: https://issues.apache.org/jira/browse/CAMEL-19618 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-box >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 4.0.0 > > > We use an older v2 java-sdk and should upgrade to v4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-19618) camel-box - Upgrade to v4
[ https://issues.apache.org/jira/browse/CAMEL-19618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-19618: --- Assignee: Claus Ibsen > camel-box - Upgrade to v4 > - > > Key: CAMEL-19618 > URL: https://issues.apache.org/jira/browse/CAMEL-19618 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-box >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > > We use an older v2 java-sdk and should upgrade to v4 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-19718) camel-util-json should allow to configure escape forward slashes or not
[
https://issues.apache.org/jira/browse/CAMEL-19718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luca Burgazzoli updated CAMEL-19718:
Summary: camel-util-json should allow to configure escape forward slashes
or not (was: camel-util-json should not escape slashes in strings)
> camel-util-json should allow to configure escape forward slashes or not
> ---
>
> Key: CAMEL-19718
> URL: https://issues.apache.org/jira/browse/CAMEL-19718
> Project: Camel
> Issue Type: Improvement
> Components: tooling
>Reporter: Luca Burgazzoli
>Priority: Minor
> Fix For: 4.1.0
>
>
> Wile exploring
> [CAMEL-19717|https://issues.apache.org/jira/browse/CAMEL-19717], I noticed
> that camel-util-json escapes i.e. slashes:
>
> {code:json}
> "beans": {
> "$ref":
> "#\/items\/definitions\/org.apache.camel.dsl.yaml.deserializers.BeansDeserializer"
> },
> {code}
> This is not required in json-schema and would be nice to have a way to
> configure JSooner to disable such behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-19649) apache-camel - Source tarball should have apache-camel as name
[ https://issues.apache.org/jira/browse/CAMEL-19649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751665#comment-17751665 ] Claus Ibsen commented on CAMEL-19649: - The duplicated camel-4.0.0-source-release.zip in https://repo.maven.apache.org/maven2/org/apache/camel/camel/4.0.0-RC2/ Will no longer be build and published. This will only the the root pom.xml that are published there. The source zip is in https://repo.maven.apache.org/maven2/org/apache/camel/apache-camel/4.0.0 > apache-camel - Source tarball should have apache-camel as name > -- > > Key: CAMEL-19649 > URL: https://issues.apache.org/jira/browse/CAMEL-19649 > Project: Camel > Issue Type: Task > Components: build system >Affects Versions: 4.0-RC2 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0.0 > > > I created the RC2 release and the tarballs got created, but they are > now located at a different path: > https://repository.apache.org/content/repositories/orgapachecamel-1594/org/apache/camel/camel/4.0.0-RC2/ > With previous releases, they used to be located at: > https://repository.apache.org/content/repositories/orgapachecamel-1594/org/apache/camel/apache-camel/4.0.0-RC2/ > (Note the path element `camel/camel` vs `camel/apache-camel`). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19703) [yaml dsl] remove kebab-case schema definition
[ https://issues.apache.org/jira/browse/CAMEL-19703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751664#comment-17751664 ] Luca Burgazzoli commented on CAMEL-19703: - [~aurelien.pupier] do you know how/if vscode support this ? it would be nice if by default vscode would pick the main url but the user had the chance to switch to another version if working with an older version of camel > [yaml dsl] remove kebab-case schema definition > -- > > Key: CAMEL-19703 > URL: https://issues.apache.org/jira/browse/CAMEL-19703 > Project: Camel > Issue Type: Task > Components: camel-yaml-dsl >Reporter: Luca Burgazzoli >Priority: Minor > Fix For: 4.0.0 > > > As today there are two schema for the YAML dsl: > - one that uses camelCase > - one that uses kebab-case > since the kebab-case is a leftover from an initial version and was meant to > be removed, we can take finally remove it now that we are moving to a new > major release. > once removed we also need to update the [schemastore > repository|https://github.com/SchemaStore/schemastore/blob/14f6880f5e6520beb1889f404589008fda1bd09f/src/api/json/catalog.json#L745-L750] > to point to the right schema -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19649) apache-camel - Source tarball should have apache-camel as name
[ https://issues.apache.org/jira/browse/CAMEL-19649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751663#comment-17751663 ] Claus Ibsen commented on CAMEL-19649: - https://github.com/apache/camel/commit/7225d7932e50358116ba9648d530ea69ed9b261a > apache-camel - Source tarball should have apache-camel as name > -- > > Key: CAMEL-19649 > URL: https://issues.apache.org/jira/browse/CAMEL-19649 > Project: Camel > Issue Type: Task > Components: build system >Affects Versions: 4.0-RC2 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0.0 > > > I created the RC2 release and the tarballs got created, but they are > now located at a different path: > https://repository.apache.org/content/repositories/orgapachecamel-1594/org/apache/camel/camel/4.0.0-RC2/ > With previous releases, they used to be located at: > https://repository.apache.org/content/repositories/orgapachecamel-1594/org/apache/camel/apache-camel/4.0.0-RC2/ > (Note the path element `camel/camel` vs `camel/apache-camel`). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19649) apache-camel - Source tarball should have apache-camel as name
[ https://issues.apache.org/jira/browse/CAMEL-19649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-19649. - Resolution: Fixed > apache-camel - Source tarball should have apache-camel as name > -- > > Key: CAMEL-19649 > URL: https://issues.apache.org/jira/browse/CAMEL-19649 > Project: Camel > Issue Type: Task > Components: build system >Affects Versions: 4.0-RC2 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0.0 > > > I created the RC2 release and the tarballs got created, but they are > now located at a different path: > https://repository.apache.org/content/repositories/orgapachecamel-1594/org/apache/camel/camel/4.0.0-RC2/ > With previous releases, they used to be located at: > https://repository.apache.org/content/repositories/orgapachecamel-1594/org/apache/camel/apache-camel/4.0.0-RC2/ > (Note the path element `camel/camel` vs `camel/apache-camel`). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-19717) [yaml dsl] replace jackson with camel-util-json for json schema generation
[ https://issues.apache.org/jira/browse/CAMEL-19717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Luca Burgazzoli reassigned CAMEL-19717: --- Assignee: Luca Burgazzoli > [yaml dsl] replace jackson with camel-util-json for json schema generation > -- > > Key: CAMEL-19717 > URL: https://issues.apache.org/jira/browse/CAMEL-19717 > Project: Camel > Issue Type: Improvement > Components: camel-yaml-dsl >Reporter: Luca Burgazzoli >Assignee: Luca Burgazzoli >Priority: Minor > Fix For: 4.1.0 > > > as today, the yaml dsl Json schema generation leverages Jackson, however for > consistency with json code generation in Camel, it would be nice to re-write > the schema generation on top of camel-util-json -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19649) apache-camel - Source tarball should have apache-camel as name
[ https://issues.apache.org/jira/browse/CAMEL-19649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751645#comment-17751645 ] Claus Ibsen commented on CAMEL-19649: - I was able to do a dryRun with some fixes (PR coming) ./mvnw release:prepare -DdryRun -Prelease [INFO] 17/17 prepare:end-release dry-run [INFO] Release preparation simulation complete. > apache-camel - Source tarball should have apache-camel as name > -- > > Key: CAMEL-19649 > URL: https://issues.apache.org/jira/browse/CAMEL-19649 > Project: Camel > Issue Type: Task > Components: build system >Affects Versions: 4.0-RC2 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0.0 > > > I created the RC2 release and the tarballs got created, but they are > now located at a different path: > https://repository.apache.org/content/repositories/orgapachecamel-1594/org/apache/camel/camel/4.0.0-RC2/ > With previous releases, they used to be located at: > https://repository.apache.org/content/repositories/orgapachecamel-1594/org/apache/camel/apache-camel/4.0.0-RC2/ > (Note the path element `camel/camel` vs `camel/apache-camel`). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CAMEL-19699) camel-yaml-dsl: schema: Express languages/dataformats are mutually exclusive
[
https://issues.apache.org/jira/browse/CAMEL-19699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomohisa Igarashi reassigned CAMEL-19699:
-
Assignee: Tomohisa Igarashi (was: Luca Burgazzoli)
> camel-yaml-dsl: schema: Express languages/dataformats are mutually exclusive
> -
>
> Key: CAMEL-19699
> URL: https://issues.apache.org/jira/browse/CAMEL-19699
> Project: Camel
> Issue Type: Task
> Components: camel-yaml-dsl
>Reporter: Tomohisa Igarashi
>Assignee: Tomohisa Igarashi
>Priority: Major
>
> For example with dataformats, this is syntactically allowed
> {code:yaml}
> - from:
> uri: "timer:test"
> parameters:
> period: 3000
> steps:
> - set-body:
> simple: "Hello World"
> - marshal:
> json:
> library: Jackson
> jaxb:
> contextPath: org.apache.camel.model
> - to:
> uri: "log:test"
> {code}
> Can we prohibit this through YAML DSL schema, possibly with `oneOf`?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-19698) camel-yaml-dsl: Express "simple" and "expression.simple" are mutually exclusive if possible
[
https://issues.apache.org/jira/browse/CAMEL-19698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomohisa Igarashi reassigned CAMEL-19698:
-
Assignee: Tomohisa Igarashi (was: Luca Burgazzoli)
> camel-yaml-dsl: Express "simple" and "expression.simple" are mutually
> exclusive if possible
>
>
> Key: CAMEL-19698
> URL: https://issues.apache.org/jira/browse/CAMEL-19698
> Project: Camel
> Issue Type: Task
> Components: camel-yaml-dsl
>Reporter: Tomohisa Igarashi
>Assignee: Tomohisa Igarashi
>Priority: Major
>
> For example currently YAML DSL allows specifying both "simple" and
> "expression" under "when"
> {code:yaml}
> - from:
> uri: "timer:test"
> parameters:
> period: 3000
> steps:
> - when:
> simple: "${header.baz} != null"
> expression:
> simple: "${header.baz} == null"
> steps:
> - log: "test"
> {code}
> But at runtime only latter wins in this case. It would be nice if this
> exclusiveness could be expressed in the schema.
> Similarly, this "anyOf" seems to allow specifying multiple expressions
> https://github.com/apache/camel/blob/36bcd6277854b8e69ca91a8d51845a306b1c2136/dsl/camel-yaml-dsl/camel-yaml-dsl/src/generated/resources/schema/camel-yaml-dsl.json#L3567-L3569
> for example
> {code:yaml}
> - from:
> uri: "timer:test"
> parameters:
> period: 3000
> steps:
> - when:
> simple: ${header.baz} != null
> jq: ".foo"
> steps:
> - log: "test"
> {code}
> Although this ends up with a runtime error
> {noformat}
> 2023-08-02 14:27:29.445 INFO 1579388 --- [ main]
> org.apache.camel.main.MainSupport : Using Java 20.0.1 with PID 1579388.
> Started by tomo in /home/tomo/workspace/Kaoto/datamapper-research/examples
> Field: jq has already been configured as an expression
> in file:test.yaml, line 8, column 13:
> jq: ".foo"
> ^
> at
> org.apache.camel.dsl.yaml.deserializers.ModelDeserializers$WhenDefinitionDeserializer.setProperty(ModelDeserializers.java:18445)
> at
> org.apache.camel.dsl.yaml.deserializers.ModelDeserializers$WhenDefinitionDeserializer.setProperty(ModelDeserializers.java:18385)
> at
> org.apache.camel.dsl.yaml.common.YamlDeserializerBase.setProperties(YamlDeserializerBase.java:125)
> at
> org.apache.camel.dsl.yaml.common.YamlDeserializerBase.construct(YamlDeserializerBase.java:65)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-19718) camel-util-json should not escape slashes in strings
Luca Burgazzoli created CAMEL-19718:
---
Summary: camel-util-json should not escape slashes in strings
Key: CAMEL-19718
URL: https://issues.apache.org/jira/browse/CAMEL-19718
Project: Camel
Issue Type: Improvement
Components: tooling
Reporter: Luca Burgazzoli
Fix For: 4.1.0
Wile exploring [CAMEL-19717|https://issues.apache.org/jira/browse/CAMEL-19717],
I noticed that camel-util-json escapes i.e. slashes:
{code:json}
"beans": {
"$ref":
"#\/items\/definitions\/org.apache.camel.dsl.yaml.deserializers.BeansDeserializer"
},
{code}
This is not required in json-schema and would be nice to have a way to
configure JSooner to disable such behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CAMEL-19649) apache-camel - Source tarball should have apache-camel as name
[ https://issues.apache.org/jira/browse/CAMEL-19649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-19649: --- Assignee: Claus Ibsen > apache-camel - Source tarball should have apache-camel as name > -- > > Key: CAMEL-19649 > URL: https://issues.apache.org/jira/browse/CAMEL-19649 > Project: Camel > Issue Type: Task > Components: build system >Affects Versions: 4.0-RC2 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 4.0.0 > > > I created the RC2 release and the tarballs got created, but they are > now located at a different path: > https://repository.apache.org/content/repositories/orgapachecamel-1594/org/apache/camel/camel/4.0.0-RC2/ > With previous releases, they used to be located at: > https://repository.apache.org/content/repositories/orgapachecamel-1594/org/apache/camel/apache-camel/4.0.0-RC2/ > (Note the path element `camel/camel` vs `camel/apache-camel`). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-19649) apache-camel - Source tarball should have apache-camel as name
[ https://issues.apache.org/jira/browse/CAMEL-19649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17751582#comment-17751582 ] Claus Ibsen commented on CAMEL-19649: - So apache-camel builds the source assembly which we use for downloads. And it looks like the (1st link above) is wrong - we have duplicated source tarball. > apache-camel - Source tarball should have apache-camel as name > -- > > Key: CAMEL-19649 > URL: https://issues.apache.org/jira/browse/CAMEL-19649 > Project: Camel > Issue Type: Task > Components: build system >Affects Versions: 4.0-RC2 >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0.0 > > > I created the RC2 release and the tarballs got created, but they are > now located at a different path: > https://repository.apache.org/content/repositories/orgapachecamel-1594/org/apache/camel/camel/4.0.0-RC2/ > With previous releases, they used to be located at: > https://repository.apache.org/content/repositories/orgapachecamel-1594/org/apache/camel/apache-camel/4.0.0-RC2/ > (Note the path element `camel/camel` vs `camel/apache-camel`). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-19717) [yaml dsl] replace jackson with camel-util-json for json schema generation
Luca Burgazzoli created CAMEL-19717: --- Summary: [yaml dsl] replace jackson with camel-util-json for json schema generation Key: CAMEL-19717 URL: https://issues.apache.org/jira/browse/CAMEL-19717 Project: Camel Issue Type: Improvement Components: camel-yaml-dsl Reporter: Luca Burgazzoli Fix For: 4.1.0 as today, the yaml dsl Json schema generation leverages Jackson, however for consistency with json code generation in Camel, it would be nice to re-write the schema generation on top of camel-util-json -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18747) camel-test-infra: investigate upgrading Hadoop images to 3.x
[ https://issues.apache.org/jira/browse/CAMEL-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18747: Fix Version/s: 4.0.0 (was: 4.1.0) > camel-test-infra: investigate upgrading Hadoop images to 3.x > > > Key: CAMEL-18747 > URL: https://issues.apache.org/jira/browse/CAMEL-18747 > Project: Camel > Issue Type: Improvement > Components: camel-test-infra-hadoop >Affects Versions: 3.20.0 >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Minor > Fix For: 4.0.0 > > > We are currently using 2.10.x and we should investigate upgrading Hadoop > images to 3.x as the code should be compatible with that version. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-12317) Provide integration with AWS Step Functions
[ https://issues.apache.org/jira/browse/CAMEL-12317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-12317: Fix Version/s: 4.1.0 (was: Future) > Provide integration with AWS Step Functions > --- > > Key: CAMEL-12317 > URL: https://issues.apache.org/jira/browse/CAMEL-12317 > Project: Camel > Issue Type: New Feature > Components: camel-aws >Reporter: Christian Müller >Assignee: Andrea Cosentino >Priority: Major > Fix For: 4.1.0 > > > Provide integration with AWS Step Functions: > [https://aws.amazon.com/step-functions/] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-19498) camel-core / camel-ftp - memory leak in MultiplePool when using pollEnrich EIP
[
https://issues.apache.org/jira/browse/CAMEL-19498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-19498.
-
Resolution: Fixed
Thanks for reporting and the small example, I was able to reproduce
> camel-core / camel-ftp - memory leak in MultiplePool when using pollEnrich EIP
> --
>
> Key: CAMEL-19498
> URL: https://issues.apache.org/jira/browse/CAMEL-19498
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.14.0
>Reporter: https://github.com/apache/camel.git
>Assignee: Claus Ibsen
>Priority: Major
> Fix For: 3.14.10, 3.20.7, 3.21.1, 3.22.0, 4.0.0
>
>
> MultiplePool does not free memory of field
> org.apache.camel.support.cache.ServicePool.pool
> {code:java}
>
>
>
>
> sftp:camel@127.0.0.1:22/data?password=camelallowNullBody=truefileName=data-${exchangeProperty.CamelTimerCounter}.csvpreferredAuthentications=password,publickeyuseUserKnownHostsFile=false
>
>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
