camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen">
Subject RE: Tracing problem
Date Fri, 22 Aug 2008 09:31:39 GMT

There is a bug in tracer when the payload is null. And since you kickstart from a timer the
body is in fact null.

So you can not use the timer with the tracer.

It is of course fixed in 1.5-SNAPSHOT

Med venlig hilsen
Claus Ibsen
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
-----Original Message-----
From: dkozic [] 
Sent: 22. august 2008 09:53
Subject: Tracing problem


I have folowing route



systemOutProcessor is simple processor that output message to System.out.

Console output from this route is:

Entered SystemOutProcessor.
2008-08-22 09:40:06,859 [seda:whcLog thread:1] DEBUG asw.someLogger:73  -
Exchange[Headers:{}, BodyType:String, Body:Test10]

Thais OK as expected.

But when I turn on tracing with:

getContext().addInterceptStrategy(new Tracer());

or with trace="true" parameter in spring.xml

and run, nothing happens. There is no output on console at all.

I am running Camel 1.4 on jdk1.5.0_10 inside Tomcat, Eclipse 3.3 on Windows
XP 2002 SP1.

I am not using maven. Maybe some library is missing? I have log4j-1.2.14.jar
in WEB-INF/lib folder.

Thanks in advance

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message