Hi

Could you at least remember to state which version of Camel! And also
did it work in a previous version? Have you tried with newer versions?
And have you tried from an unit test outside any container (especially
OSGi containers).



On Wed, Sep 15, 2010 at 11:58 AM, S. Ali Tokmen
<savas-ali.tok...@bull.net> wrote:
>  Hello
>
> The route I'm currently interested in uses CAMEL in Java DSL mode. It
> basically copies files from an FTP server, hence the from clause:
>
>
> ftp://ca...@production26:21/ftproot/camel?password=camel&delay=60000&binary=true&disconnect=true
>
> As a result, the delay is supposed to be 60 seconds. But here's what I get
> in the logs:
>
>   2010-09-15 09:22:09,008 INFO (RemoteFileConsumer) - Connected and
>   logged in to: ftp://ca...@production26:21:21
>   2010-09-15 09:22:09,508 INFO (RemoteFileConsumer) - Connected and
>   logged in to: ftp://ca...@production26:21:21
>   2010-09-15 09:22:10,004 INFO (RemoteFileConsumer) - Connected and
>   logged in to: ftp://ca...@production26:21:21
>   2010-09-15 09:22:10,714 INFO (RemoteFileConsumer) - Connected and
>   logged in to: ftp://ca...@production26:21:21
>
> Which indicates that CAMEL about twice a second. After looking to it with a
> debugger, I've seen that this delay comes from the default value of
> ScheduledPollConsumer.delay (500).
>
> I therefore see that the "delay" attribute of the consumer is not changed no
> matter what delay I put in my URL. Is this an expected behaviour?
>
> Cheers
>
> --
>
> S. Ali Tokmen
> savas-ali.tok...@bull.net
>
> Office: +33 4 76 29 76 19
> GSM:    +33 66 43 00 555
>
> Bull, Architect of an Open World TM
> http://www.bull.com
>
>



-- 
Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus

Reply via email to