Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Information Provided
-
3.12.0, 3.14.2, 3.15.0
-
None
-
None
-
Unknown
Description
In version 3.12.0 the RedeliveryErrorHandler doesn't log the BreadcrumbId and RouteId anymore.
In version 3.12.0 I would see:
2022-02-17 16:47:31,701 INFO o.a.c.p.e.DeadLetterChannel - [BC ] - [RI ] - Failed delivery for (MessageId: ID:activemq-6bbb4dbb68-cr62z-39269-1645104552893-5:2:1:1:8 on ExchangeId: 92F0FAC801928B8-0000000000000000). On delivery attempt: 0 caught: java.lang.Exception: Some Bug
Where as on version 3.11.4 the following is being displayed
2022-02-17 17:20:24,820 INFO o.a.c.p.e.DeadLetterChannel - [BC 331601E40883DAE-0000000000000000] - [RI CamelMDCTest1] - Failed delivery for (MessageId: ID:activemq-6bbb4dbb68-cr62z-39269-1645104552893-5:3:1:1:1 on ExchangeId: 331601E40883DAE-0000000000000000). On delivery attempt: 0 caught: java.lang.Exception: Some Bug
The following is my logging formatting:
<pattern>%d %-5level %logger{36} - [BC %X{camel.breadcrumbId}] - [RI %X{camel.routeId}] - %msg%n</pattern>
I think this has to do with CAMEL-17009 for cleaning the MDC out more often now.
Attachments
Issue Links
- is caused by
-
CAMEL-17009 camel-core - Camel does not clear MDC correctly
- Resolved
- is related to
-
CAMEL-17514 BreadcrumbId MDC Value not set even MDCLogging is true during ErrorHandling Processor
- Resolved
- relates to
-
CAMEL-17889 camel.routeId removed from MDCs
- Resolved