Hi
Thanks for reporting. I do think the FTP library cannot safely recover.
When a poll is performed Camel asks it whether it still a valid
connection before doing the list files.
I wonder if we need to rebuild it if has caused an exception in the
previous poll and do not trust that it can recover.
If you enable TRACE logging level for org.apache.camel.component.file
you should see what it does in much more details.
You are very welcome to do this. Eg enable TRACE logging to a logfile
and perform your test again.
And then mail back with the log file attached, then I can take a look
on friday morning.
On Thu, Jul 16, 2009 at 8:09 PM, Jason Queen<jason.qu...@colinx.com> wrote:
>
> Ok, I tried removing the maximumReconnectAttempts=-1 option from the endpoint
> and still get the same results. I also tried making the routes as simple as
> possible (code below) and the same thing happens. Startup camel and let it
> swap a couple files a few times, kill the connection, wait a few seconds and
> Route 2 gets stuck in a loop calling FtpOperations.listFiles() and never
> recovers even after plugging back in the network cable.
>
> public void configure() throws Exception {
>
> // Route 1
> from("file://C:/cameltest?sortBy=file:modifed")
> .to("ftp://u...@server/ftptest?password=password";);
>
> // Route 2
> from("ftp://u...@server/ftptest?password=password";)
> .to("file://C:/cameltest");
>
> }
> --
> View this message in context:
> http://www.nabble.com/FTP-Component-Network-Failure-Recovery-Problem-tp24517828p24521614.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
