You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by bpinto <br...@hotmail.com> on 2013/09/06 02:30:23 UTC
Processing Asynchronous Interceptors
Hi,
I am facing slow performance on an Interceptor processor. This is because
the interceptor is used to log messages at every step. The interceptor is
initialized using DelegateAsyncProcessor(Processor) and adding it to
CamelContext.AddInterceptStrategy.
Questions
1. Does using DelegateAsyncProcessor mean the processor will be executed
asynchronously on a separate thread?
2. Is understanding right in the following statement. "If the intercept is
being processed asynchronously, it will still wait for all the async
processors to complete before completing the Exchange"
Thanks,
Brian
--
View this message in context: http://camel.465427.n5.nabble.com/Processing-Asynchronous-Interceptors-tp5738810.html
Sent from the Camel Development mailing list archive at Nabble.com.
Re: Processing Asynchronous Interceptors
Posted by bpinto <br...@hotmail.com>.
Thanks for the reply Claus. That explains the behavior I have been seeing
Essentially, I was expecting wrongly of asyncprocessors to kick off a
separate
thread and continue processing the exchange.
Thanks,
Brian
--
View this message in context: http://camel.465427.n5.nabble.com/Processing-Asynchronous-Interceptors-tp5738810p5739067.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Processing Asynchronous Interceptors
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
Ad 1)
No. See link below.
Ad 2)
See more details here:
http://camel.apache.org/asynchronous-processing.html
On Tue, Sep 10, 2013 at 1:52 AM, bpinto <br...@hotmail.com> wrote:
> Hi,
>
> Still awaiting any suggestions/information on the question.
>
> At the moment working around the problem by customizing processor handling
> in already initiated threads.
>
> Regards,
> Brian
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Processing-Asynchronous-Interceptors-tp5738810p5738981.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
Re: Processing Asynchronous Interceptors
Posted by bpinto <br...@hotmail.com>.
Hi,
Still awaiting any suggestions/information on the question.
At the moment working around the problem by customizing processor handling
in already initiated threads.
Regards,
Brian
--
View this message in context: http://camel.465427.n5.nabble.com/Processing-Asynchronous-Interceptors-tp5738810p5738981.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Processing Asynchronous Interceptors
Posted by bpinto <br...@hotmail.com>.
My apologies, moved the topic to the users forum
--
View this message in context: http://camel.465427.n5.nabble.com/Processing-Asynchronous-Interceptors-tp5738810p5738851.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Processing Asynchronous Interceptors
Posted by Bilgin Ibryam <bi...@gmail.com>.
The best place to ask these kind of questions and get answer is the users
list.
Cheers
Bilgin
On 6 September 2013 01:30, bpinto <br...@hotmail.com> wrote:
> Hi,
>
> I am facing slow performance on an Interceptor processor. This is because
> the interceptor is used to log messages at every step. The interceptor is
> initialized using DelegateAsyncProcessor(Processor) and adding it to
> CamelContext.AddInterceptStrategy.
>
> Questions
> 1. Does using DelegateAsyncProcessor mean the processor will be executed
> asynchronously on a separate thread?
> 2. Is understanding right in the following statement. "If the intercept is
> being processed asynchronously, it will still wait for all the async
> processors to complete before completing the Exchange"
>
> Thanks,
> Brian
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Processing-Asynchronous-Interceptors-tp5738810.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>