I had the same issue today.
It was simply linked to the file encoding.
I just had charset option to the file component and the problem has been
solved !
--
View this message in context:
http://camel.465427.n5.nabble.com/File-Component-route-issue-tp5747281p5795564.html
Sent from the Camel - Us
Hello Claus,
Do you suggest any work around for this issue?
--
View this message in context:
http://camel.465427.n5.nabble.com/File-Component-route-issue-tp5747281p5747786.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi
I found this ticket, which refers to another thread
https://issues.apache.org/jira/browse/CAMEL-7100
On Wed, Feb 19, 2014 at 3:02 PM, jay wrote:
> Hi Claus,
> it is both as we might get the CR LF or LF in file so i used both. And also
> you are right that the tokenizer needs to be adjusted
Hi Claus,
it is both as we might get the CR LF or LF in file so i used both. And also
you are right that the tokenizer needs to be adjusted ignoring the invalid
lines/chars - looks like it is not a memory issue - it is issue with the
program.
.split(body().tokenize("\n|\r\n")).streaming().conve
Thanks Claus - thanks for your views. i have tried with tokenizer locally and
it processed all the records.
however i think tokenizer may not be a problem as the same file has been
processed in my local fuse container (Macbook)- i have tried couple of
times in local fuse esb and it processed.
Hi
What about the line separators on the big file? Are it just \n or is
it maybe \n\r or \r etc?
Maybe the tokenizer need to be adjusted?
You can also try a little java main app and try to use the java util
Scanner to read the same file and see if you can do that without any
issues. And is there
