camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: FTP performance with hundreds of concurrent routes.
Date Wed, 09 May 2012 12:47:56 GMT
On Wed, May 9, 2012 at 2:29 PM, domenec <> wrote:
> Hello and thanks beforehand for any response, pointer or simply reading.
> Without previous knowledge of Camel I was requested to support a customer
> who had "a Java application that does FTP's at scheduled times and eats up
> server resources, and they have no source code".
> OK, I inspected the WAR, found out it was Camel, discovered what it was (and
> liked it, I have done MQ Series and Oracle Service Bus and several
> integration projects).
> At the moment the Tomcat server has been instrumented with JMX and I will
> collect data about threads, memory usage, whatever gives some hint.
> I have a suspect on threading, based a priori on FTP usually eating two
> threads (for data and communication channels) and a posteriori for having
> read about performance issues with default pool of 10 threads, which were
> fixed by going to 50 threads.
> So, at the moment all I can say is that there are about 600 to 800 possibly
> concurrent FTP's, which looks like a lot for 10 threads, if I get it right.
> No questions, I'd just appreciate hints on what to look and report if it
> looks suspicious, based on your experience, thanks :)

What version of Camel do you use?

And do you download or upload files to the FTP server? (consumer or
producer in EIP terms)

The Camel FTP consumer is by default single threaded, eg

So if you have a route that does: (pseudo)
from ftp
  to bean

Then only 1 thread is active.

> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

Claus Ibsen
CamelOne 2012 Conference, May 15-16, 2012:
Twitter: davsclaus, fusenews
Author of Camel in Action:

View raw message