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
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.
.to(splitMessageQueue);
>
>
> Error is - exhausted after delivery attempt: 1 caught:
> org.apache.camel.RuntimeCamelException: Scanner aborted because of an
> IOException!
>
> would you mind to provide me your views on fixing the issue.
>
>
>
> --
> View this message
fixing the issue.
--
View this message in context:
http://camel.465427.n5.nabble.com/File-Component-route-issue-tp5747281p5747550.html
Sent from the Camel - Users mailing list archive at Nabble.com.
.
I am suspecting may be some cache/memory/aggregation problem in the
container as it is keep on the reading only few records and processing them
again and again.
--
View this message in context:
http://camel.465427.n5.nabble.com/File-Component-route-issue-tp5747281p5747310.html
Sent from the
2.10.0.fuse-71-047]
>
> Caused by: java.nio.charset.MalformedInputException: Input length = 1
> at
> java.nio.charset.CoderResult.throwException(CoderResult.java:260)[:1.6.0_45]
> at
> sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:319)[:1.6.0_45]
>
&
topper issue for my delivery?
--
View this message in context:
http://camel.465427.n5.nabble.com/File-Component-route-issue-tp5747281.html
Sent from the Camel - Users mailing list archive at Nabble.com.
