-0: We are using it a lot. It is very convenient and works great for our
use-cases.
Am 22.03.2021 um 10:45 schrieb Claus Ibsen:
Hi
In Camel 3.x and in a more and more reactive world, then MDC logging
is becoming a more and more bad practice.
That MDC context is thread bound, and that informati
Hi Claus,
aren't there libraries that implement reactive context?
Reactive contexts could replace the thread contexts and hold the MDC
instance, no?
Regards,
Ralf
On 3/22/21 10:45 AM, Claus Ibsen wrote:
Hi
In Camel 3.x and in a more and more reactive world, then MDC logging
is becoming a m
+0
Regards
JB
> Le 22 mars 2021 à 10:45, Claus Ibsen a écrit :
>
> Hi
>
> In Camel 3.x and in a more and more reactive world, then MDC logging
> is becoming a more and more bad practice.
>
> That MDC context is thread bound, and that information needs to be
> transferred between MDC thread bo
+1
Il lun 22 mar 2021, 10:45 Claus Ibsen ha scritto:
> Hi
>
> In Camel 3.x and in a more and more reactive world, then MDC logging
> is becoming a more and more bad practice.
>
> That MDC context is thread bound, and that information needs to be
> transferred between MDC thread bound context whe
Hi
In Camel 3.x and in a more and more reactive world, then MDC logging
is becoming a more and more bad practice.
That MDC context is thread bound, and that information needs to be
transferred between MDC thread bound context when Camel routes
messages, both within its own routing engine, but als
