Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
MIME-Version: 1.0
In-Reply-To: <1432736477420-5767547.post@n5.nabble.com>
References: <1431948399076-5767210.post@n5.nabble.com>
 <CAGB5yNn9y9Xt30rUoe4tS4pihTo92iV8LpHUqQ+NY-yF+uJ7DQ@mail.gmail.com>
 <1432736477420-5767547.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Wed, 27 May 2015 18:33:35 +0200
Message-ID: 
 <CAGB5yNkfUbb8xDUzC1gmsNzTFDC8xdyfaPA8L0=JiBvwpKRqww@mail.gmail.com>
Subject: Re: camel-ftp sendNoOp takes 15 minutes
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: text/plain; charset=UTF-8

Hi

Yeah that would be a way of doing it. But are you sure its the send
noop command that is the problem? If you eg patch the Camel source
code and build a custom camel-ftp JAR with it disabled, does it work
for you then?

I just added an option to turn this sendNoop off from Camel 2.16
onward in jira ticket: CAMEL-8807

On Wed, May 27, 2015 at 4:21 PM, rwijngaa
<rino.van.wijngaarden@gmail.com> wrote:
> Hi Claus, thanks for your response.
>
> I'm affraid i'm stuck on this camel version (2.12).
>
> What is the best way to do this?
> I'm thinking creating a new component, say ftp2, that extends from the
> standard ftp component and overrides the preWriteCheck method in the
> RemoteFileProducer.
>
> Or is there a better way?
>
> Regards
> Rino
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/camel-ftp-sendNoOp-takes-15-minutes-tp5767210p5767547.html
> Sent from the Camel - Users mailing list archive at Nabble.com.


-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/