Hi Gerda
Thanks for sharing your solution.
I guess users like you whom dynamic add and remove routes more frequently
could be affected by this deadlock when doing concurrent add and removes.
On top of my head one aspect that could lead to a problem is that if your
routes are using the same route
Hi Claus,
Yes, we're now doing our own locking - essentially just straightening
out the order of locks Camel will need later on in our code.
It feels wrong, though: CamelContext is already putting a lot of
effort into protecting addRoutes/removeRoute-calls.
Streamlining the order in which locks ar
Hi
Do you own locking if you do concurrent model changes to Camel
On Thu, Sep 1, 2022 at 6:21 PM Gerda Ilger wrote:
> Dear Camel Community,
>
> We ran into a deadlock when concurrently adding and removing routes.
>
> We're dynamically adding and removing routes, whose (ftp) consumers
> sometime
