Hi
What is your use-case for the reason you want to do this?
You should often not do something like this, so want to hear more about why.
And what Camel version and what resources are you using for transaction?
On Sun, Dec 29, 2019 at 12:52 PM Mikhail Lukyanov wrote:
>
> Hello everyone
> Tell me
Hi, Claus.
I have the following reasons
1) For some reason, the exchange freezes (error, something is not
available) and the message being processed becomes blocked. I want the user
to be able to complete this stuck exchange so that the blocked message is
released and other consumers can start pr
Hi
Ah okay so its not a transaction (eg using a tx manager with jms/jdbc
etc). So that is a bit different.
You can take a look in JMX in the services tree of Camel there is a
AsyncProcessorAwaitManager mbean. It has details if there is a thread
stuck somewhere, which you can then force to free up
Thanks for the information Claus, yes, from the beginning I did not
correctly formulate my question.
понедельник, 30 декабря 2019 г. пользователь Claus Ibsen <
claus.ib...@gmail.com> написал:
> Hi
>
> Ah okay so its not a transaction (eg using a tx manager with jms/jdbc
> etc). So that is a bit d
TL;DR: I'm trying to use a single logger for both my routes (i.e. the Log EIP)
and in my components. In my routes, I would like the displayed log name to be
the Route ID, and in the components it should be the class name.
Ok, it's about time I solved this one once and for all...
I create my Ca
