Alright... thank you for the reply! Really appreciate it.
Do you think this is clear enough in the current documentation? To me, this
part is rather confusing:
IMPORTANT: this will only reduce the endpoint cache of the toD that has a
chance of being reused in case a message is routed with the sa
Alright, understood. Thanks!
Em ter., 10 de jun. de 2025, 10:51, Claus Ibsen
escreveu:
> Hi
>
> Its either
>
> a)
> Do not use all those HTTP_XXX headers with toD.
> Instead put dynamic parts in the toD uri with {{xxx}} placeholders for
> headers / variables etc.
>
> b)
> Or use a single static
Hi
Its either
a)
Do not use all those HTTP_XXX headers with toD.
Instead put dynamic parts in the toD uri with {{xxx}} placeholders for
headers / variables etc.
b)
Or use a single static to and only HTTP_XXX headers
On Tue, Jun 10, 2025 at 2:27 PM Gabriel Souza <
gabrielaraujodesouz...@gmail.
Hi
This is expected behaviour as toD needs to know the component in use before
it can do optimizations. And that is why it works correctly when you start
with "http:..." then Camel knows its the http component and can do pre-
optimizations.
On Fri, May 23, 2025 at 2:17 PM Gabriel Souza <
gabriel
Hi, did someone get to see this?
Em sex., 23 de mai. de 2025, 09:11, Gabriel Souza <
gabrielaraujodesouz...@gmail.com> escreveu:
> Hello, I want to ask a question about the usage of the .toD EIP. Recently,
> we had a memory leak problem due to a misuse of .toD. Our URL had a path
> parameter that
Hello, I want to ask a question about the usage of the .toD EIP. Recently,
we had a memory leak problem due to a misuse of .toD. Our URL had a path
parameter that was dynamically computed, and we found that each request was
kept forever inside camelContext's attribute "routesToStop".
The URL is in
