camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject Re: Timers stop firing after certain unpredictable interval
Date Fri, 04 Feb 2011 15:02:27 GMT
Dont know what's causing this.

Generally the timer component would stop firing if it exist the run
method. Which it would only do if a java.lang.Error was thrown (not
caught).

Quartz ought to be resilient and fire according to the schedule.

So I think it fires but there is some issue in your bean or Camel route.
What does your route do?

As you can see the TRACER logs the firing of the event.


On Fri, Feb 4, 2011 at 3:45 PM, s2010in <samir.sumant@mphasis.com> wrote:
>
> I tried using exception handling now, there is no exception thrown for a
> reference also displaying a log snippet
>
> onException(Throwable.class)
>                .useOriginalMessage()
>                .handled(true)
> ...
>
> From logs you can see after 8:26 onwards The bean ref method of test service
> is never called by timer, and after 8:36 logs wont even display timer, most
> interesting part is now all the other routes also come at standstill
>
> 2011-02-04 08:19:00,078 [DefaultQuartzScheduler_Worker-1] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-2 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8+
> 2011-02-04 08:19:01,984 [DefaultQuartzScheduler_Worker-1] INFO  TestService
> - Return Code [0] Return Message [Test Message
> 2011-02-04 08:20:00,015 [DefaultQuartzScheduler_Worker-2] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-4 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8+
> 2011-02-04 08:20:00,562 [DefaultQuartzScheduler_Worker-2] INFO  TestService
> - Return Code [0] Return Message [Test Message
> 2011-02-04 08:21:00,015 [DefaultQuartzScheduler_Worker-3] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-6 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8+
> 2011-02-04 08:21:00,562 [DefaultQuartzScheduler_Worker-3] INFO  TestService
> - Return Code [0] Return Message [Test Message
> 2011-02-04 08:22:00,015 [DefaultQuartzScheduler_Worker-4] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-8 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8+
> 2011-02-04 08:22:00,468 [DefaultQuartzScheduler_Worker-4] INFO  TestService
> - Return Code [0] Return Message [Test Message
> 2011-02-04 08:23:00,015 [DefaultQuartzScheduler_Worker-5] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-10 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8
> 2011-02-04 08:23:00,687 [DefaultQuartzScheduler_Worker-5] INFO  TestService
> - Return Code [0] Return Message [Test Message
> 2011-02-04 08:24:00,015 [DefaultQuartzScheduler_Worker-6] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-12 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8
> 2011-02-04 08:24:00,578 [DefaultQuartzScheduler_Worker-6] INFO  TestService
> - Return Code [0] Return Message [Test Message
> 2011-02-04 08:25:00,015 [DefaultQuartzScheduler_Worker-7] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-14 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8
> 2011-02-04 08:25:00,484 [DefaultQuartzScheduler_Worker-7] INFO  TestService
> - Return Code [0] Return Message [Test Message
> 2011-02-04 08:26:00,015 [DefaultQuartzScheduler_Worker-8] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-16 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8
> 2011-02-04 08:26:00,500 [DefaultQuartzScheduler_Worker-8] INFO  TestService
> - Return Code [0] Return Message [Test Message
> 2011-02-04 08:27:00,015 [DefaultQuartzScheduler_Worker-9] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-18 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8
> 2011-02-04 08:28:00,015 [DefaultQuartzScheduler_Worker-10] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-20 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-
> 2011-02-04 08:29:00,015 [DefaultQuartzScheduler_Worker-1] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-22 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8
> 2011-02-04 08:30:00,015 [DefaultQuartzScheduler_Worker-2] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-24 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8
> 2011-02-04 08:31:00,015 [DefaultQuartzScheduler_Worker-3] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-26 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8
> 2011-02-04 08:32:00,015 [DefaultQuartzScheduler_Worker-4] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-28 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8
> 2011-02-04 08:33:00,015 [DefaultQuartzScheduler_Worker-5] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-30 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8
> 2011-02-04 08:34:00,015 [DefaultQuartzScheduler_Worker-6] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-32 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8
> 2011-02-04 08:35:00,015 [DefaultQuartzScheduler_Worker-7] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-34 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8
> 2011-02-04 08:36:00,015 [DefaultQuartzScheduler_Worker-8] INFO  Tracer  -
> ID-xxxx-1508-1296829074500-0-36 >>> (route_test)
> from(quartz://timerName?cron=0+*+18-8
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Timers-stop-firing-after-certain-unpredictable-interval-tp3370457p3371081.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>



-- 
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Mime
View raw message