Seems that I found the difference, but have no solution yet.
Sorry, I wasn't specific enough at first.
Instead of starting the app using org.apache.camel.spring.Main class, I'm
starting it just using the Spring context:
public class App {
public static void main(String[] args) {
new ClassPathXmlApplicationContext("config.xml").start();
}
}
And the route class:
public class Route extends SpringRouteBuilder {
public void configure() throws Exception {
onException(RuntimeCamelException.class);
errorHandler(loggingErrorHandler(getClass().getName()));
from("timer:hello?daemon=true&period=2000").to("log:myLogger?level=INFO");
}
}
The route triggers only once, producing the following output:
May 4, 2009 8:07:56 PM org.apache.camel.impl.DefaultCamelContext doStart
INFO: Apache Camel 2.0-M1 (CamelContext:camel) is starting
May 4, 2009 8:07:57 PM org.apache.camel.impl.DefaultCamelContext doStart
INFO: Apache Camel 2.0-M1 (CamelContext:camel) started
May 4, 2009 8:07:57 PM org.apache.camel.processor.Logger process
INFO: Exchange[BodyType:null, Body:null]
This is with 2.0-M1. Will try the SNAPSHOT version a bit later.
Claus Ibsen-2 wrote:
>
> On Mon, May 4, 2009 at 6:06 PM, arhan <[email protected]> wrote:
>>
>> Hi!
>>
>> I tried it with 2.0-M1
> Well I am surprised. The unit test I added is 2.0-SNAPSHOT.
>
> How do you start/run Camel? Could be something there. And what is
> logged in the output when you say it "hangs"?
> And how have you defined your bean?
>
> You can also try out the SNAPSHOT version. A m2 is scheduled to be
> build and released soon. The person doing this is however a bit tight
> work other work.
> But there is a topic on the camel dev forum about that release being
> in progress.
>
> The snapshot can be downloaded and/or use maven. See this page:
> http://camel.apache.org/download.html
>
>>
>>
>> Claus Ibsen-2 wrote:
>>>
>>>
>>> I just added unit test in Camel 2.0 that looks like you route and it
>>> works:
>>> http://svn.apache.org/viewvc?view=rev&revision=771312
>>>
>>> What version of Camel are you using?
>>>
>>> The reason could be the body message is null, as the timer does not
>>> create any input message.
>>> There was such a bug in Camel 1.3/1.4 when using the tracer.
>>>
>>> You can try adding
>>> .setBody(constant(""))
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Timer-endpoint-and-errorHandler-tp23366970p23371453.html
>> Sent from the Camel - Users (activemq) mailing list archive at
>> Nabble.com.
>>
>>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
> Apache Camel Reference Card:
> http://refcardz.dzone.com/refcardz/enterprise-integration
>
>
--
View this message in context:
http://www.nabble.com/Timer-endpoint-and-errorHandler-tp23366970p23372552.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
