Hi 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 ...................................... Silverbullet Skovsgårdsvænget 21 8362 Hørning Tlf. +45 2962 7576 Web: www.silverbullet.dk -----Original Message----- From: dkozic [mailto:[EMAIL PROTECTED] Sent: 22. august 2008 09:53 To: [email protected] Subject: Tracing problem Hi, I have folowing route from("timer://whcTimer?period=20000&delay=10000").setBody(constant("Test10")).processRef("systemOutProcessor").to( "seda:whcLog"); from("seda:whcLog").to("log:asw.someLogger?level=DEBUG&showHeaders=true"); 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: http://www.nabble.com/Tracing-problem-tp19103013s22882p19103013.html Sent from the Camel - Users mailing list archive at Nabble.com.
