[jira] [Created] (CAMEL-18501) Camel-Google-Secret-Manager: Create a task looking for secrets update in PubSub
Andrea Cosentino created CAMEL-18501: Summary: Camel-Google-Secret-Manager: Create a task looking for secrets update in PubSub Key: CAMEL-18501 URL: https://issues.apache.org/jira/browse/CAMEL-18501 Project: Camel Issue Type: Sub-task Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18485) Error message when loading a routetemplate as resource
[
https://issues.apache.org/jira/browse/CAMEL-18485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17603233#comment-17603233
]
Raymond commented on CAMEL-18485:
-
ad 1) Nice
ad 2/3) I actually looked at the route reload, but there was something that I
missed or didn't work as expected (Can't recall what exactly), so I wrote my
own filewatch class and actually also use the ResourceHelper, but I was
thinking maybe we can skip it all and just pass a string to
loadOrUpdateRoute(String route) as a convenient method. Thus not a must have,
but just something convenient. But like you said, this maybe a bit too far from
normal use case to spend too much time on it.
> Error message when loading a routetemplate as resource
> --
>
> Key: CAMEL-18485
> URL: https://issues.apache.org/jira/browse/CAMEL-18485
> Project: Camel
> Issue Type: Improvement
> Components: came-core
>Affects Versions: 3.18.1
> Environment: - JDK 11 (OpenJDK Temurin)
> - Windows 10
> - Camel 3.18.1
>Reporter: Raymond
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.19.0
>
>
> I'm loading a xml routetemplate as resource as follows:
> {code:java}
> loader = extendedCamelContext.getRoutesLoader();
> Resource resource = IntegrationUtil.setResource(routetemplate);
> log.info("Loading routetemplate " + routetemplate);
> try{
>loader.loadRoutes(resource);
> }catch(java.lang.IllegalArgumentException e){
>loader.updateRoutes(resource);
> }
> {code}
> I however made a mistake and the resource was empty. The error
> message/stacktrace I received was:
> {code:java}
> Unable to parse resource: route.yaml
> at
> org.apache.camel.dsl.yaml.YamlRoutesBuilderLoaderSupport.lambda$doLoadRouteBuilder$1(YamlRoutesBuilderLoaderSupport.java:90)
> at java.base/java.util.Optional.orElseThrow(Optional.java:408)
> at
> org.apache.camel.dsl.yaml.YamlRoutesBuilderLoaderSupport.doLoadRouteBuilder(YamlRoutesBuilderLoaderSupport.java:90)
> at
> org.apache.camel.dsl.support.RouteBuilderLoaderSupport.loadRoutesBuilder(RouteBuilderLoaderSupport.java:104)
> at
> org.apache.camel.impl.engine.DefaultRoutesLoader.findRoutesBuilders(DefaultRoutesLoader.java:124)
> at
> org.apache.camel.spi.RoutesLoader.findRoutesBuilders(RoutesLoader.java:117)
> at org.apache.camel.spi.RoutesLoader.loadRoutes(RoutesLoader.java:72)
> {code}
> I was a bit puzzled about this because I was thinking I was providing a XML.
> Maybe better in this case:
> {code:java}
> Unable to parse resource: empty resource {code}
> The text also mentions 'route', but it can also be a routeConfiguration or a
> routeTemplate.
> Three sidenotes (some things I noticed):
> 1. In general one could check faulty input better. (is it a valid xml, yaml
> etc, or just some random text, empty or null). And for routetemplate are all
> the template parameters provide?
> 2. Notice in the example code I first need to create a resource before
> passing it to the routeloader. I have a string and would like to pass
> directly as a String to the routeloader.
> 3. When loading an existing route the routeloader may give an error (for
> example when the route already exist). I would like to
> loadOrUpdateRoute(String route) (this was possible in Camel 2).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18500) camel-kamelet - Kamelet component should avoid reflection
[ https://issues.apache.org/jira/browse/CAMEL-18500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18500. - Resolution: Fixed > camel-kamelet - Kamelet component should avoid reflection > - > > Key: CAMEL-18500 > URL: https://issues.apache.org/jira/browse/CAMEL-18500 > Project: Camel > Issue Type: Improvement > Components: camel-kamelet >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18500) camel-kamelet - Kamelet component should avoid reflection
Claus Ibsen created CAMEL-18500: --- Summary: camel-kamelet - Kamelet component should avoid reflection Key: CAMEL-18500 URL: https://issues.apache.org/jira/browse/CAMEL-18500 Project: Camel Issue Type: Improvement Components: camel-kamelet Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18491) camel-main - Configuring vault should avoid reflection
[ https://issues.apache.org/jira/browse/CAMEL-18491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18491. - Assignee: Claus Ibsen Resolution: Fixed > camel-main - Configuring vault should avoid reflection > -- > > Key: CAMEL-18491 > URL: https://issues.apache.org/jira/browse/CAMEL-18491 > Project: Camel > Issue Type: Improvement > Components: camel-main >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 3.19.0 > > > I noticed in the aws secret reloader example that the bean introspector > reports that reflection are used for configuring the vault options. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18485) Error message when loading a routetemplate as resource
[
https://issues.apache.org/jira/browse/CAMEL-18485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17603105#comment-17603105
]
Claus Ibsen edited comment on CAMEL-18485 at 9/12/22 2:29 PM:
--
ad 1) empty resource error is reported now
ad 2) See ResourceHelper
ad 3) no (see route reload that has some of that functionality)
was (Author: davsclaus):
ad 1) empty resource error is reported now
ad 2) See ResourceHelper
ad 3) no
> Error message when loading a routetemplate as resource
> --
>
> Key: CAMEL-18485
> URL: https://issues.apache.org/jira/browse/CAMEL-18485
> Project: Camel
> Issue Type: Improvement
> Components: came-core
>Affects Versions: 3.18.1
> Environment: - JDK 11 (OpenJDK Temurin)
> - Windows 10
> - Camel 3.18.1
>Reporter: Raymond
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.19.0
>
>
> I'm loading a xml routetemplate as resource as follows:
> {code:java}
> loader = extendedCamelContext.getRoutesLoader();
> Resource resource = IntegrationUtil.setResource(routetemplate);
> log.info("Loading routetemplate " + routetemplate);
> try{
>loader.loadRoutes(resource);
> }catch(java.lang.IllegalArgumentException e){
>loader.updateRoutes(resource);
> }
> {code}
> I however made a mistake and the resource was empty. The error
> message/stacktrace I received was:
> {code:java}
> Unable to parse resource: route.yaml
> at
> org.apache.camel.dsl.yaml.YamlRoutesBuilderLoaderSupport.lambda$doLoadRouteBuilder$1(YamlRoutesBuilderLoaderSupport.java:90)
> at java.base/java.util.Optional.orElseThrow(Optional.java:408)
> at
> org.apache.camel.dsl.yaml.YamlRoutesBuilderLoaderSupport.doLoadRouteBuilder(YamlRoutesBuilderLoaderSupport.java:90)
> at
> org.apache.camel.dsl.support.RouteBuilderLoaderSupport.loadRoutesBuilder(RouteBuilderLoaderSupport.java:104)
> at
> org.apache.camel.impl.engine.DefaultRoutesLoader.findRoutesBuilders(DefaultRoutesLoader.java:124)
> at
> org.apache.camel.spi.RoutesLoader.findRoutesBuilders(RoutesLoader.java:117)
> at org.apache.camel.spi.RoutesLoader.loadRoutes(RoutesLoader.java:72)
> {code}
> I was a bit puzzled about this because I was thinking I was providing a XML.
> Maybe better in this case:
> {code:java}
> Unable to parse resource: empty resource {code}
> The text also mentions 'route', but it can also be a routeConfiguration or a
> routeTemplate.
> Three sidenotes (some things I noticed):
> 1. In general one could check faulty input better. (is it a valid xml, yaml
> etc, or just some random text, empty or null). And for routetemplate are all
> the template parameters provide?
> 2. Notice in the example code I first need to create a resource before
> passing it to the routeloader. I have a string and would like to pass
> directly as a String to the routeloader.
> 3. When loading an existing route the routeloader may give an error (for
> example when the route already exist). I would like to
> loadOrUpdateRoute(String route) (this was possible in Camel 2).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-18485) Error message when loading a routetemplate as resource
[
https://issues.apache.org/jira/browse/CAMEL-18485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17603105#comment-17603105
]
Claus Ibsen commented on CAMEL-18485:
-
ad 1) empty resource error is reported now
ad 2) See ResourceHelper
ad 3) no
> Error message when loading a routetemplate as resource
> --
>
> Key: CAMEL-18485
> URL: https://issues.apache.org/jira/browse/CAMEL-18485
> Project: Camel
> Issue Type: Improvement
> Components: came-core
>Affects Versions: 3.18.1
> Environment: - JDK 11 (OpenJDK Temurin)
> - Windows 10
> - Camel 3.18.1
>Reporter: Raymond
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.19.0
>
>
> I'm loading a xml routetemplate as resource as follows:
> {code:java}
> loader = extendedCamelContext.getRoutesLoader();
> Resource resource = IntegrationUtil.setResource(routetemplate);
> log.info("Loading routetemplate " + routetemplate);
> try{
>loader.loadRoutes(resource);
> }catch(java.lang.IllegalArgumentException e){
>loader.updateRoutes(resource);
> }
> {code}
> I however made a mistake and the resource was empty. The error
> message/stacktrace I received was:
> {code:java}
> Unable to parse resource: route.yaml
> at
> org.apache.camel.dsl.yaml.YamlRoutesBuilderLoaderSupport.lambda$doLoadRouteBuilder$1(YamlRoutesBuilderLoaderSupport.java:90)
> at java.base/java.util.Optional.orElseThrow(Optional.java:408)
> at
> org.apache.camel.dsl.yaml.YamlRoutesBuilderLoaderSupport.doLoadRouteBuilder(YamlRoutesBuilderLoaderSupport.java:90)
> at
> org.apache.camel.dsl.support.RouteBuilderLoaderSupport.loadRoutesBuilder(RouteBuilderLoaderSupport.java:104)
> at
> org.apache.camel.impl.engine.DefaultRoutesLoader.findRoutesBuilders(DefaultRoutesLoader.java:124)
> at
> org.apache.camel.spi.RoutesLoader.findRoutesBuilders(RoutesLoader.java:117)
> at org.apache.camel.spi.RoutesLoader.loadRoutes(RoutesLoader.java:72)
> {code}
> I was a bit puzzled about this because I was thinking I was providing a XML.
> Maybe better in this case:
> {code:java}
> Unable to parse resource: empty resource {code}
> The text also mentions 'route', but it can also be a routeConfiguration or a
> routeTemplate.
> Three sidenotes (some things I noticed):
> 1. In general one could check faulty input better. (is it a valid xml, yaml
> etc, or just some random text, empty or null). And for routetemplate are all
> the template parameters provide?
> 2. Notice in the example code I first need to create a resource before
> passing it to the routeloader. I have a string and would like to pass
> directly as a String to the routeloader.
> 3. When loading an existing route the routeloader may give an error (for
> example when the route already exist). I would like to
> loadOrUpdateRoute(String route) (this was possible in Camel 2).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18485) Error message when loading a routetemplate as resource
[
https://issues.apache.org/jira/browse/CAMEL-18485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18485.
-
Assignee: Claus Ibsen
Resolution: Information Provided
Adding check for empty resource.
The API and terms are as-is. What you do is lower level and loading routes from
custom code, and that is not the usual usage for normal Camel end users.
> Error message when loading a routetemplate as resource
> --
>
> Key: CAMEL-18485
> URL: https://issues.apache.org/jira/browse/CAMEL-18485
> Project: Camel
> Issue Type: Improvement
> Components: came-core
>Affects Versions: 3.18.1
> Environment: - JDK 11 (OpenJDK Temurin)
> - Windows 10
> - Camel 3.18.1
>Reporter: Raymond
>Assignee: Claus Ibsen
>Priority: Minor
> Fix For: 3.19.0
>
>
> I'm loading a xml routetemplate as resource as follows:
> {code:java}
> loader = extendedCamelContext.getRoutesLoader();
> Resource resource = IntegrationUtil.setResource(routetemplate);
> log.info("Loading routetemplate " + routetemplate);
> try{
>loader.loadRoutes(resource);
> }catch(java.lang.IllegalArgumentException e){
>loader.updateRoutes(resource);
> }
> {code}
> I however made a mistake and the resource was empty. The error
> message/stacktrace I received was:
> {code:java}
> Unable to parse resource: route.yaml
> at
> org.apache.camel.dsl.yaml.YamlRoutesBuilderLoaderSupport.lambda$doLoadRouteBuilder$1(YamlRoutesBuilderLoaderSupport.java:90)
> at java.base/java.util.Optional.orElseThrow(Optional.java:408)
> at
> org.apache.camel.dsl.yaml.YamlRoutesBuilderLoaderSupport.doLoadRouteBuilder(YamlRoutesBuilderLoaderSupport.java:90)
> at
> org.apache.camel.dsl.support.RouteBuilderLoaderSupport.loadRoutesBuilder(RouteBuilderLoaderSupport.java:104)
> at
> org.apache.camel.impl.engine.DefaultRoutesLoader.findRoutesBuilders(DefaultRoutesLoader.java:124)
> at
> org.apache.camel.spi.RoutesLoader.findRoutesBuilders(RoutesLoader.java:117)
> at org.apache.camel.spi.RoutesLoader.loadRoutes(RoutesLoader.java:72)
> {code}
> I was a bit puzzled about this because I was thinking I was providing a XML.
> Maybe better in this case:
> {code:java}
> Unable to parse resource: empty resource {code}
> The text also mentions 'route', but it can also be a routeConfiguration or a
> routeTemplate.
> Three sidenotes (some things I noticed):
> 1. In general one could check faulty input better. (is it a valid xml, yaml
> etc, or just some random text, empty or null). And for routetemplate are all
> the template parameters provide?
> 2. Notice in the example code I first need to create a resource before
> passing it to the routeloader. I have a string and would like to pass
> directly as a String to the routeloader.
> 3. When loading an existing route the routeloader may give an error (for
> example when the route already exist). I would like to
> loadOrUpdateRoute(String route) (this was possible in Camel 2).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CAMEL-18327) camel-kafka: Kafka consumer closes when it is paused
[
https://issues.apache.org/jira/browse/CAMEL-18327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Otavio Rodolfo Piske resolved CAMEL-18327.
--
Resolution: Fixed
Merged and back-ported, therefore closing.
> camel-kafka: Kafka consumer closes when it is paused
>
>
> Key: CAMEL-18327
> URL: https://issues.apache.org/jira/browse/CAMEL-18327
> Project: Camel
> Issue Type: Task
> Components: camel-kafka
>Affects Versions: 3.17.0
>Reporter: rupam
>Assignee: Otavio Rodolfo Piske
>Priority: Major
> Fix For: 3.18.3, 3.19.0
>
>
>
> In the startPolling() method, if the consumer is suspending, then the
> unsubscribe method is called which permanently closes the consumer
>
> {code:java}
> Duration pollDuration = Duration.ofMillis(pollTimeoutMs);
> while (isKafkaConsumerRunnable() && isConnected() &&
> pollExceptionStrategy.canContinue()) {
> ConsumerRecords allRecords =
> consumer.poll(pollDuration);
> if (consumerListener != null) {
> if (!consumerListener.afterConsume(consumer)) {
> continue;
> }
> }
> ProcessingResult result =
> recordProcessorFacade.processPolledRecords(allRecords);
> if (result.isBreakOnErrorHit()) {
> LOG.debug("We hit an error ... setting flags to force reconnect");
> // force re-connect
> setReconnect(true);
> setConnected(false);
> }
> updateTaskState();
> }
> if (!isConnected()) {
> LOG.debug("Not reconnecting, check whether to auto-commit or not
> ...");
> commitManager.commit();
> }
> safeUnsubscribe();
> } catch (InterruptException e) {{code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (CAMEL-18499) camel-kubernetes - Upgrade to 6.x
Claus Ibsen created CAMEL-18499: --- Summary: camel-kubernetes - Upgrade to 6.x Key: CAMEL-18499 URL: https://issues.apache.org/jira/browse/CAMEL-18499 Project: Camel Issue Type: Dependency upgrade Components: camel-kubernetes Reporter: Claus Ibsen Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-14680) javax -> jakarta
[ https://issues.apache.org/jira/browse/CAMEL-14680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17603040#comment-17603040 ] Jimisola Laursen commented on CAMEL-14680: -- [~davsclaus] Ok . Thank you for the information. > javax -> jakarta > > > Key: CAMEL-14680 > URL: https://issues.apache.org/jira/browse/CAMEL-14680 > Project: Camel > Issue Type: Task >Reporter: Claus Ibsen >Priority: Major > Fix For: 4.0 > > > When the industry switches from javax to jarkarta then we should follow up as > well. > Its mostly JMS, Servlet, Mail, CDI, WS, JAX-RS, and other components. So at > some day we may have a release that switches fully over and is not backwards > compatible. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18470) camel-rabbitmq - skipQueueDeclare option is not working in 3.18.1. was working in 3.14.x
[ https://issues.apache.org/jira/browse/CAMEL-18470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18470. - Fix Version/s: 3.17.0 (was: 3.19.0) (was: 3.18.3) Resolution: Information Provided > camel-rabbitmq - skipQueueDeclare option is not working in 3.18.1. was > working in 3.14.x > - > > Key: CAMEL-18470 > URL: https://issues.apache.org/jira/browse/CAMEL-18470 > Project: Camel > Issue Type: Bug > Components: camel-rabbitmq >Affects Versions: 3.17.0, 3.18.0, 3.18.1 >Reporter: Devansh Arora >Priority: Minor > Fix For: 3.17.0 > > > we are using camel-rabbitmq > we upgraded to 3.18.1 from 3.14.2 recently. > to send a message to rabbitmq queue we using camel producer template. > In our endpoint uri for rabbitmq, we set skipQueueDeclare=true. by enabling > this we donot need to declare queue name. > after upgrade to 3.18.1 we are seeing below errors while sending message to > rabbitmq > Caused by: com.rabbitmq.client.ShutdownSignalException: channel error; > protocol method: #method(reply-code=404, reply-text=NOT_FOUND > - no queue '1892359723' in vhost 'myvhost', class-id=50, method-id=10) > Ideally it should not take any queue name. > *More trace.* in this trace we are seeing that it is trying to declare > exchange and queue and then bind them. with skipQueueDeclare=true it should > not happen i guess.. > > _org.apache.camel.CamelExecutionException: Exception occurred during > execution on the exchange: Exchange[]_ at > org.apache.camel.CamelExecutionException.wrapCamelExecutionException(CamelExecutionException.java:45)_ > at > org.apache.camel.support.ExchangeHelper.extractResultBody(ExchangeHelper.java:667)_ > at > org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:591)_ > at > org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:587)_ > at > org.apache.camel.impl.engine.DefaultProducerTemplate.sendBodyAndHeaders(DefaultProducerTemplate.java:313)_ > at > org.apache.camel.impl.engine.DefaultProducerTemplate.sendBodyAndHeaders(DefaultProducerTemplate.java:305)_ > at > com.myapp.myrabbitq.queue.route.MessageSender.routeMessageToTopicNoQueue_aroundBody20(MessageSender.java:211)_ > at > com.myapp.myrabbitq.queue.route.MessageSender$AjcClosure21.run(MessageSender.java:1)_ > at > org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:167)_ > at com.myapp.myrabbitq.log.LogAspect.aroundInternal(LogAspect.java:67)_ at > com.myapp.myrabbitq.log.LogAspect.ajc$inlineAccessMethod$com_digitate_ignio_log_LogAspect$com_digitate_ignio_log_LogAspect$aroundInternal(LogAspect.java:1)_ > at com.myapp.myrabbitq.log.LogAspect.around1(LogAspect.java:44)_ at > com.myapp.myrabbitq.queue.route.MessageSender.routeMessageToTopicNoQueue(MessageSender.java:207)_ > at > com.myapp.myrabbitq.platform.workitem.route.WorkitemManagerProducer.lambda$1_aroundBody6(WorkitemManagerProducer.java:53)_ > at > com.myapp.myrabbitq.platform.workitem.route.WorkitemManagerProducer$AjcClosure7.run(WorkitemManagerProducer.java:1)_ > at > org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:167)_ > at com.myapp.myrabbitq.log.LogAspect.aroundInternal(LogAspect.java:67)_ at > com.myapp.myrabbitq.log.LogAspect.ajc$inlineAccessMethod$com_digitate_ignio_log_LogAspect$com_digitate_ignio_log_LogAspect$aroundInternal(LogAspect.java:1)_ > at com.myapp.myrabbitq.log.LogAspect.around1(LogAspect.java:44)_ at > com.myapp.myrabbitq.platform.workitem.route.WorkitemManagerProducer.lambda$1(WorkitemManagerProducer.java:47)_ > at > java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)_ > at > java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)_ > at > java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)_ > at > java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)_ > at > java.base/java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:290)_ > at > java.base/java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:746)_ > at > java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)_ > at > java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)_ > at > java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)_ > at > java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)_ > at >
[jira] [Commented] (CAMEL-18470) camel-rabbitmq - skipQueueDeclare option is not working in 3.18.1. was working in 3.14.x
[
https://issues.apache.org/jira/browse/CAMEL-18470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17603032#comment-17603032
]
Claus Ibsen commented on CAMEL-18470:
-
Okay we can add a note in the 3.17 upgrade guide
> camel-rabbitmq - skipQueueDeclare option is not working in 3.18.1. was
> working in 3.14.x
> -
>
> Key: CAMEL-18470
> URL: https://issues.apache.org/jira/browse/CAMEL-18470
> Project: Camel
> Issue Type: Bug
> Components: camel-rabbitmq
>Affects Versions: 3.17.0, 3.18.0, 3.18.1
>Reporter: Devansh Arora
>Priority: Minor
> Fix For: 3.18.3, 3.19.0
>
>
> we are using camel-rabbitmq
> we upgraded to 3.18.1 from 3.14.2 recently.
> to send a message to rabbitmq queue we using camel producer template.
> In our endpoint uri for rabbitmq, we set skipQueueDeclare=true. by enabling
> this we donot need to declare queue name.
> after upgrade to 3.18.1 we are seeing below errors while sending message to
> rabbitmq
> Caused by: com.rabbitmq.client.ShutdownSignalException: channel error;
> protocol method: #method(reply-code=404, reply-text=NOT_FOUND
> - no queue '1892359723' in vhost 'myvhost', class-id=50, method-id=10)
> Ideally it should not take any queue name.
> *More trace.* in this trace we are seeing that it is trying to declare
> exchange and queue and then bind them. with skipQueueDeclare=true it should
> not happen i guess..
>
> _org.apache.camel.CamelExecutionException: Exception occurred during
> execution on the exchange: Exchange[]_ at
> org.apache.camel.CamelExecutionException.wrapCamelExecutionException(CamelExecutionException.java:45)_
> at
> org.apache.camel.support.ExchangeHelper.extractResultBody(ExchangeHelper.java:667)_
> at
> org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:591)_
> at
> org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:587)_
> at
> org.apache.camel.impl.engine.DefaultProducerTemplate.sendBodyAndHeaders(DefaultProducerTemplate.java:313)_
> at
> org.apache.camel.impl.engine.DefaultProducerTemplate.sendBodyAndHeaders(DefaultProducerTemplate.java:305)_
> at
> com.myapp.myrabbitq.queue.route.MessageSender.routeMessageToTopicNoQueue_aroundBody20(MessageSender.java:211)_
> at
> com.myapp.myrabbitq.queue.route.MessageSender$AjcClosure21.run(MessageSender.java:1)_
> at
> org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:167)_
> at com.myapp.myrabbitq.log.LogAspect.aroundInternal(LogAspect.java:67)_ at
> com.myapp.myrabbitq.log.LogAspect.ajc$inlineAccessMethod$com_digitate_ignio_log_LogAspect$com_digitate_ignio_log_LogAspect$aroundInternal(LogAspect.java:1)_
> at com.myapp.myrabbitq.log.LogAspect.around1(LogAspect.java:44)_ at
> com.myapp.myrabbitq.queue.route.MessageSender.routeMessageToTopicNoQueue(MessageSender.java:207)_
> at
> com.myapp.myrabbitq.platform.workitem.route.WorkitemManagerProducer.lambda$1_aroundBody6(WorkitemManagerProducer.java:53)_
> at
> com.myapp.myrabbitq.platform.workitem.route.WorkitemManagerProducer$AjcClosure7.run(WorkitemManagerProducer.java:1)_
> at
> org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:167)_
> at com.myapp.myrabbitq.log.LogAspect.aroundInternal(LogAspect.java:67)_ at
> com.myapp.myrabbitq.log.LogAspect.ajc$inlineAccessMethod$com_digitate_ignio_log_LogAspect$com_digitate_ignio_log_LogAspect$aroundInternal(LogAspect.java:1)_
> at com.myapp.myrabbitq.log.LogAspect.around1(LogAspect.java:44)_ at
> com.myapp.myrabbitq.platform.workitem.route.WorkitemManagerProducer.lambda$1(WorkitemManagerProducer.java:47)_
> at
> java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)_
> at
> java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)_
> at
> java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)_
> at
> java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)_
> at
> java.base/java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:290)_
> at
> java.base/java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:746)_
> at
> java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)_
> at
> java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)_
> at
> java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)_
> at
> java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594)_
> at
> java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183){_}Caused
>
[jira] [Created] (CAMEL-18498) Create a Camel AWS Event Ruler component
Andrea Cosentino created CAMEL-18498: Summary: Create a Camel AWS Event Ruler component Key: CAMEL-18498 URL: https://issues.apache.org/jira/browse/CAMEL-18498 Project: Camel Issue Type: New Feature Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18497) camel-jbang - camel run -v x.y.z
[ https://issues.apache.org/jira/browse/CAMEL-18497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17603018#comment-17603018 ] Claus Ibsen commented on CAMEL-18497: - We need to work with the JBang team to make this easier in JBang for "apps" then we can better do this > camel-jbang - camel run -v x.y.z > > > Key: CAMEL-18497 > URL: https://issues.apache.org/jira/browse/CAMEL-18497 > Project: Camel > Issue Type: Task > Components: camel-jbang >Reporter: Pasquale Congiusti >Priority: Minor > Fix For: 3.x > > > We can specify any Camel version when using the jbang CLI as documented in: > https://camel.apache.org/manual/camel-jbang.html#_using_a_specific_camel_version > However, it would be nice to have the same feature when using directly camel > CLI, in order to have the very same behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18497) camel-jbang - camel run -v x.y.z
[ https://issues.apache.org/jira/browse/CAMEL-18497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17603017#comment-17603017 ] Claus Ibsen commented on CAMEL-18497: - Yeah its a bit tricky to do as jbang does not support "apps" to specify easily arguments to their "main" script, and hence the -D JVM system property is the current "way of doing this". You can possible create an OS shell alias using the long command line where you set the version. We also have idea of allowing to specify the version in a config file, so you can set it once - ala camel set-version x.y.z > camel-jbang - camel run -v x.y.z > > > Key: CAMEL-18497 > URL: https://issues.apache.org/jira/browse/CAMEL-18497 > Project: Camel > Issue Type: Task > Components: camel-jbang >Reporter: Pasquale Congiusti >Priority: Minor > Fix For: 3.x > > > We can specify any Camel version when using the jbang CLI as documented in: > https://camel.apache.org/manual/camel-jbang.html#_using_a_specific_camel_version > However, it would be nice to have the same feature when using directly camel > CLI, in order to have the very same behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18497) camel-jbang - camel run -v x.y.z
[ https://issues.apache.org/jira/browse/CAMEL-18497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18497: Summary: camel-jbang - camel run -v x.y.z (was: camel run -v x.y.z) > camel-jbang - camel run -v x.y.z > > > Key: CAMEL-18497 > URL: https://issues.apache.org/jira/browse/CAMEL-18497 > Project: Camel > Issue Type: Task > Components: camel-jbang >Reporter: Pasquale Congiusti >Priority: Minor > > We can specify any Camel version when using the jbang CLI as documented in: > https://camel.apache.org/manual/camel-jbang.html#_using_a_specific_camel_version > However, it would be nice to have the same feature when using directly camel > CLI, in order to have the very same behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18497) camel-jbang - camel run -v x.y.z
[ https://issues.apache.org/jira/browse/CAMEL-18497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18497: Fix Version/s: 3.x > camel-jbang - camel run -v x.y.z > > > Key: CAMEL-18497 > URL: https://issues.apache.org/jira/browse/CAMEL-18497 > Project: Camel > Issue Type: Task > Components: camel-jbang >Reporter: Pasquale Congiusti >Priority: Minor > Fix For: 3.x > > > We can specify any Camel version when using the jbang CLI as documented in: > https://camel.apache.org/manual/camel-jbang.html#_using_a_specific_camel_version > However, it would be nice to have the same feature when using directly camel > CLI, in order to have the very same behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18497) camel run -v x.y.z
Pasquale Congiusti created CAMEL-18497: -- Summary: camel run -v x.y.z Key: CAMEL-18497 URL: https://issues.apache.org/jira/browse/CAMEL-18497 Project: Camel Issue Type: Task Components: camel-jbang Reporter: Pasquale Congiusti We can specify any Camel version when using the jbang CLI as documented in: https://camel.apache.org/manual/camel-jbang.html#_using_a_specific_camel_version However, it would be nice to have the same feature when using directly camel CLI, in order to have the very same behavior. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18456) camel-test-infra: investigate consolidating usages of web server and servlets
[ https://issues.apache.org/jira/browse/CAMEL-18456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602991#comment-17602991 ] Otavio Rodolfo Piske commented on CAMEL-18456: -- camel-cmis: broken (also won't be migrated because the component is deprecated) > camel-test-infra: investigate consolidating usages of web server and servlets > - > > Key: CAMEL-18456 > URL: https://issues.apache.org/jira/browse/CAMEL-18456 > Project: Camel > Issue Type: Task > Components: camel-test-infra >Reporter: Otavio Rodolfo Piske >Assignee: Otavio Rodolfo Piske >Priority: Major > Fix For: 3.x > > > There are many tests using Jetty, Undertow, Tomcat and others to run web > servers and/or servlet containers. Investigate consolidating this code into a > test infra module and cleaning up the components. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CAMEL-18470) camel-rabbitmq - skipQueueDeclare option is not working in 3.18.1. was working in 3.14.x
[ https://issues.apache.org/jira/browse/CAMEL-18470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602981#comment-17602981 ] Devansh Arora edited comment on CAMEL-18470 at 9/12/22 8:05 AM: after changes from https://issues.apache.org/jira/browse/CAMEL-17892 need to add skipQueueBind=true in route to prevent this error was (Author: devansharor...@gmail.com): after changes from https://issues.apache.org/jira/browse/CAMEL-17892 need to add skipQueueBind=true to prevent this error > camel-rabbitmq - skipQueueDeclare option is not working in 3.18.1. was > working in 3.14.x > - > > Key: CAMEL-18470 > URL: https://issues.apache.org/jira/browse/CAMEL-18470 > Project: Camel > Issue Type: Bug > Components: camel-rabbitmq >Affects Versions: 3.17.0, 3.18.0, 3.18.1 >Reporter: Devansh Arora >Priority: Minor > Fix For: 3.18.3, 3.19.0 > > > we are using camel-rabbitmq > we upgraded to 3.18.1 from 3.14.2 recently. > to send a message to rabbitmq queue we using camel producer template. > In our endpoint uri for rabbitmq, we set skipQueueDeclare=true. by enabling > this we donot need to declare queue name. > after upgrade to 3.18.1 we are seeing below errors while sending message to > rabbitmq > Caused by: com.rabbitmq.client.ShutdownSignalException: channel error; > protocol method: #method(reply-code=404, reply-text=NOT_FOUND > - no queue '1892359723' in vhost 'myvhost', class-id=50, method-id=10) > Ideally it should not take any queue name. > *More trace.* in this trace we are seeing that it is trying to declare > exchange and queue and then bind them. with skipQueueDeclare=true it should > not happen i guess.. > > _org.apache.camel.CamelExecutionException: Exception occurred during > execution on the exchange: Exchange[]_ at > org.apache.camel.CamelExecutionException.wrapCamelExecutionException(CamelExecutionException.java:45)_ > at > org.apache.camel.support.ExchangeHelper.extractResultBody(ExchangeHelper.java:667)_ > at > org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:591)_ > at > org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:587)_ > at > org.apache.camel.impl.engine.DefaultProducerTemplate.sendBodyAndHeaders(DefaultProducerTemplate.java:313)_ > at > org.apache.camel.impl.engine.DefaultProducerTemplate.sendBodyAndHeaders(DefaultProducerTemplate.java:305)_ > at > com.myapp.myrabbitq.queue.route.MessageSender.routeMessageToTopicNoQueue_aroundBody20(MessageSender.java:211)_ > at > com.myapp.myrabbitq.queue.route.MessageSender$AjcClosure21.run(MessageSender.java:1)_ > at > org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:167)_ > at com.myapp.myrabbitq.log.LogAspect.aroundInternal(LogAspect.java:67)_ at > com.myapp.myrabbitq.log.LogAspect.ajc$inlineAccessMethod$com_digitate_ignio_log_LogAspect$com_digitate_ignio_log_LogAspect$aroundInternal(LogAspect.java:1)_ > at com.myapp.myrabbitq.log.LogAspect.around1(LogAspect.java:44)_ at > com.myapp.myrabbitq.queue.route.MessageSender.routeMessageToTopicNoQueue(MessageSender.java:207)_ > at > com.myapp.myrabbitq.platform.workitem.route.WorkitemManagerProducer.lambda$1_aroundBody6(WorkitemManagerProducer.java:53)_ > at > com.myapp.myrabbitq.platform.workitem.route.WorkitemManagerProducer$AjcClosure7.run(WorkitemManagerProducer.java:1)_ > at > org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:167)_ > at com.myapp.myrabbitq.log.LogAspect.aroundInternal(LogAspect.java:67)_ at > com.myapp.myrabbitq.log.LogAspect.ajc$inlineAccessMethod$com_digitate_ignio_log_LogAspect$com_digitate_ignio_log_LogAspect$aroundInternal(LogAspect.java:1)_ > at com.myapp.myrabbitq.log.LogAspect.around1(LogAspect.java:44)_ at > com.myapp.myrabbitq.platform.workitem.route.WorkitemManagerProducer.lambda$1(WorkitemManagerProducer.java:47)_ > at > java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)_ > at > java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)_ > at > java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)_ > at > java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)_ > at > java.base/java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:290)_ > at > java.base/java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:746)_ > at > java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)_ > at >
[jira] [Comment Edited] (CAMEL-18470) camel-rabbitmq - skipQueueDeclare option is not working in 3.18.1. was working in 3.14.x
[ https://issues.apache.org/jira/browse/CAMEL-18470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602981#comment-17602981 ] Devansh Arora edited comment on CAMEL-18470 at 9/12/22 8:04 AM: after changes from https://issues.apache.org/jira/browse/CAMEL-17892 need to add skipQueueBind=true to prevent this error was (Author: devansharor...@gmail.com): after changes from https://issues.apache.org/jira/browse/CAMEL-17892[#https://issues.apache.org/jira/browse/CAMEL-17892] need to add skipQueueBind=true to prevent this error > camel-rabbitmq - skipQueueDeclare option is not working in 3.18.1. was > working in 3.14.x > - > > Key: CAMEL-18470 > URL: https://issues.apache.org/jira/browse/CAMEL-18470 > Project: Camel > Issue Type: Bug > Components: camel-rabbitmq >Affects Versions: 3.17.0, 3.18.0, 3.18.1 >Reporter: Devansh Arora >Priority: Minor > Fix For: 3.18.3, 3.19.0 > > > we are using camel-rabbitmq > we upgraded to 3.18.1 from 3.14.2 recently. > to send a message to rabbitmq queue we using camel producer template. > In our endpoint uri for rabbitmq, we set skipQueueDeclare=true. by enabling > this we donot need to declare queue name. > after upgrade to 3.18.1 we are seeing below errors while sending message to > rabbitmq > Caused by: com.rabbitmq.client.ShutdownSignalException: channel error; > protocol method: #method(reply-code=404, reply-text=NOT_FOUND > - no queue '1892359723' in vhost 'myvhost', class-id=50, method-id=10) > Ideally it should not take any queue name. > *More trace.* in this trace we are seeing that it is trying to declare > exchange and queue and then bind them. with skipQueueDeclare=true it should > not happen i guess.. > > _org.apache.camel.CamelExecutionException: Exception occurred during > execution on the exchange: Exchange[]_ at > org.apache.camel.CamelExecutionException.wrapCamelExecutionException(CamelExecutionException.java:45)_ > at > org.apache.camel.support.ExchangeHelper.extractResultBody(ExchangeHelper.java:667)_ > at > org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:591)_ > at > org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:587)_ > at > org.apache.camel.impl.engine.DefaultProducerTemplate.sendBodyAndHeaders(DefaultProducerTemplate.java:313)_ > at > org.apache.camel.impl.engine.DefaultProducerTemplate.sendBodyAndHeaders(DefaultProducerTemplate.java:305)_ > at > com.myapp.myrabbitq.queue.route.MessageSender.routeMessageToTopicNoQueue_aroundBody20(MessageSender.java:211)_ > at > com.myapp.myrabbitq.queue.route.MessageSender$AjcClosure21.run(MessageSender.java:1)_ > at > org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:167)_ > at com.myapp.myrabbitq.log.LogAspect.aroundInternal(LogAspect.java:67)_ at > com.myapp.myrabbitq.log.LogAspect.ajc$inlineAccessMethod$com_digitate_ignio_log_LogAspect$com_digitate_ignio_log_LogAspect$aroundInternal(LogAspect.java:1)_ > at com.myapp.myrabbitq.log.LogAspect.around1(LogAspect.java:44)_ at > com.myapp.myrabbitq.queue.route.MessageSender.routeMessageToTopicNoQueue(MessageSender.java:207)_ > at > com.myapp.myrabbitq.platform.workitem.route.WorkitemManagerProducer.lambda$1_aroundBody6(WorkitemManagerProducer.java:53)_ > at > com.myapp.myrabbitq.platform.workitem.route.WorkitemManagerProducer$AjcClosure7.run(WorkitemManagerProducer.java:1)_ > at > org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:167)_ > at com.myapp.myrabbitq.log.LogAspect.aroundInternal(LogAspect.java:67)_ at > com.myapp.myrabbitq.log.LogAspect.ajc$inlineAccessMethod$com_digitate_ignio_log_LogAspect$com_digitate_ignio_log_LogAspect$aroundInternal(LogAspect.java:1)_ > at com.myapp.myrabbitq.log.LogAspect.around1(LogAspect.java:44)_ at > com.myapp.myrabbitq.platform.workitem.route.WorkitemManagerProducer.lambda$1(WorkitemManagerProducer.java:47)_ > at > java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)_ > at > java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)_ > at > java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)_ > at > java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)_ > at > java.base/java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:290)_ > at > java.base/java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:746)_ > at > java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)_ > at >
[jira] [Commented] (CAMEL-18470) camel-rabbitmq - skipQueueDeclare option is not working in 3.18.1. was working in 3.14.x
[ https://issues.apache.org/jira/browse/CAMEL-18470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17602981#comment-17602981 ] Devansh Arora commented on CAMEL-18470: --- after changes from https://issues.apache.org/jira/browse/CAMEL-17892[#https://issues.apache.org/jira/browse/CAMEL-17892] need to add skipQueueBind=true to prevent this error > camel-rabbitmq - skipQueueDeclare option is not working in 3.18.1. was > working in 3.14.x > - > > Key: CAMEL-18470 > URL: https://issues.apache.org/jira/browse/CAMEL-18470 > Project: Camel > Issue Type: Bug > Components: camel-rabbitmq >Affects Versions: 3.17.0, 3.18.0, 3.18.1 >Reporter: Devansh Arora >Priority: Minor > Fix For: 3.18.3, 3.19.0 > > > we are using camel-rabbitmq > we upgraded to 3.18.1 from 3.14.2 recently. > to send a message to rabbitmq queue we using camel producer template. > In our endpoint uri for rabbitmq, we set skipQueueDeclare=true. by enabling > this we donot need to declare queue name. > after upgrade to 3.18.1 we are seeing below errors while sending message to > rabbitmq > Caused by: com.rabbitmq.client.ShutdownSignalException: channel error; > protocol method: #method(reply-code=404, reply-text=NOT_FOUND > - no queue '1892359723' in vhost 'myvhost', class-id=50, method-id=10) > Ideally it should not take any queue name. > *More trace.* in this trace we are seeing that it is trying to declare > exchange and queue and then bind them. with skipQueueDeclare=true it should > not happen i guess.. > > _org.apache.camel.CamelExecutionException: Exception occurred during > execution on the exchange: Exchange[]_ at > org.apache.camel.CamelExecutionException.wrapCamelExecutionException(CamelExecutionException.java:45)_ > at > org.apache.camel.support.ExchangeHelper.extractResultBody(ExchangeHelper.java:667)_ > at > org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:591)_ > at > org.apache.camel.impl.engine.DefaultProducerTemplate.extractResultBody(DefaultProducerTemplate.java:587)_ > at > org.apache.camel.impl.engine.DefaultProducerTemplate.sendBodyAndHeaders(DefaultProducerTemplate.java:313)_ > at > org.apache.camel.impl.engine.DefaultProducerTemplate.sendBodyAndHeaders(DefaultProducerTemplate.java:305)_ > at > com.myapp.myrabbitq.queue.route.MessageSender.routeMessageToTopicNoQueue_aroundBody20(MessageSender.java:211)_ > at > com.myapp.myrabbitq.queue.route.MessageSender$AjcClosure21.run(MessageSender.java:1)_ > at > org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:167)_ > at com.myapp.myrabbitq.log.LogAspect.aroundInternal(LogAspect.java:67)_ at > com.myapp.myrabbitq.log.LogAspect.ajc$inlineAccessMethod$com_digitate_ignio_log_LogAspect$com_digitate_ignio_log_LogAspect$aroundInternal(LogAspect.java:1)_ > at com.myapp.myrabbitq.log.LogAspect.around1(LogAspect.java:44)_ at > com.myapp.myrabbitq.queue.route.MessageSender.routeMessageToTopicNoQueue(MessageSender.java:207)_ > at > com.myapp.myrabbitq.platform.workitem.route.WorkitemManagerProducer.lambda$1_aroundBody6(WorkitemManagerProducer.java:53)_ > at > com.myapp.myrabbitq.platform.workitem.route.WorkitemManagerProducer$AjcClosure7.run(WorkitemManagerProducer.java:1)_ > at > org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:167)_ > at com.myapp.myrabbitq.log.LogAspect.aroundInternal(LogAspect.java:67)_ at > com.myapp.myrabbitq.log.LogAspect.ajc$inlineAccessMethod$com_digitate_ignio_log_LogAspect$com_digitate_ignio_log_LogAspect$aroundInternal(LogAspect.java:1)_ > at com.myapp.myrabbitq.log.LogAspect.around1(LogAspect.java:44)_ at > com.myapp.myrabbitq.platform.workitem.route.WorkitemManagerProducer.lambda$1(WorkitemManagerProducer.java:47)_ > at > java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)_ > at > java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177)_ > at > java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)_ > at > java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)_ > at > java.base/java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:290)_ > at > java.base/java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:746)_ > at > java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290)_ > at > java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020)_ > at > java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656)_ > at >
