In your test, do exceptions happen? How many inside the 15.000-line file?
What does the direct:AEDFormatException route do? Please post its code. It
could be the reason for slowness.
Thanks.
On 12 Mar 2013 08:23, "Jean Francois LE BESCONT"
wrote:
> Hey !
>
> I have found a strange thing with th
Btw - It looks like you decided to go with the approach I suggested. First
enrich, then split.
Is the aggregation strategy storing the SQL results in a property, which
you access later?
On 12 Mar 2013 08:23, "Jean Francois LE BESCONT"
wrote:
> Hey !
>
> I have found a strange thing with the doTr
Yes Raul , I opted for your suggestion,and it works fine ! Yes I put it in
a property and acces it later ( has you suggest :)
OH I ommited to say that my file contains only valid line, the
direct:AEDFormatException
which is a reject route is never call for the moment.
2013/3/12 Raul Kripalani
Ok.
Obviously there will be more overhead in capturing the exception and
re-throwing under a different exception type, but it should not make the
route 12x slower. Something's going on.
Do you have any additional error handlers? onExceptions, errorHandlers,
etc.?
Could you paste your entire conf
So you append each invalid record to a file (direct:AEDFormatException).
For *each* rejected line, this process occurs: the FileInputStream is
opened, positioned at the end, the line is written, the
FileInputStream is closed. That could explain some of the slowness.
Let's gather some performance
Have a look at the following tests:
https://github.com/muellerc/apachecon-na-2013/tree/master/file-component/src/test/java/org/apache/cmueller/camel/apachecon/na2013
The are performance comparison between the different possibilities...
Best,
Christian
On Thu, Mar 14, 2013 at 12:53 AM, Raul Kripa
