I would like to understand how the configuration of the thread pool in Servicemix works with respect to the components in the service assembly. Suppose I configure servicemix like this:
--------------------------------------- servicemix.corePoolSize = 1 servicemix.maximumPoolSize = 1 servicemix.queueSize = 128 -------------------------------------- Now I've deployed a service assembly which contains 4 components-- 1) filepoller, 2) xslt, 3) lw component, 4) bridge. The filepoller polls and sends files to the bridge. The bridge first sends it to the xslt component for transformation, then sends this transformed document to the lw component which does its thing. Since there is only 1 thread configured, will servicemix create four threads, one for each component, i.e. 1 for file poller, 1 for xslt, 1 for bridge, and 1 for lw, or is this 1 thread for the entire service assembly, i.e. filepoller gets the thread and needs to finish, then the thread is allocated for the bridge, and so on? And how does the queueSize fit into all of this? Larry -- View this message in context: http://www.nabble.com/thread-pools-and-components-tf4159831s12049.html#a11835670 Sent from the ServiceMix - User mailing list archive at Nabble.com.
