Ok my problem is that when the thread pool reaches 10 threads, the JVM
doesn't discard them when there is no more activity and I have 10 threads
hanging. Is doing something like wireTap("...").thread(5) will work ?Claus Ibsen-2 wrote: > > On Tue, Sep 15, 2009 at 9:47 AM, Julien D <[email protected]> wrote: >> >> Hi, >> >> I'm using the wireTap component and when I looked into the code, I saw >> that >> it was creating a ScheduledThreadPoolExecutor with 10 threads. It would >> be >> useful to control the number of threads created. What do you think ? > > Its using the JDK Executors Service which handles this. The 10 is the > maximum concurrent threads. Java itself handles how it want to manage > this. > > We do have on the roadmap to have a nice and easy configurable thread > pools in Camel. However bare bone the processors do have a > setExecutorService method > you can leverage to insert your own custom executors. > > > > >> >> Julien >> -- >> View this message in context: >> http://www.nabble.com/Number-of-threads-created-with-WireTap-tp25449550p25449550.html >> Sent from the Camel - Users (activemq) mailing list archive at >> Nabble.com. >> >> > > > > -- > Claus Ibsen > Apache Camel Committer > > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus > > -- View this message in context: http://www.nabble.com/Number-of-threads-created-with-WireTap-tp25449550p25449955.html Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
