camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject [FEEDBACK] - The small details in the logs when stopping Camel
Date Fri, 15 Jun 2012 15:29:43 GMT

Camel 2.10 is about to be cut soon.

And there is a few changes in the logs when Camel stops.

There is a new TypeConverterRegistry utilization log, that prints stats
from the type converter.

The uptime is now on the same line as the last log line

[                      Thread-3] DefaultTypeConverter           INFO
 TypeConverterRegistry utilization[attempts=67, hits=67, misses=0,
failures=0] mappings[total=175, misses=0]
[                      Thread-3] DefaultCamelContext            INFO
 Apache Camel 2.10-SNAPSHOT (CamelContext: camel-1) is shutdown in 0.088
seconds. Uptime 26.814 seconds.

Ad 1)
The type converter is used a lot in Camel. And since this works both
implicit and explicit, then you may not be aware of the utilization of the
type conversion. For example you may have many missed attempts, which
impacts a little.

I set this log at INFO level so I could easier run all the Camel tests, and
then grep the logs, and find if there was a lot of misses etc.

We could lower this to DEBUG level, if people would think the log line
confuses people more, eg operations people looking at this log line etc.

Ad 2)
I moved the Uptime to the last log line. We can move it back to just before
the last log line if people want it on its own log line.

Any thoughts?

Claus Ibsen
Twitter: davsclaus, fusenews
Author of Camel in Action:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message