[jira] [Created] (CAMEL-18822) camel-kafka- KafkaConsumerAuthIT fails often on CI
Claus Ibsen created CAMEL-18822: --- Summary: camel-kafka- KafkaConsumerAuthIT fails often on CI Key: CAMEL-18822 URL: https://issues.apache.org/jira/browse/CAMEL-18822 Project: Camel Issue Type: Test Components: camel-kafka Affects Versions: 3.20.0 Reporter: Claus Ibsen Fix For: 3.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18816) camel-ahc component crashes when a traffic starts too early
[
https://issues.apache.org/jira/browse/CAMEL-18816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18816.
-
Resolution: Fixed
Thanks for the patch
> camel-ahc component crashes when a traffic starts too early
> ---
>
> Key: CAMEL-18816
> URL: https://issues.apache.org/jira/browse/CAMEL-18816
> Project: Camel
> Issue Type: Bug
> Components: camel-ahc
>Affects Versions: 3.18.4
>Reporter: Krzysztof Mackowiak
>Priority: Minor
> Fix For: 3.18.5
>
> Attachments: camel-ahc-bug.patch
>
>
> Unfortunately it looks that when traffic to camel-ahc component starts to
> early it crashes with an exception:
> {code:java}
> org.apache.camel.FailedToCreateProducerException: Failed to create Producer
> for endpoint: ahc://http://localhost:59729/foo.
> Reason: java.lang.IllegalArgumentException: AsyncHttpClient must be specified
> on: ahc://http://localhost:59729/foo
>at
> org.apache.camel.support.cache.DefaultProducerCache.acquireProducer(DefaultProducerCache.java:164)
>at
> org.apache.camel.processor.RecipientListProcessor.doCreateProcessorExchangePairs(RecipientListProcessor.java:270)
>at
> org.apache.camel.processor.RecipientListProcessor.createProcessorExchangePairs(RecipientListProcessor.java:246)
>at
> org.apache.camel.processor.MulticastProcessor.process(MulticastProcessor.java:295)
>at org.apache.camel.processor.RecipientList.process(RecipientList.java:175)
>at org.apache.camel.processor.Pipeline$PipelineTask.run(Pipeline.java:106)
>at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:189)
>at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:61)
>at org.apache.camel.processor.Pipeline.process(Pipeline.java:182)
>at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:399)
>at
> org.apache.camel.component.timer.TimerConsumer.sendTimerExchange(TimerConsumer.java:210)
>at
> org.apache.camel.component.timer.TimerConsumer$2.run(TimerConsumer.java:118)
>at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: java.lang.IllegalArgumentException: AsyncHttpClient must be
> specified on: ahc://http://localhost:59729/foo
>at org.apache.camel.util.ObjectHelper.notNull(ObjectHelper.java:176)
>at
> org.apache.camel.component.ahc.AhcEndpoint.createProducer(AhcEndpoint.java:94)
>at
> org.apache.camel.support.DefaultEndpoint.createAsyncProducer(DefaultEndpoint.java:200)
>at
> org.apache.camel.support.cache.ServicePool$SinglePool.acquire(ServicePool.java:237)
>at
> org.apache.camel.support.cache.ServicePool$SinglePool.acquire(ServicePool.java:216)
>at org.apache.camel.support.cache.ServicePool.acquire(ServicePool.java:112)
>at
> org.apache.camel.support.cache.ProducerServicePool.acquire(ProducerServicePool.java:28)
>at
> org.apache.camel.support.cache.DefaultProducerCache.acquireProducer(DefaultProducerCache.java:149)
>... 14 common frames omitted
> {code}
> It causes that all traffic to camel-ahc endpoint is failing. It happens in my
> application for routes that take messages from JMS queue and sent it to HTTP
> (using camel-ahc component).
> Here is a test that reproduces a problem:
> {code:java}
> public class AhcRecipientListTest extends BaseAhcTest {
> @Test
> public void testRecipientListCalledBeforeComponentStarted() throws
> Exception {
> getMockEndpoint("mock:result").expectedBodiesReceived("Hello");
> assertMockEndpointsSatisfied();
> }
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> from("timer://foo?delay=-1&?repeatCount=1")
> .recipientList(constant(getAhcEndpointUri()))
> .to("mock:result");
> from(getTestServerEndpointUri())
> .transform(constant("Hello"));
> }
> };
> }
> } {code}
> I've prepared a patch with another 2 tests and a possible bugfix. The bugfix
> is based on a solution from HttpEnpoint/HttpProducer.
> The bug was discovered in version 3.18.4, but it looks that it was present
> for a long time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18820) Infinite recursion with direct endpoint
[
https://issues.apache.org/jira/browse/CAMEL-18820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17648169#comment-17648169
]
Claus Ibsen edited comment on CAMEL-18820 at 12/15/22 5:25 PM:
---
Its like in java if you call your own method recursively, and yes end users can
write camel routes using choice / when that would route elsewhere etc.
was (Author: davsclaus):
Its like in java if you call your own method recursively
> Infinite recursion with direct endpoint
> ---
>
> Key: CAMEL-18820
> URL: https://issues.apache.org/jira/browse/CAMEL-18820
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.19.0
>Reporter: Marco Bergsma
>Priority: Minor
>
> Creating routes like this produces an infinite loop.
> {code:java}
> from(timer("test").repeatCount(1))
> .routeId("test")
> .to(direct("testing"));
> from(direct("testing"))
> .routeId("test-2")
> .log("Hey I am testing")
> .to(direct("testing")); {code}
> Is this something that don't want to allow or do we rely on users creating
> some stop condition?
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18821) camel-core - Thread hangs on transacted routes after aggregation and multiplex (possibly more)
[
https://issues.apache.org/jira/browse/CAMEL-18821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18821:
Fix Version/s: 3.x
> camel-core - Thread hangs on transacted routes after aggregation and
> multiplex (possibly more)
> --
>
> Key: CAMEL-18821
> URL: https://issues.apache.org/jira/browse/CAMEL-18821
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Environment: Quarkus 3.18.3, 3.18.4, 3.19.0 in TomEE 8.0.13 on JDK 17
> (Termium).
>Reporter: Christian Kalkhoff
>Priority: Major
> Fix For: 3.x
>
>
> When an aggregator runs in the same thread as the transacted route (Using
> org.apache.camel.util.concurrent.SynchronousExecutorService for
> executorService), the thread hands after completion (error or not) at
> camel-base-engine-3.19.0-sources.jar!/org/apache/camel/impl/engine/DefaultAsyncProcessorAwaitManager.java:107
>
> {code:java}
> latch.await(); {code}
>
> If I run latch.countDown() in a debugger, the thread continues just fine.
> For the success case I found the workaround to set
> {{{}jtaTransactionErrorHandler(){}}}for the route containing the aggregator.
> Still in case of an exception thrown from the code processing the aggregated
> messages, the thread hangs.
> See
> [https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/Deadlock.20in.20transacted.20route.2E.20is.20this.20a.20bug.3F]
> for the discussion on this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18820) Infinite recursion with direct endpoint
[
https://issues.apache.org/jira/browse/CAMEL-18820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18820.
-
Resolution: Not A Bug
Its like in java if you call your own method recursively
> Infinite recursion with direct endpoint
> ---
>
> Key: CAMEL-18820
> URL: https://issues.apache.org/jira/browse/CAMEL-18820
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.19.0
>Reporter: Marco Bergsma
>Priority: Minor
>
> Creating routes like this produces an infinite loop.
> {code:java}
> from(timer("test").repeatCount(1))
> .routeId("test")
> .to(direct("testing"));
> from(direct("testing"))
> .routeId("test-2")
> .log("Hey I am testing")
> .to(direct("testing")); {code}
> Is this something that don't want to allow or do we rely on users creating
> some stop condition?
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18821) camel-core - Thread hangs on transacted routes after aggregation and multiplex (possibly more)
Christian Kalkhoff created CAMEL-18821:
--
Summary: camel-core - Thread hangs on transacted routes after
aggregation and multiplex (possibly more)
Key: CAMEL-18821
URL: https://issues.apache.org/jira/browse/CAMEL-18821
Project: Camel
Issue Type: Bug
Components: camel-core
Environment: Quarkus 3.18.3, 3.18.4, 3.19.0 in TomEE 8.0.13 on JDK 17
(Termium).
Reporter: Christian Kalkhoff
When an aggregator runs in the same thread as the transacted route (Using
org.apache.camel.util.concurrent.SynchronousExecutorService for
executorService), the thread hands after completion (error or not) at
camel-base-engine-3.19.0-sources.jar!/org/apache/camel/impl/engine/DefaultAsyncProcessorAwaitManager.java:107
{code:java}
latch.await(); {code}
If I run latch.countDown() in a debugger, the thread continues just fine.
For the success case I found the workaround to set
{{{}jtaTransactionErrorHandler(){}}}for the route containing the aggregator.
Still in case of an exception thrown from the code processing the aggregated
messages, the thread hangs.
See
[https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/Deadlock.20in.20transacted.20route.2E.20is.20this.20a.20bug.3F]
for the discussion on this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18820) Infinite recursion with direct endpoint
[
https://issues.apache.org/jira/browse/CAMEL-18820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Bergsma updated CAMEL-18820:
--
Description:
Creating routes like this produces an infinite loop.
{code:java}
from(timer("test").repeatCount(1))
.routeId("test")
.to(direct("testing"));
from(direct("testing"))
.routeId("test-2")
.log("Hey I am testing")
.to(direct("testing")); {code}
Is this something that don't want to allow or do we rely on users creating some
stop condition?
was:
Creating routes like this produces an infinite loop.
{code:java}
from(timer("test").repeatCount(1))
.routeId("test")
.to(direct("testing"));
from(direct("testing"))
.routeId("test-2")
.log("Hey I am testing")
.to(direct("testing")); {code}
Is this something that we wouldn't want to allow or do we rely on users
creating some stop condition?
> Infinite recursion with direct endpoint
> ---
>
> Key: CAMEL-18820
> URL: https://issues.apache.org/jira/browse/CAMEL-18820
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.19.0
>Reporter: Marco Bergsma
>Priority: Minor
>
> Creating routes like this produces an infinite loop.
> {code:java}
> from(timer("test").repeatCount(1))
> .routeId("test")
> .to(direct("testing"));
> from(direct("testing"))
> .routeId("test-2")
> .log("Hey I am testing")
> .to(direct("testing")); {code}
> Is this something that don't want to allow or do we rely on users creating
> some stop condition?
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18820) Infinite recursion with direct endpoint
[
https://issues.apache.org/jira/browse/CAMEL-18820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Bergsma updated CAMEL-18820:
--
Summary: Infinite recursion with direct endpoint (was: Infinite recursion
when using direct endpoint)
> Infinite recursion with direct endpoint
> ---
>
> Key: CAMEL-18820
> URL: https://issues.apache.org/jira/browse/CAMEL-18820
> Project: Camel
> Issue Type: Bug
> Components: came-core
>Affects Versions: 3.19.0
>Reporter: Marco Bergsma
>Priority: Minor
>
> Creating routes like this produces an infinite loop.
> {code:java}
> from(timer("test").repeatCount(1))
> .routeId("test")
> .to(direct("testing"));
> from(direct("testing"))
> .routeId("test-2")
> .log("Hey I am testing")
> .to(direct("testing")); {code}
> Is this something that we wouldn't want to allow or do we rely on users
> creating some stop condition?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18820) Infinite recursion when using direct endpoint
Marco Bergsma created CAMEL-18820:
-
Summary: Infinite recursion when using direct endpoint
Key: CAMEL-18820
URL: https://issues.apache.org/jira/browse/CAMEL-18820
Project: Camel
Issue Type: Bug
Components: came-core
Affects Versions: 3.19.0
Reporter: Marco Bergsma
Creating routes like this produces an infinite loop.
{code:java}
from(timer("test").repeatCount(1))
.routeId("test")
.to(direct("testing"));
from(direct("testing"))
.routeId("test-2")
.log("Hey I am testing")
.to(direct("testing")); {code}
Is this something that we wouldn't want to allow or do we rely on users
creating some stop condition?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18819) hbase: different version of audience-annotations brought by zookeeper
[ https://issues.apache.org/jira/browse/CAMEL-18819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18819. - Resolution: Fixed Excluded from hbase-test-infra also as it comes there too https://github.com/apache/camel/commit/b8460586fa75b6ed4b5812aa25e17f636ebf7ed9 > hbase: different version of audience-annotations brought by zookeeper > -- > > Key: CAMEL-18819 > URL: https://issues.apache.org/jira/browse/CAMEL-18819 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-hbase >Affects Versions: 3.20.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.20.0 > > > Dependency `audience-annotations` has version 0.13.0. > Zookeper brings version 0.5.0. It should be excluded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18819) hbase: different version of audience-annotations brought by zookeeper
[ https://issues.apache.org/jira/browse/CAMEL-18819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17648028#comment-17648028 ] Jiri Ondrusek commented on CAMEL-18819: --- Sure, pr: https://github.com/apache/camel/pull/8908 > hbase: different version of audience-annotations brought by zookeeper > -- > > Key: CAMEL-18819 > URL: https://issues.apache.org/jira/browse/CAMEL-18819 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-hbase >Affects Versions: 3.20.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.20.0 > > > Dependency `audience-annotations` has version 0.13.0. > Zookeper brings version 0.5.0. It should be excluded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18819) hbase: different version of audience-annotations brought by zookeeper
[ https://issues.apache.org/jira/browse/CAMEL-18819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17648014#comment-17648014 ] Claus Ibsen commented on CAMEL-18819: - Jiri can you send PR today as we want to build the release tomorrow > hbase: different version of audience-annotations brought by zookeeper > -- > > Key: CAMEL-18819 > URL: https://issues.apache.org/jira/browse/CAMEL-18819 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-hbase >Affects Versions: 3.20.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.20.0 > > > Dependency `audience-annotations` has version 0.13.0. > Zookeper brings version 0.5.0. It should be excluded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18819) hbase: different version of audience-annotations brought by zookeeper
[ https://issues.apache.org/jira/browse/CAMEL-18819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18819: Fix Version/s: 3.20.0 > hbase: different version of audience-annotations brought by zookeeper > -- > > Key: CAMEL-18819 > URL: https://issues.apache.org/jira/browse/CAMEL-18819 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-hbase >Affects Versions: 3.20.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > Fix For: 3.20.0 > > > Dependency `audience-annotations` has version 0.13.0. > Zookeper brings version 0.5.0. It should be excluded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18819) hbase: different version of audience-annotations brought by zookeeper
[ https://issues.apache.org/jira/browse/CAMEL-18819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18819: Issue Type: Dependency upgrade (was: Bug) > hbase: different version of audience-annotations brought by zookeeper > -- > > Key: CAMEL-18819 > URL: https://issues.apache.org/jira/browse/CAMEL-18819 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-hbase >Affects Versions: 3.20.0 >Reporter: Jiri Ondrusek >Assignee: Jiri Ondrusek >Priority: Major > > Dependency `audience-annotations` has version 0.13.0. > Zookeper brings version 0.5.0. It should be excluded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18816) camel-ahc component crashes when a traffic starts too early
[
https://issues.apache.org/jira/browse/CAMEL-18816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17648002#comment-17648002
]
Krzysztof Mackowiak commented on CAMEL-18816:
-
Of course. I've send it as a PR [https://github.com/apache/camel/pull/8907]
> camel-ahc component crashes when a traffic starts too early
> ---
>
> Key: CAMEL-18816
> URL: https://issues.apache.org/jira/browse/CAMEL-18816
> Project: Camel
> Issue Type: Bug
> Components: camel-ahc
>Affects Versions: 3.18.4
>Reporter: Krzysztof Mackowiak
>Priority: Minor
> Fix For: 3.18.5
>
> Attachments: camel-ahc-bug.patch
>
>
> Unfortunately it looks that when traffic to camel-ahc component starts to
> early it crashes with an exception:
> {code:java}
> org.apache.camel.FailedToCreateProducerException: Failed to create Producer
> for endpoint: ahc://http://localhost:59729/foo.
> Reason: java.lang.IllegalArgumentException: AsyncHttpClient must be specified
> on: ahc://http://localhost:59729/foo
>at
> org.apache.camel.support.cache.DefaultProducerCache.acquireProducer(DefaultProducerCache.java:164)
>at
> org.apache.camel.processor.RecipientListProcessor.doCreateProcessorExchangePairs(RecipientListProcessor.java:270)
>at
> org.apache.camel.processor.RecipientListProcessor.createProcessorExchangePairs(RecipientListProcessor.java:246)
>at
> org.apache.camel.processor.MulticastProcessor.process(MulticastProcessor.java:295)
>at org.apache.camel.processor.RecipientList.process(RecipientList.java:175)
>at org.apache.camel.processor.Pipeline$PipelineTask.run(Pipeline.java:106)
>at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:189)
>at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:61)
>at org.apache.camel.processor.Pipeline.process(Pipeline.java:182)
>at
> org.apache.camel.impl.engine.CamelInternalProcessor.process(CamelInternalProcessor.java:399)
>at
> org.apache.camel.component.timer.TimerConsumer.sendTimerExchange(TimerConsumer.java:210)
>at
> org.apache.camel.component.timer.TimerConsumer$2.run(TimerConsumer.java:118)
>at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>at java.base/java.lang.Thread.run(Thread.java:829)
> Caused by: java.lang.IllegalArgumentException: AsyncHttpClient must be
> specified on: ahc://http://localhost:59729/foo
>at org.apache.camel.util.ObjectHelper.notNull(ObjectHelper.java:176)
>at
> org.apache.camel.component.ahc.AhcEndpoint.createProducer(AhcEndpoint.java:94)
>at
> org.apache.camel.support.DefaultEndpoint.createAsyncProducer(DefaultEndpoint.java:200)
>at
> org.apache.camel.support.cache.ServicePool$SinglePool.acquire(ServicePool.java:237)
>at
> org.apache.camel.support.cache.ServicePool$SinglePool.acquire(ServicePool.java:216)
>at org.apache.camel.support.cache.ServicePool.acquire(ServicePool.java:112)
>at
> org.apache.camel.support.cache.ProducerServicePool.acquire(ProducerServicePool.java:28)
>at
> org.apache.camel.support.cache.DefaultProducerCache.acquireProducer(DefaultProducerCache.java:149)
>... 14 common frames omitted
> {code}
> It causes that all traffic to camel-ahc endpoint is failing. It happens in my
> application for routes that take messages from JMS queue and sent it to HTTP
> (using camel-ahc component).
> Here is a test that reproduces a problem:
> {code:java}
> public class AhcRecipientListTest extends BaseAhcTest {
> @Test
> public void testRecipientListCalledBeforeComponentStarted() throws
> Exception {
> getMockEndpoint("mock:result").expectedBodiesReceived("Hello");
> assertMockEndpointsSatisfied();
> }
> @Override
> protected RouteBuilder createRouteBuilder() throws Exception {
> return new RouteBuilder() {
> @Override
> public void configure() throws Exception {
> from("timer://foo?delay=-1&?repeatCount=1")
> .recipientList(constant(getAhcEndpointUri()))
> .to("mock:result");
> from(getTestServerEndpointUri())
> .transform(constant("Hello"));
> }
> };
> }
> } {code}
> I've prepared a patch with another 2 tests and a possible bugfix. The bugfix
> is based on a solution from HttpEnpoint/HttpProducer.
> The bug was discovered in version 3.18.4, but it looks that it was present
> for a long time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18819) hbase: different version of audience-annotations brought by zookeeper
Jiri Ondrusek created CAMEL-18819: - Summary: hbase: different version of audience-annotations brought by zookeeper Key: CAMEL-18819 URL: https://issues.apache.org/jira/browse/CAMEL-18819 Project: Camel Issue Type: Bug Components: camel-hbase Affects Versions: 3.20.0 Reporter: Jiri Ondrusek Assignee: Jiri Ondrusek Dependency `audience-annotations` has version 0.13.0. Zookeper brings version 0.5.0. It should be excluded. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18818) Upgrade to Spring Boot 3.0.0
[ https://issues.apache.org/jira/browse/CAMEL-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17647990#comment-17647990 ] Clemens Blamauer commented on CAMEL-18818: -- Thank you, this information is very helpful. > Upgrade to Spring Boot 3.0.0 > > > Key: CAMEL-18818 > URL: https://issues.apache.org/jira/browse/CAMEL-18818 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Affects Versions: 3.19.0 >Reporter: Clemens Blamauer >Priority: Major > > Dear Camel team, > Is there already a plan/roadmap to upgrade camel-spring-boot to Spring Boot > 3.x? > We are planning to upgrade our microservices to Spring Boot 3 in the course > of next year. As many of them are using Camel, we'd like to consider this in > our roadmap. > Would you please share any plans/high-level roadmap for moving to Spring Boot > 3, if such exist? > Thank you. > Kind regards, > Clemens -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18818) Upgrade to Spring Boot 3.0.0
[ https://issues.apache.org/jira/browse/CAMEL-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17647986#comment-17647986 ] Claus Ibsen commented on CAMEL-18818: - Comments to blog post is welcome at https://github.com/apache/camel-website/pull/943 > Upgrade to Spring Boot 3.0.0 > > > Key: CAMEL-18818 > URL: https://issues.apache.org/jira/browse/CAMEL-18818 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Affects Versions: 3.19.0 >Reporter: Clemens Blamauer >Priority: Major > > Dear Camel team, > Is there already a plan/roadmap to upgrade camel-spring-boot to Spring Boot > 3.x? > We are planning to upgrade our microservices to Spring Boot 3 in the course > of next year. As many of them are using Camel, we'd like to consider this in > our roadmap. > Would you please share any plans/high-level roadmap for moving to Spring Boot > 3, if such exist? > Thank you. > Kind regards, > Clemens -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18818) Upgrade to Spring Boot 3.0.0
[ https://issues.apache.org/jira/browse/CAMEL-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17647963#comment-17647963 ] Claus Ibsen commented on CAMEL-18818: - And talks about Camel v4 is on the developer mailing list > Upgrade to Spring Boot 3.0.0 > > > Key: CAMEL-18818 > URL: https://issues.apache.org/jira/browse/CAMEL-18818 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Affects Versions: 3.19.0 >Reporter: Clemens Blamauer >Priority: Major > > Dear Camel team, > Is there already a plan/roadmap to upgrade camel-spring-boot to Spring Boot > 3.x? > We are planning to upgrade our microservices to Spring Boot 3 in the course > of next year. As many of them are using Camel, we'd like to consider this in > our roadmap. > Would you please share any plans/high-level roadmap for moving to Spring Boot > 3, if such exist? > Thank you. > Kind regards, > Clemens -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18818) Upgrade to Spring Boot 3.0.0
[ https://issues.apache.org/jira/browse/CAMEL-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17647961#comment-17647961 ] Claus Ibsen commented on CAMEL-18818: - Roadmap to be posted later this month > Upgrade to Spring Boot 3.0.0 > > > Key: CAMEL-18818 > URL: https://issues.apache.org/jira/browse/CAMEL-18818 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Affects Versions: 3.19.0 >Reporter: Clemens Blamauer >Priority: Major > > Dear Camel team, > Is there already a plan/roadmap to upgrade camel-spring-boot to Spring Boot > 3.x? > We are planning to upgrade our microservices to Spring Boot 3 in the course > of next year. As many of them are using Camel, we'd like to consider this in > our roadmap. > Would you please share any plans/high-level roadmap for moving to Spring Boot > 3, if such exist? > Thank you. > Kind regards, > Clemens -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18818) Upgrade to Spring Boot 3.0.0
[ https://issues.apache.org/jira/browse/CAMEL-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18818. - Resolution: Invalid > Upgrade to Spring Boot 3.0.0 > > > Key: CAMEL-18818 > URL: https://issues.apache.org/jira/browse/CAMEL-18818 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Affects Versions: 3.19.0 >Reporter: Clemens Blamauer >Priority: Major > > Dear Camel team, > Is there already a plan/roadmap to upgrade camel-spring-boot to Spring Boot > 3.x? > We are planning to upgrade our microservices to Spring Boot 3 in the course > of next year. As many of them are using Camel, we'd like to consider this in > our roadmap. > Would you please share any plans/high-level roadmap for moving to Spring Boot > 3, if such exist? > Thank you. > Kind regards, > Clemens -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18818) Upgrade to Spring Boot 3.0.0
[ https://issues.apache.org/jira/browse/CAMEL-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17647956#comment-17647956 ] Andrea Cosentino edited comment on CAMEL-18818 at 12/15/22 9:31 AM: Spring Boot 3.x support will come with Camel 4.x. Probably in 2023 with some milestone, before a fully supported Camel 4 release. So it's not in the short-term. was (Author: ancosen): Spring Boot 3.x support will come with Camel 4.x. Probably in 2023 with some milestone. > Upgrade to Spring Boot 3.0.0 > > > Key: CAMEL-18818 > URL: https://issues.apache.org/jira/browse/CAMEL-18818 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Affects Versions: 3.19.0 >Reporter: Clemens Blamauer >Priority: Major > > Dear Camel team, > Is there already a plan/roadmap to upgrade camel-spring-boot to Spring Boot > 3.x? > We are planning to upgrade our microservices to Spring Boot 3 in the course > of next year. As many of them are using Camel, we'd like to consider this in > our roadmap. > Would you please share any plans/high-level roadmap for moving to Spring Boot > 3, if such exist? > Thank you. > Kind regards, > Clemens -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18818) Upgrade to Spring Boot 3.0.0
[ https://issues.apache.org/jira/browse/CAMEL-18818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17647956#comment-17647956 ] Andrea Cosentino commented on CAMEL-18818: -- Spring Boot 3.x support will come with Camel 4.x. Probably in 2023 with some milestone. > Upgrade to Spring Boot 3.0.0 > > > Key: CAMEL-18818 > URL: https://issues.apache.org/jira/browse/CAMEL-18818 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-spring-boot >Affects Versions: 3.19.0 >Reporter: Clemens Blamauer >Priority: Major > > Dear Camel team, > Is there already a plan/roadmap to upgrade camel-spring-boot to Spring Boot > 3.x? > We are planning to upgrade our microservices to Spring Boot 3 in the course > of next year. As many of them are using Camel, we'd like to consider this in > our roadmap. > Would you please share any plans/high-level roadmap for moving to Spring Boot > 3, if such exist? > Thank you. > Kind regards, > Clemens -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18818) Upgrade to Spring Boot 3.0.0
Clemens Blamauer created CAMEL-18818: Summary: Upgrade to Spring Boot 3.0.0 Key: CAMEL-18818 URL: https://issues.apache.org/jira/browse/CAMEL-18818 Project: Camel Issue Type: Dependency upgrade Components: camel-spring-boot Affects Versions: 3.19.0 Reporter: Clemens Blamauer Dear Camel team, Is there already a plan/roadmap to upgrade camel-spring-boot to Spring Boot 3.x? We are planning to upgrade our microservices to Spring Boot 3 in the course of next year. As many of them are using Camel, we'd like to consider this in our roadmap. Would you please share any plans/high-level roadmap for moving to Spring Boot 3, if such exist? Thank you. Kind regards, Clemens -- This message was sent by Atlassian Jira (v8.20.10#820010)
