[jira] [Created] (CAMEL-18488) camel-management - Statistic for current throughput
Claus Ibsen created CAMEL-18488: --- Summary: camel-management - Statistic for current throughput Key: CAMEL-18488 URL: https://issues.apache.org/jira/browse/CAMEL-18488 Project: Camel Issue Type: New Feature Components: camel-jmx Reporter: Claus Ibsen Assignee: Claus Ibsen Fix For: 3.19.0 If you enable load average then we can also output the current msg/sec as throughput. And maybe also calculate a sliding window of average throughput. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18483) camel-microprofile-health: Routes and consumers health checks are not registered if routes are supervised
[ https://issues.apache.org/jira/browse/CAMEL-18483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Netherton resolved CAMEL-18483. - Resolution: Fixed > camel-microprofile-health: Routes and consumers health checks are not > registered if routes are supervised > - > > Key: CAMEL-18483 > URL: https://issues.apache.org/jira/browse/CAMEL-18483 > Project: Camel > Issue Type: Bug > Components: camel-microprofile-health >Affects Versions: 3.18.1, 3.18.2 >Reporter: James Netherton >Assignee: James Netherton >Priority: Major > Fix For: 3.18.3, 3.19.0 > > > Some more detail here: > https://github.com/apache/camel-quarkus/issues/3989 > Due to how CamelMicroProfileHealthCheckRegistry figures out whether it should > register the HealthCheckRespository checks it misses ones for routes & > consumers if SupervisingRouteController is in use. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18479) camel-aws - Capture aws secrets in use making refresh no need for declaring the secrets
[ https://issues.apache.org/jira/browse/CAMEL-18479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18479. - Resolution: Fixed > camel-aws - Capture aws secrets in use making refresh no need for declaring > the secrets > --- > > Key: CAMEL-18479 > URL: https://issues.apache.org/jira/browse/CAMEL-18479 > Project: Camel > Issue Type: Improvement > Components: camel-aws >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Major > Fix For: 3.19.0 > > > The goal is to avoid need for declaring this > https://github.com/apache/camel-examples/blob/main/examples/aws/aws-secrets-manager-reloading/src/main/resources/application.properties#L30 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18463) upgrade grpc to 1.49.x
[ https://issues.apache.org/jira/browse/CAMEL-18463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-18463: Fix Version/s: 3.20.0 (was: 3.19.0) > upgrade grpc to 1.49.x > -- > > Key: CAMEL-18463 > URL: https://issues.apache.org/jira/browse/CAMEL-18463 > Project: Camel > Issue Type: Dependency upgrade > Components: camel-grpc >Reporter: Claus Ibsen >Priority: Minor > Fix For: 3.20.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-11647) SupervisingRouteController : add JMX support
[ https://issues.apache.org/jira/browse/CAMEL-11647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11647: Fix Version/s: 3.20.0 (was: 3.19.0) > SupervisingRouteController : add JMX support > > > Key: CAMEL-11647 > URL: https://issues.apache.org/jira/browse/CAMEL-11647 > Project: Camel > Issue Type: Improvement > Components: camel-core, camel-spring-boot >Reporter: Luca Burgazzoli >Assignee: Claus Ibsen >Priority: Major > Labels: route-controller > Fix For: 3.20.0 > > > SupervisingRouteController should expose info about routes it is supervising > like: > - the back-off configuration > - the status > - when the next restart will happens (i.e. nb of seconds till attempt) > - the last error/stack trace > Camel Spring Boot should leverage this and expose the same information from > an Endpoints -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-11647) SupervisingRouteController : add JMX support
[ https://issues.apache.org/jira/browse/CAMEL-11647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-11647: Issue Type: New Feature (was: Improvement) > SupervisingRouteController : add JMX support > > > Key: CAMEL-11647 > URL: https://issues.apache.org/jira/browse/CAMEL-11647 > Project: Camel > Issue Type: New Feature > Components: camel-core, camel-spring-boot >Reporter: Luca Burgazzoli >Assignee: Claus Ibsen >Priority: Major > Labels: route-controller > Fix For: 3.20.0 > > > SupervisingRouteController should expose info about routes it is supervising > like: > - the back-off configuration > - the status > - when the next restart will happens (i.e. nb of seconds till attempt) > - the last error/stack trace > Camel Spring Boot should leverage this and expose the same information from > an Endpoints -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18449) camel-spring-boot - platform-http implementation
[ https://issues.apache.org/jira/browse/CAMEL-18449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-18449. - Resolution: Fixed > camel-spring-boot - platform-http implementation > > > Key: CAMEL-18449 > URL: https://issues.apache.org/jira/browse/CAMEL-18449 > Project: Camel > Issue Type: New Feature > Components: camel-spring-boot >Affects Versions: 3.18.0 >Reporter: Federico Mariani >Assignee: Federico Mariani >Priority: Major > Fix For: 3.19.0 > > Attachments: rest-post-consumer.zip > > > I was wondering if an implementation for platform-http can be provided in > camel-spring-boot platform-http-starter. Attached you can find a simple POC, > do you think it can be helpful/possible to have something like > _SpringBootPlatformHttpEngine_ implemented in camel-platform-http-starter? > In this way the > [camel-quarkus|https://camel.apache.org/camel-quarkus/2.11.x/reference/extensions/platform-http.html#_using_platform_http_via_camel_rest_dsl] > and camel-spring-boot behavior will be similar. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CAMEL-18487) Camel-AWS-Secrets-Manager: Cloudtrail task should support environment variables as configuration too
Andrea Cosentino created CAMEL-18487: Summary: Camel-AWS-Secrets-Manager: Cloudtrail task should support environment variables as configuration too Key: CAMEL-18487 URL: https://issues.apache.org/jira/browse/CAMEL-18487 Project: Camel Issue Type: Sub-task Components: camel-aws2 Reporter: Andrea Cosentino Assignee: Andrea Cosentino Fix For: 3.19.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CAMEL-18472) deadlock when concurrently adding and removing routes
[
https://issues.apache.org/jira/browse/CAMEL-18472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-18472.
-
Resolution: Fixed
Thanks for reporting and the PR
> deadlock when concurrently adding and removing routes
> -
>
> Key: CAMEL-18472
> URL: https://issues.apache.org/jira/browse/CAMEL-18472
> Project: Camel
> Issue Type: Improvement
> Components: came-core
>Affects Versions: 3.7.7, 3.19.0
>Reporter: Gerda Ilger
>Priority: Major
> Fix For: 3.19.0
>
>
> As discussed on us...@camel.apache.org, i am opening a Jira issue +
> We ran into the following issue when dynamically adding and removing ftp
> routes, whose consumers sometimes take a longer time to start up:
> Deadlock when concurrently adding and removing routes
> * {{Default/Abstract)CamelContext.addRoutes}} ->
> {{DefaultCamelContext.addRouteDefinitions}} locks {{DefaultModel}} first, and
> is then blocked trying to lock {{DefaultCamelContext}}
> * {{(Default/Abstract)CamelContext.removeRoute}} locks
> {{DefaultCamelContext}} first, and is then blocked trying to lock
> {{DefaultModel}}
> {*}Threaddump{*}:
> {{Found one Java-level deadlock:}}
> {{=}}
> {{"pool-2-thread-1":}}
> {{waiting to lock monitor 0x7fd22000b0c0 (object 0x00068c800170, a
> org.apache.camel.impl.DefaultModel),}}
> {{{}which is held by "pool-2-thread-3"{}}}{{{}"pool-2-thread-3":{}}}
> {{waiting to lock monitor 0x7fd21404a130 (object 0x00068c002a20, a
> org.apache.camel.impl.DefaultCamelContext),}}
> {{{}which is held by "pool-2-thread-2"{}}}{{{}"pool-2-thread-2":{}}}
> {{waiting to lock monitor 0x7fd22000b0c0 (object 0x00068c800170, a
> org.apache.camel.impl.DefaultModel),}}
> {{{}which is held by "pool-2-thread-3"{}}}{{{}Java stack information for the
> threads listed above:{}}}
> {{===}}
> {{"pool-2-thread-1":}}
> {{at
> org.apache.camel.impl.DefaultModel.addRouteDefinitions(DefaultModel.java:163)}}
> - {{{}waiting to lock <0x00068c800170> (a
> org.apache.camel.impl.DefaultModel){}}}{{{}at
> org.apache.camel.impl.DefaultCamelContext.addRouteDefinitions(DefaultCamelContext.java:351){}}}{{{}at
>
> org.apache.camel.builder.RouteBuilder.populateRoutes(RouteBuilder.java:723){}}}{{{}at
>
> org.apache.camel.builder.RouteBuilder.addRoutesToCamelContext(RouteBuilder.java:569){}}}{{{}at
>
> org.apache.camel.impl.engine.AbstractCamelContext.addRoutes(AbstractCamelContext.java:1186){}}}{{{}at
>
> org.apache.camel.impl.DynamicallyConcurrentlyAddRoutesTest.lambda$1(DynamicallyConcurrentlyAddRoutesTest.java:64){}}}{{{}at
>
> org.apache.camel.impl.DynamicallyConcurrentlyAddRoutesTest$$Lambda$487/0x0008002c52d0.call(Unknown
> Source){}}}{{{}at
> java.util.concurrent.FutureTask.run(java.base@17.0.3/FutureTask.java:264){}}}{{{}at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@17.0.3/ThreadPoolExecutor.java:1136){}}}{{{}at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@17.0.3/ThreadPoolExecutor.java:635){}}}{{{}at
>
> java.lang.Thread.run(java.base@17.0.3/Thread.java:833){}}}{{{}"pool-2-thread-3":{}}}{{{}at
>
> org.apache.camel.impl.engine.AbstractCamelContext.removeRoute(AbstractCamelContext.java:1400){}}}
> - {{{}waiting to lock <0x00068c002a20> (a
> org.apache.camel.impl.DefaultCamelContext){}}}{{{}at
> org.apache.camel.impl.DefaultModel.removeRouteDefinition(DefaultModel.java:212){}}}
> - {{{}locked <0x00068c800170> (a
> org.apache.camel.impl.DefaultModel){}}}{{{}at
> org.apache.camel.impl.DefaultModel.removeRouteDefinitions(DefaultModel.java:201){}}}
> - {{{}locked <0x00068c800170> (a
> org.apache.camel.impl.DefaultModel){}}}{{{}at
> org.apache.camel.impl.DefaultModel.addRouteDefinitions(DefaultModel.java:179){}}}
> - {{{}locked <0x00068c800170> (a
> org.apache.camel.impl.DefaultModel){}}}{{{}at
> org.apache.camel.impl.DefaultCamelContext.addRouteDefinitions(DefaultCamelContext.java:351){}}}{{{}at
>
> org.apache.camel.builder.RouteBuilder.populateRoutes(RouteBuilder.java:723){}}}{{{}at
>
> org.apache.camel.builder.RouteBuilder.addRoutesToCamelContext(RouteBuilder.java:569){}}}{{{}at
>
> org.apache.camel.impl.engine.AbstractCamelContext.addRoutes(AbstractCamelContext.java:1186){}}}{{{}at
>
> org.apache.camel.impl.DynamicallyConcurrentlyAddRoutesTest.lambda$1(DynamicallyConcurrentlyAddRoutesTest.java:64){}}}{{{}at
>
> org.apache.camel.impl.DynamicallyConcurrentlyAddRoutesTest$$Lambda$487/0x0008002c52d0.call(Unknown
> Source){}}}{{{}at
> java.util.concurrent.FutureTask.run(java.base@17.0.3/FutureTask.java:264){}}}{{{}at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@17.0.3/ThreadPoolExecutor.java:1136){}}}{{{}at
>
[jira] [Created] (CAMEL-18486) Camel-xchange: Add mocked mapping for the test AccountProducerTest#testFundingHistory
Jiri Ondrusek created CAMEL-18486:
-
Summary: Camel-xchange: Add mocked mapping for the test
AccountProducerTest#testFundingHistory
Key: CAMEL-18486
URL: https://issues.apache.org/jira/browse/CAMEL-18486
Project: Camel
Issue Type: Test
Affects Versions: 3.19.0
Reporter: Jiri Ondrusek
Assignee: Jiri Ondrusek
During implementation of https://issues.apache.org/jira/browse/CAMEL-18484 I
had a problem with the test {_}AccountProducerTest#testFundingHistory{_}.
Test works when using real account, but once I added a wiremock recording
server to catch communication, I got
{code:java}
org.knowm.xchange.exceptions.ExchangeException: API-key format invalid. (HTTP
status code: 400) {code}
I'm not sure why this is happening. It would be nice to solve this problem and
once it works, enable this test for the mocked testing (it is disabled with a
comment now)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CAMEL-16624) camel-salesforce - Replace Map Options with Multivalue
[ https://issues.apache.org/jira/browse/CAMEL-16624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601762#comment-17601762 ] Hemang Ajmera commented on CAMEL-16624: --- I do not remember for sure since lately I am not working on camel. It could be either, I just happened to notice initialReplayIdMap also, so added to jira. But if I remember correctly, initialReplayIdMap can be used to set different values of replay Id for different topics. > camel-salesforce - Replace Map Options with Multivalue > -- > > Key: CAMEL-16624 > URL: https://issues.apache.org/jira/browse/CAMEL-16624 > Project: Camel > Issue Type: Improvement > Components: camel-salesforce >Affects Versions: 3.9.0 >Reporter: Hemang Ajmera >Priority: Minor > Fix For: 3.x > > > We should replace Map with Multi Value, so that they can be initialized in > URI sting. > > Please refer to > [https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/set.20Map.20option/near/239077029] > for details > > The Map options in Salesforce Component are > # apexQueryParams > # initialReplayIdMap > > If there is quick way to find all the options in other component which is > Map, then this Jira can be extended to convert them all. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CAMEL-18472) deadlock when concurrently adding and removing routes
[
https://issues.apache.org/jira/browse/CAMEL-18472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-18472:
Fix Version/s: 3.19.0
> deadlock when concurrently adding and removing routes
> -
>
> Key: CAMEL-18472
> URL: https://issues.apache.org/jira/browse/CAMEL-18472
> Project: Camel
> Issue Type: Improvement
> Components: came-core
>Affects Versions: 3.7.7, 3.19.0
>Reporter: Gerda Ilger
>Priority: Major
> Fix For: 3.19.0
>
>
> As discussed on us...@camel.apache.org, i am opening a Jira issue +
> We ran into the following issue when dynamically adding and removing ftp
> routes, whose consumers sometimes take a longer time to start up:
> Deadlock when concurrently adding and removing routes
> * {{Default/Abstract)CamelContext.addRoutes}} ->
> {{DefaultCamelContext.addRouteDefinitions}} locks {{DefaultModel}} first, and
> is then blocked trying to lock {{DefaultCamelContext}}
> * {{(Default/Abstract)CamelContext.removeRoute}} locks
> {{DefaultCamelContext}} first, and is then blocked trying to lock
> {{DefaultModel}}
> {*}Threaddump{*}:
> {{Found one Java-level deadlock:}}
> {{=}}
> {{"pool-2-thread-1":}}
> {{waiting to lock monitor 0x7fd22000b0c0 (object 0x00068c800170, a
> org.apache.camel.impl.DefaultModel),}}
> {{{}which is held by "pool-2-thread-3"{}}}{{{}"pool-2-thread-3":{}}}
> {{waiting to lock monitor 0x7fd21404a130 (object 0x00068c002a20, a
> org.apache.camel.impl.DefaultCamelContext),}}
> {{{}which is held by "pool-2-thread-2"{}}}{{{}"pool-2-thread-2":{}}}
> {{waiting to lock monitor 0x7fd22000b0c0 (object 0x00068c800170, a
> org.apache.camel.impl.DefaultModel),}}
> {{{}which is held by "pool-2-thread-3"{}}}{{{}Java stack information for the
> threads listed above:{}}}
> {{===}}
> {{"pool-2-thread-1":}}
> {{at
> org.apache.camel.impl.DefaultModel.addRouteDefinitions(DefaultModel.java:163)}}
> - {{{}waiting to lock <0x00068c800170> (a
> org.apache.camel.impl.DefaultModel){}}}{{{}at
> org.apache.camel.impl.DefaultCamelContext.addRouteDefinitions(DefaultCamelContext.java:351){}}}{{{}at
>
> org.apache.camel.builder.RouteBuilder.populateRoutes(RouteBuilder.java:723){}}}{{{}at
>
> org.apache.camel.builder.RouteBuilder.addRoutesToCamelContext(RouteBuilder.java:569){}}}{{{}at
>
> org.apache.camel.impl.engine.AbstractCamelContext.addRoutes(AbstractCamelContext.java:1186){}}}{{{}at
>
> org.apache.camel.impl.DynamicallyConcurrentlyAddRoutesTest.lambda$1(DynamicallyConcurrentlyAddRoutesTest.java:64){}}}{{{}at
>
> org.apache.camel.impl.DynamicallyConcurrentlyAddRoutesTest$$Lambda$487/0x0008002c52d0.call(Unknown
> Source){}}}{{{}at
> java.util.concurrent.FutureTask.run(java.base@17.0.3/FutureTask.java:264){}}}{{{}at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@17.0.3/ThreadPoolExecutor.java:1136){}}}{{{}at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@17.0.3/ThreadPoolExecutor.java:635){}}}{{{}at
>
> java.lang.Thread.run(java.base@17.0.3/Thread.java:833){}}}{{{}"pool-2-thread-3":{}}}{{{}at
>
> org.apache.camel.impl.engine.AbstractCamelContext.removeRoute(AbstractCamelContext.java:1400){}}}
> - {{{}waiting to lock <0x00068c002a20> (a
> org.apache.camel.impl.DefaultCamelContext){}}}{{{}at
> org.apache.camel.impl.DefaultModel.removeRouteDefinition(DefaultModel.java:212){}}}
> - {{{}locked <0x00068c800170> (a
> org.apache.camel.impl.DefaultModel){}}}{{{}at
> org.apache.camel.impl.DefaultModel.removeRouteDefinitions(DefaultModel.java:201){}}}
> - {{{}locked <0x00068c800170> (a
> org.apache.camel.impl.DefaultModel){}}}{{{}at
> org.apache.camel.impl.DefaultModel.addRouteDefinitions(DefaultModel.java:179){}}}
> - {{{}locked <0x00068c800170> (a
> org.apache.camel.impl.DefaultModel){}}}{{{}at
> org.apache.camel.impl.DefaultCamelContext.addRouteDefinitions(DefaultCamelContext.java:351){}}}{{{}at
>
> org.apache.camel.builder.RouteBuilder.populateRoutes(RouteBuilder.java:723){}}}{{{}at
>
> org.apache.camel.builder.RouteBuilder.addRoutesToCamelContext(RouteBuilder.java:569){}}}{{{}at
>
> org.apache.camel.impl.engine.AbstractCamelContext.addRoutes(AbstractCamelContext.java:1186){}}}{{{}at
>
> org.apache.camel.impl.DynamicallyConcurrentlyAddRoutesTest.lambda$1(DynamicallyConcurrentlyAddRoutesTest.java:64){}}}{{{}at
>
> org.apache.camel.impl.DynamicallyConcurrentlyAddRoutesTest$$Lambda$487/0x0008002c52d0.call(Unknown
> Source){}}}{{{}at
> java.util.concurrent.FutureTask.run(java.base@17.0.3/FutureTask.java:264){}}}{{{}at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@17.0.3/ThreadPoolExecutor.java:1136){}}}{{{}at
>
>
[jira] [Created] (CAMEL-18485) Error message when loading a routetemplate as resource
Raymond created CAMEL-18485:
---
Summary: Error message when loading a routetemplate as resource
Key: CAMEL-18485
URL: https://issues.apache.org/jira/browse/CAMEL-18485
Project: Camel
Issue Type: Bug
Components: came-core
Affects Versions: 3.18.1
Environment: - JDK 11 (OpenJDK Temurin)
- Windows 10
- Camel 3.18.1
Reporter: Raymond
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] [Created] (CAMEL-18484) Camel-xchange: Enable mock testing without neaed of real account
Jiri Ondrusek created CAMEL-18484:
-
Summary: Camel-xchange: Enable mock testing without neaed of real
account
Key: CAMEL-18484
URL: https://issues.apache.org/jira/browse/CAMEL-18484
Project: Camel
Issue Type: Test
Affects Versions: 3.19.0
Reporter: Jiri Ondrusek
Assignee: Jiri Ondrusek
Tests in camel-xchange component are disabled by default (because of the need
of the real credentials)
{code:java}
@EnabledIfSystemProperty(named = "enable.xchange.itests", matches = "true",
disabledReason = "Requires API credentials") {code}
It would be much better if the functionality was covered by mocked junit tests.
(For example wiremock could be used)
- if _enable.xchange.itests_ is set to {_}true{_}, not-mocked test would be
used (as before)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CAMEL-18476) when artemis streaming enabled then Camel-file component is not able to delete the file after its archived in windows
[
https://issues.apache.org/jira/browse/CAMEL-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ramarajan R updated CAMEL-18476:
Attachment: artemis-large-messages-final.zip
Docs Text: Attached example with Junit
Summary: when artemis streaming enabled then Camel-file component is not
able to delete the file after its archived in windows (was: Camel-file
component is not able to delete the file after its archived in windows)
> when artemis streaming enabled then Camel-file component is not able to
> delete the file after its archived in windows
> -
>
> Key: CAMEL-18476
> URL: https://issues.apache.org/jira/browse/CAMEL-18476
> Project: Camel
> Issue Type: Bug
> Components: camel-file
>Affects Versions: 3.14.3, 3.18.1
>Reporter: Ramarajan R
>Priority: Minor
> Attachments: artemis-large-messages-final.zip,
> artemis-large-messages.zip
>
>
> I have used
> [https://github.com/apache/camel-examples/tree/main/examples/artemis-large-messages]
> using AMQ 7.8.0 Broker
> Messages are getting processed but after processing the file is unable to
> delete from source location, tested in more than 1 windows systems facing the
> same
> I am using Camel 3.14.3 and Spring boot 2.6.6 using JAVA DSL,
> tested with Camel 3.18.1 and Spring boot 2.7.3 also
> when running with Camel XML routes are fine but we want to use Java DSL ,
> Kindly help.
> Raising the concern in Zulip chat earlier.
> {{[https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/camel-file.20artemis.20large.20message.20example.20failing.20in.20windows]
> }}{{{}tion-poc/inbox0] o.a.c.c.file.GenericFileOnCompletion : Error during
> commit. Exchange[7D4CFE29E3F7515-0003]. Caused by:
> [org.apache.camel.component.file.GenericFileOperationFailedException - Error
> renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx to
> C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx]{}}}{{{}org.apache.camel.component.file.GenericFileOperationFailedException:
> Error renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx
> to C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx{}}}
> {{at
> org.apache.camel.component.file.FileOperations.renameFile(FileOperations.java:93)
> ~[camel-file-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:145)
> ~[camel-file-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:121)
> ~[camel-file-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.component.file.GenericFileOnCompletion.processStrategyCommit(GenericFileOnCompletion.java:134)
> ~[camel-file-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.component.file.GenericFileOnCompletion.onCompletion(GenericFileOnCompletion.java:86)
> ~[camel-file-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.component.file.GenericFileOnCompletion.onComplete(GenericFileOnCompletion.java:60)
> ~[camel-file-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.support.UnitOfWorkHelper.doneSynchronization(UnitOfWorkHelper.java:104)
> ~[camel-support-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.support.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:93)
> ~[camel-support-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.impl.engine.DefaultUnitOfWork.done(DefaultUnitOfWork.java:238)
> ~[camel-base-engine-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.support.UnitOfWorkHelper.doneUow(UnitOfWorkHelper.java:61)
> ~[camel-support-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:777)
> ~[camel-base-engine-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:712)
> ~[camel-base-engine-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.impl.engine.CamelInternalProcessor$AsyncAfterTask.done(CamelInternalProcessor.java:263)
> ~[camel-base-engine-3.14.3.jar:3.14.3]}}
> {{at org.apache.camel.AsyncCallback.run(AsyncCallback.java:44)
> ~[camel-api-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193)
> ~[camel-base-engine-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:64)
> ~[camel-base-engine-3.14.3.jar:3.14.3]}}
> {{at org.apache.camel.processor.Pipeline.process(Pipeline.java:184)
> ~[camel-core-processor-3.14.3.jar:3.14.3]}}
> {{at
>
[jira] [Commented] (CAMEL-18476) when artemis streaming enabled then Camel-file component is not able to delete the file after its archived in windows
[
https://issues.apache.org/jira/browse/CAMEL-18476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601716#comment-17601716
]
Ramarajan R commented on CAMEL-18476:
-
Hi Team,
pls find the attached example with junits, I am facing the issue only when we
have artemis-stream enabled for large message.
if you comment below lines from ConsumerBeanConfiguration the same test case
passes.
coreConsumerComponent.setArtemisStreamingEnabled(true);
coreConsumerConnectionFactory.setMinLargeMessageSize(10240);
coreConsumerConnectionFactory.setCompressLargeMessage(true);
thanks,
R Ramarajan.
> when artemis streaming enabled then Camel-file component is not able to
> delete the file after its archived in windows
> -
>
> Key: CAMEL-18476
> URL: https://issues.apache.org/jira/browse/CAMEL-18476
> Project: Camel
> Issue Type: Bug
> Components: camel-file
>Affects Versions: 3.14.3, 3.18.1
>Reporter: Ramarajan R
>Priority: Minor
> Attachments: artemis-large-messages-final.zip,
> artemis-large-messages.zip
>
>
> I have used
> [https://github.com/apache/camel-examples/tree/main/examples/artemis-large-messages]
> using AMQ 7.8.0 Broker
> Messages are getting processed but after processing the file is unable to
> delete from source location, tested in more than 1 windows systems facing the
> same
> I am using Camel 3.14.3 and Spring boot 2.6.6 using JAVA DSL,
> tested with Camel 3.18.1 and Spring boot 2.7.3 also
> when running with Camel XML routes are fine but we want to use Java DSL ,
> Kindly help.
> Raising the concern in Zulip chat earlier.
> {{[https://camel.zulipchat.com/#narrow/stream/257298-camel/topic/camel-file.20artemis.20large.20message.20example.20failing.20in.20windows]
> }}{{{}tion-poc/inbox0] o.a.c.c.file.GenericFileOnCompletion : Error during
> commit. Exchange[7D4CFE29E3F7515-0003]. Caused by:
> [org.apache.camel.component.file.GenericFileOperationFailedException - Error
> renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx to
> C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx]{}}}{{{}org.apache.camel.component.file.GenericFileOperationFailedException:
> Error renaming file from C:\opt\file-transfer-solution-poc\inbox0\test.xlsx
> to C:\opt\file-transfer-solution-poc\inbox0\.camel\test.xlsx{}}}
> {{at
> org.apache.camel.component.file.FileOperations.renameFile(FileOperations.java:93)
> ~[camel-file-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.component.file.strategy.GenericFileProcessStrategySupport.renameFile(GenericFileProcessStrategySupport.java:145)
> ~[camel-file-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.component.file.strategy.GenericFileRenameProcessStrategy.commit(GenericFileRenameProcessStrategy.java:121)
> ~[camel-file-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.component.file.GenericFileOnCompletion.processStrategyCommit(GenericFileOnCompletion.java:134)
> ~[camel-file-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.component.file.GenericFileOnCompletion.onCompletion(GenericFileOnCompletion.java:86)
> ~[camel-file-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.component.file.GenericFileOnCompletion.onComplete(GenericFileOnCompletion.java:60)
> ~[camel-file-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.support.UnitOfWorkHelper.doneSynchronization(UnitOfWorkHelper.java:104)
> ~[camel-support-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.support.UnitOfWorkHelper.doneSynchronizations(UnitOfWorkHelper.java:93)
> ~[camel-support-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.impl.engine.DefaultUnitOfWork.done(DefaultUnitOfWork.java:238)
> ~[camel-base-engine-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.support.UnitOfWorkHelper.doneUow(UnitOfWorkHelper.java:61)
> ~[camel-support-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:777)
> ~[camel-base-engine-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.impl.engine.CamelInternalProcessor$UnitOfWorkProcessorAdvice.after(CamelInternalProcessor.java:712)
> ~[camel-base-engine-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.impl.engine.CamelInternalProcessor$AsyncAfterTask.done(CamelInternalProcessor.java:263)
> ~[camel-base-engine-3.14.3.jar:3.14.3]}}
> {{at org.apache.camel.AsyncCallback.run(AsyncCallback.java:44)
> ~[camel-api-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:193)
> ~[camel-base-engine-3.14.3.jar:3.14.3]}}
> {{at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:64)
> ~[camel-base-engine-3.14.3.jar:3.14.3]}}
> {{at
[jira] [Created] (CAMEL-18483) camel-microprofile-health: Routes and consumers health checks are not registered if routes are supervised
James Netherton created CAMEL-18483: --- Summary: camel-microprofile-health: Routes and consumers health checks are not registered if routes are supervised Key: CAMEL-18483 URL: https://issues.apache.org/jira/browse/CAMEL-18483 Project: Camel Issue Type: Bug Components: camel-microprofile-health Affects Versions: 3.18.1, 3.18.2 Reporter: James Netherton Assignee: James Netherton Fix For: 3.18.3, 3.19.0 Some more detail here: https://github.com/apache/camel-quarkus/issues/3989 Due to how CamelMicroProfileHealthCheckRegistry figures out whether it should register the HealthCheckRespository checks it misses ones for routes & consumers if SupervisingRouteController is in use. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-14158) camel-microprofile - Reactive Messaging component
[ https://issues.apache.org/jira/browse/CAMEL-14158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601697#comment-17601697 ] Vinod Pahuja commented on CAMEL-14158: -- is it already done ? https://camel.apache.org/camel-quarkus/next/reference/extensions/smallrye-reactive-messaging.html > camel-microprofile - Reactive Messaging component > - > > Key: CAMEL-14158 > URL: https://issues.apache.org/jira/browse/CAMEL-14158 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Priority: Minor > Fix For: Future > > > We should look at adding a new camel component for MP reactive messaging spec > https://github.com/eclipse/microprofile-reactive-messaging -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-14158) camel-microprofile - Reactive Messaging component
[ https://issues.apache.org/jira/browse/CAMEL-14158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601689#comment-17601689 ] Vinod Pahuja commented on CAMEL-14158: -- There is a SmallRye implementation available [https://smallrye.io/smallrye-reactive-messaging/smallrye-reactive-messaging/3.9/camel/camel.html] Can it be generalized to support this ? > camel-microprofile - Reactive Messaging component > - > > Key: CAMEL-14158 > URL: https://issues.apache.org/jira/browse/CAMEL-14158 > Project: Camel > Issue Type: New Feature >Reporter: Claus Ibsen >Priority: Minor > Fix For: Future > > > We should look at adding a new camel component for MP reactive messaging spec > https://github.com/eclipse/microprofile-reactive-messaging -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CAMEL-18327) camel-kafka: Kafka consumer closes when it is paused
[
https://issues.apache.org/jira/browse/CAMEL-18327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17601662#comment-17601662
]
Otavio Rodolfo Piske commented on CAMEL-18327:
--
[~geek.rupam] would you mind sending a PR with your proposed change, please?
> 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] [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=17601653#comment-17601653 ] Devansh Arora edited comment on CAMEL-18470 at 9/8/22 6:13 AM: --- Hey Claus, If you have already found the cause/fix for the issue can you share that with us. We can merge it in our local copy of camel-rabbitmq 3.18.1 and use it in our projects. We want to be on latest camel versions as we are using multiple other components of camel. Thanks & Regards was (Author: devansharor...@gmail.com): Hey Claus, If you have already found the cause/fix for the issue can you share that with us. We can merge it in our local copy of camel-rabbitmq 3.18.1 and use it in our projects. We want to be on latest camel versions as we are using multiple other components of camel. Thanks & Regards > 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 >
[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=17601653#comment-17601653 ] Devansh Arora commented on CAMEL-18470: --- Hey Claus, If you have already found the cause/fix for the issue can you share that with us. We can merge it in our local copy of camel-rabbitmq 3.18.1 and use it in our projects. We want to be on latest camel versions as we are using multiple other components of camel. Thanks & Regards > 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 >
