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). >
