Hi Claus, Thanks for the suggestion. I tested the sample code with Camel Quarkus 3.2 and 3.8. The result logs are the same.
________________________________ 发件人: Claus Ibsen <claus.ib...@gmail.com> 发送时间: 2024年7月11日 15:24 收件人: users@camel.apache.org <users@camel.apache.org> 主题: Re: MDCUnitOfWork not working with vert.x-eventloop-thread Hi This is an old Quarkus version and we dont support this CAMEL VERSION QUARKUS JDK KIND RELEASED SUPPORTED UNTIL 3.18.6 2.13.3 11 LTS April 2023 July 2023 You can try latest v4 Camel version and see what happens there. On Thu, Jul 11, 2024 at 7:58 AM _ Jane <belief...@hotmail.com> wrote: > Dear community, > > When I using Camel Quarkus and use camel-knative event producer, the > thread name is vert.x-eventloop-thread-xxx and the fields from > MDCUnitOfWork (like camel.routeId) is missing. Is there any special > configuration needed to show the MDCUnitOfWork fields in my log? Thanks! > > The Camel Quarkus version is 2.13.3 and here is the sample code: > > from("timer://foo?fixedRate=true&period=60000") > .routeId("route_timer_test") > .setBody(constant("test event")) > .setHeader(CloudEvent.CAMEL_CLOUD_EVENT_SOURCE, constant("test-route")) > .log("there is camel.routeId") > .to("knative:event/broker-test") > .log("there isn't camel.routeId") > > The log format config is "quarkus.log.console.format=%d{yyyy-MM-dd > HH:mm:ss,SSS} %-5p [%c{3.}] (%t) - %X{camel.routeId} - %s%e%n" and the > result log is: > > 2024-07-11 13:53:51,273 INFO [route_timer_test] (Camel (test-route) > thread #2 - timer://foo) - route_timer_test- there is camel.routeId > 2024-07-11 13:53:51,401 INFO [route_timer_test] > (vert.x-eventloop-thread-0) - - there isn't camel.routeId > > -- Claus Ibsen ----------------- @davsclaus Camel in Action 2: https://www.manning.com/ibsen2