I think you may need to find another way to pull the sub directory instead of
pulling root directory directly.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-ftp-2-15-1-return-ftp-error-code-421-tp5765272p5765843.html
Sent from the Camel - Users mailing list archive at
The first connection is used to check if the ftp server is still alive before
starting to pull the directory.
If the RemoteFileConsumer cannot connect to the server, it just return the
pulling process and wait for another pulling.
--
View this message in context:
http://camel.465427.n5.nabble.c
An exemplary work plan Ftp consumer.
As we can see, at the beginning of a connection to the server.
FTPClient establishes a new connection for a list of files in each
directory.
At the end of the first connection is switched off.
Why hold the first connection?
Another question.
Some directorie
Yes, I tried to find an answer to the question why the process ceases to take
files from ftp server.
The most simple - revert to the old assembly Camel. Lo and behold, the files
were taken.
But just a couple of days. Server file number increased by several hundred.
The system stops to pick up the f
I just try to guess what’s the cause of issue of camel-ftp 2.15.1 by looking up
the change log. I’m not sure if changing the receiving buffer could make the
difference.
It looks like you just find the key of the issue, am I right?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blo
It looks like quite a different matter.
On the server, there is a restriction session. After 10 minutes, the server
connection tearing.
No problem in download speed of large files. Disconnection is the fault of
the strategy routePolicyStopTime. But it's not scary.
The main problem is to read a lar
OK, here is another change CAMEL-8513[1] in Camel 2.15.1 which improves the
download speed. I guess it may cause the ftp server complain about the server
load. So the workaround could be set the receiveBufferSize option to 1024 to
slow down the processing speed.
[1]https://issues.apache.org/ji
A short excerpt from karaf.log.xxx file
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-ftp-2-15-1-return-ftp-error-code-421-tp5765272p5765368.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Honestly. 2.15.0 On this effect is much less than 2.15.1.
I used to
CronScheduledRoutePolicy ftpDocReadRoutePolicy = new
CronScheduledRoutePolicy();
ftpDocReadRoutePolicy.setRouteStartTime(routePolicyStartTime);
ftpDocReadRoutePolicy.setRouteStopTime(routePolicyStopTime);
ftpDocReadRoutePol
There are only few changes between Camel 2.15.1 and Camel 2.15.0.
I’m not sure if CAMEL-7565[1] is related to issue that you faced.
[1]https://issues.apache.org/jira/browse/CAMEL-7565
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http:
Imagine that your FTP directory shows the "C:\Program Files" on Windows or
"/usr/lib" on Linux. There is a very large number of files. Files can not be
deleted.
Process periodically scans all files in all folders, filters, and sorts.
Uses a database table to store the names of files previously trea
On the new version of Apache Camel 2.15.1 started to happen strange errors.
On this version 2.15.0 there is no error.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-ftp-2-15-1-return-ftp-error-code-421-tp5765272.html
Sent from the Camel - Users mailing list archive a
12 matches
Mail list logo