Yes its part of JDK as it specifies the size of the worker queue, of the thread pool (ThreadPoolExecutor)
For more docs see http://camel.apache.org/threading-model.html Or the Camel in Action books On Fri, Nov 20, 2015 at 12:22 AM, David Hoffer <dhoff...@gmail.com> wrote: > I'm trying to understand the default Camel Thread Pool and how the > maxQueueSize is used, or more precisely what's it for? > > I can't find any documentation on what this really is or how it's used. I > understand all the other parameters as they match what I'd expect from the > JDK...poolSize is the minimum threads to keep in the pool for new tasks and > maxPoolSize is the maximum number of the same. > > So how does maxQueueSize fit into this? This isn't part of the JDK thread > pool so I don't know how Camel uses this. > > The context of my question is that we have a from sftp route that seems to > be getting thread starved. E.g. the thread that polls the sftp connection > is slowing/stopping at times when it is busy processing other files that > were previously downloaded. > > We are using the default camel thread pool that I see has only a max of 20 > threads yet a maxQueueSize of 1000. That doesn't make any sense to me > yet. I would think one would want a much larger pool of threads (as we are > processing lots of files) but no queue at all...but not sure on that as I > don't understand how the queue is used. > > -Dave -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
