camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Zhemzhitsky (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4928) Async API support by the Timer component
Date Mon, 23 Jan 2012 19:43:40 GMT


Sergey Zhemzhitsky commented on CAMEL-4928:

I noticed that *synchronous=false* is used primarily by producers and *asyncConsumer* parameter
exists only in jms consumer, so I suppose that *synchronous* parameter can be used to determine
whether both producers or consumers should be synchronous. (Maybe jms consumer should consider
using of *synchronous* parameter instead of *asyncConsumer* to prevent introduction of new
parameters for the same thing in other components)

So, the patch was replaced to involve usage of *synchronous* parameter.
> Async API support by the Timer component
> ----------------------------------------
>                 Key: CAMEL-4928
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.9.0
>            Reporter: Sergey Zhemzhitsky
>              Labels: timer
>         Attachments: CAMEL-4928.patch
> It would be great to have timer component support asynchronous API.
> Such a feature can be useful when timer component generates events which must be processed
by multiple threads. 
> Current implementation of the timer component makes a blocking call so the usage of thread
pools hardly possible to process multiple timer event simultaneously.
> {code:title=Sample}
> from("timer:start")
>     .threads(1, 5)
>     .to("bean:very-long-operation");
> {code}

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message