Hi
Do you see any exceptions in the log as the TimerConsumer does a try
.. catch and logs the exception.
} catch (Exception e) {
getExceptionHandler().handleException("Error processing
exchange", exchange, exchange.getException());
}
My only thought could be that something more serious is thrown such as
a Error which isn't caught. So we may have to use Throwable to ensure
all is caught.
On Fri, Feb 4, 2011 at 5:50 AM, s2010in <samir.sum...@mphasis.com> wrote:
>
> Hello,
>
> There is a issue with using timers, I have tried both timer and quartz timer
> to process a spring bean method using Camel 2.4.0 and Camel 2.6.0 on tomcat
> 6 container using spring
>
> Observation is timer stops processing after certain unpredictable interval,
> the service method is not getting called anymore, along with this all other
> routes also do not respond to events and messages keep piling up.
>
> This is causing entire processing to come at standstill unless server is
> restarted. If the timer route is removed things work well as they are
> supposed to be.
>
> Endpoint for Quartz: quartz://timerName?cron=0+*+18-8+?+*+MON-SAT
> Endpoint for Timer: timer://foo?fixedRate=true&period=60000
>
> Furthermore a smaller issue which has already been raised in this forum is
> these timers cause tomcat to hang and it wont shutdown gracefully.
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Timers-stop-firing-after-certain-unpredictable-interval-tp3370457p3370457.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Claus Ibsen
-----------------
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
