You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by bhanuprakash <sb...@anz.com> on 2013/04/15 12:49:35 UTC
Quickfix to Direct message loss
I fired 100 FIX messages with a injector with 10 millisecond gap inbetween.
The routes looked like this
<route 1 >
<from <b>quickfix* >
<to <b>direct*:process >
</route 1>
<route 2>
<from <b>direct*:process>
<to <b>bean*:transform>
</route2>
I am able to recieve 75-80 messages everytime I test this.
But , when I do this
<route 1>
<from <b>quickfix*>
<to <b>file*:C:\trades>
<route 1>
The directory does recieve 100 files. So I know its not an issue with Camel
quickfix component.
I moved to *seda* from *direct* and the issue got resolved , but not able to
find the root cause for this.
Appreciate any help .
Thanks
--
View this message in context: http://camel.465427.n5.nabble.com/Quickfix-to-Direct-message-loss-tp5730891.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Quickfix to Direct message loss
Posted by Willem jiang <wi...@gmail.com>.
I'm not a quick fix expert, but I can tell you the difference between the direct and seda component.
Direct component just provide the sync invocation, the seda can leverage the Camel Async engine to execute the processes with multiple threads and it is more effective.
Can you try to set the interval time a bit longer? In this way , I guess you will get few message lost.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Tuesday, April 16, 2013 at 10:48 AM, bhanuprakash wrote:
> Thank you for responding.
>
> I am using Camel 2.10.1 version.
>
> My bean transforms FIX msg from one format to another.
>
> But , even if I remove the bean and define the route like this
>
> <route 1>
> <from quickfix >
> <to direct:process>
> </route 1>
>
> <route 2>
> <from direct:process>
> <to file C:/trades>
> </route 2>
>
> Still , I receive 75-80 messages.
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Quickfix-to-Direct-message-loss-tp5730893p5730945.html
> Sent from the Camel - Users mailing list archive at Nabble.com (http://Nabble.com).
>
Re: Quickfix to Direct message loss
Posted by bhanuprakash <sb...@anz.com>.
Thank you for responding.
I am using Camel 2.10.1 version.
My bean transforms FIX msg from one format to another.
But , even if I remove the bean and define the route like this
<route 1>
<from quickfix >
<to direct:process>
</route 1>
<route 2>
<from direct:process>
<to file C:/trades>
</route 2>
Still , I receive 75-80 messages.
--
View this message in context: http://camel.465427.n5.nabble.com/Quickfix-to-Direct-message-loss-tp5730893p5730945.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Quickfix to Direct message loss
Posted by Claus Ibsen <cl...@gmail.com>.
What version of Camel do you use?
And what does your bean do?
On Mon, Apr 15, 2013 at 12:49 PM, bhanuprakash <sb...@anz.com> wrote:
> I fired 100 FIX messages with a injector with 10 millisecond gap inbetween.
>
> The routes looked like this
>
> <route 1 >
> <from <b>quickfix* >
> <to <b>direct*:process >
> </route 1>
>
> <route 2>
> <from <b>direct*:process>
> <to <b>bean*:transform>
> </route2>
>
> I am able to recieve 75-80 messages everytime I test this.
>
> But , when I do this
>
> <route 1>
> <from <b>quickfix*>
> <to <b>file*:C:\trades>
> <route 1>
>
> The directory does recieve 100 files. So I know its not an issue with Camel
> quickfix component.
>
> I moved to *seda* from *direct* and the issue got resolved , but not able to
> find the root cause for this.
>
> Appreciate any help .
>
>
> Thanks
>
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Quickfix-to-Direct-message-loss-tp5730891.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen