Are you using a thread pool ?
Its the JDK which controls and executes the tasks and thus its up to
how the JDK handles this.


On Mon, Oct 31, 2011 at 7:09 PM, ebinsingh
<ebenezer.si...@verizonwireless.com> wrote:
> Thanks a lot all of you.
>
> As you may see the code in above in this thread, I am splitting based on the
> new line token and sending it to a bean.
>
> I noticed som gap in the processing times. I 5 messages beeing processed in
> a single millisecond and there is a gap of 15 milliseconds before the next 5
> message's are sent to the bean  .. this pattern repeats itself.
>
> Any reason for this time delay. I went through the Splitter and streaming
> and do not see any specific property i could set for continous streaming.
>
> 2011-10-31 13:42:43,874 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting
> bean invocation result on the IN message: <Some message>
> 2011-10-31 13:42:43,874 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting
> bean invocation result on the IN message: <Some message>
> 2011-10-31 13:42:43,*874* DEBUG [pool-1-thread-1] bean.BeanProcessor -
> Setting bean invocation result on the IN message: <Some message>
> 2011-10-31 13:42:43,*890* DEBUG [pool-1-thread-1] bean.BeanProcessor -
> Setting bean invocation result on the IN message: <Some message>
> 2011-10-31 13:42:43,890 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting
> bean invocation result on the IN message: <Some message>
> 2011-10-31 13:42:43,890 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting
> bean invocation result on the IN message: <Some message>
> 2011-10-31 13:42:43,890 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting
> bean invocation result on the IN message: <Some message>
> 2011-10-31 13:42:43,890 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting
> bean invocation result on the IN message: <Some message>
> 2011-10-31 13:42:43,890 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting
> bean invocation result on the IN message: <Some message>
> 2011-10-31 13:42:43,890 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting
> bean invocation result on the IN message: <Some message>
> 2011-10-31 13:42:43,890 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting
> bean invocation result on the IN message: <Some message>
> 2011-10-31 13:42:43,*890* DEBUG [pool-1-thread-1] bean.BeanProcessor -
> Setting bean invocation result on the IN message: <Some message>
> 2011-10-31 13:42:43,*905* DEBUG [pool-1-thread-1] bean.BeanProcessor -
> Setting bean invocation result on the IN message: <Some message>
> 2011-10-31 13:42:43,905 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting
> bean invocation result on the IN message: <Some message>
> 2011-10-31 13:42:43,905 DEBUG [pool-1-thread-1] bean.BeanProcessor - Setting
> bean invocation result on the IN message: <Some message>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Spliter-in-Camel-tp4940967p4953111.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, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/

Reply via email to