Hi
Yes it sounds like that's a good candidate for the problem.
Camel 2.x is EOL soon and we only fix very serious security issues in 2.x.
So you can patch the code yourself, or do not use the transferExchange
option (that option is also not recommended to use - Java object
serialization is bad).
Dear community,
We have 2 camel services: camel-A and camel-B and both of them use camel-jms
component.
Camel-A is the JMS producer with:
Camel-B is the JMS consumer with:
After stress testing, we got camel-B OOM exception and found the memory leak
root cause is DefaultInflightRepository:
Hi Tobias,
To get better response I advise to tell a bit more about the setup, the
challenges and the goals you are facing and where it relates to Camel. I
think Cosmos provide a compatibility API for MongoDB mapping Containers
(Collections at MongoDB) and Items (Documents at MongboDB) with each o
Hi Claus,
Great - thanks for the quick fix!
Best Regards, Andreas
Mit freundlichen Grüßen / Best regards
Andreas Klug
Middleware Development (CI/XDM1)
Robert Bosch GmbH | Postfach 30 02 20 | 70442 Stuttgart | GERMANY |
www.bosch.com
Sitz: Stuttgart, Registergericht: Amtsgericht Stuttgart, HR
Hi all,
we use apache camel in ms azure + microservices (Version 3.7, AKS, k8s)and have
legacy code.
In legacy code (docker-compose) we used mongoDB.
What could the best way to migrate to cosmodb with mongoAPI
best regards
Tobias
Hi
I took a look and found the bug, so I created a ticket
https://issues.apache.org/jira/browse/CAMEL-17225
On Tue, Nov 23, 2021 at 2:29 PM Claus Ibsen wrote:
>
> Hi
>
> Ah okay, so its that rarely used or/and builder that we only have in Java DSL.
> Can you create a JIRA ticket. That or thingy
Hi
Ah okay, so its that rarely used or/and builder that we only have in Java DSL.
Can you create a JIRA ticket. That or thingy need likely some init to
prepare the simple language.
On Mon, Nov 22, 2021 at 12:22 PM Klug Andreas (CI/XDM1)
wrote:
>
> Hello everyone,
>
> Can anybody pls. give me a h
