Camel InterceptFrom拦截器startTime值不变问题咨询

The core issue here is when the header value gets evaluated in your initial setup. When you call setHeader() directly within RouteBuilder.configure(), Camel computes that value once during route initialization (when the Camel context starts up), not for every incoming exchange. That’s why your startTime header never changes—it’s stuck with the timestamp from when the route first launched.

Let’s break this down: #

• The configure() method runs only once, at Camel context startup. Any constant value or static calculation you pass to setHeader() here is resolved immediately and reused for every exchange intercepted.
• For example, if you had code like this:

  interceptFrom()
      .setHeader("startTime", constant(System.currentTimeMillis()));
  

  The System.currentTimeMillis() call executes once when the route is built, so all exchanges end up with the same fixed timestamp.

Why moving to a Bean worked: #

When you refactored to use a Bean, you’re telling Camel to invoke a method per exchange. That method runs every time an exchange is intercepted, so it calculates the current timestamp dynamically for each request—exactly what you need to track processing duration accurately.

Correct alternatives to your initial approach: #

Besides using a Bean, you can also use a Processor or a dynamic expression to ensure the value is computed per exchange:

1. Using a Processor:

   interceptFrom()
       .process(exchange -> {
           exchange.getIn().setHeader("startTime", System.currentTimeMillis());
       });
   

2. Using a dynamic expression (like Simple):
   If you just need a human-readable timestamp, Camel’s Simple language can evaluate it dynamically for each exchange:

   interceptFrom()
       .setHeader("startTime", simple("${date:now:yyyy-MM-dd HH:mm:ss.SSS}"));
   

   (Note: For precise epoch milliseconds, a Processor or Bean is still preferable, as Simple doesn’t directly return epoch values without a custom formatter.)

Key takeaway: #

Always remember that configuration code in RouteBuilder.configure() runs once at startup. To perform actions that need to execute per exchange (like setting a dynamic timestamp), use a Processor, Bean, or a dynamic expression that Camel evaluates at runtime for each message.

内容的提问来源于stack exchange，提问作者pointerness