Hi Gnodet, Thanks for your quick reply.
Regarding Question1: =============== It means that servicemix uses same thread pool size running on JBoss as well standalone. Regarding Question2: =============== Firstly, what are the steps to create and configure ExecutorFactory for jboss deployer. Secondly, I have tried to deploy my servicemix service assembly using the standard web app distribution too, but there was one issue while running the application. The response of http consumer is not coming back on the browser. The link for details is given below. I have replication the same problem on Tomcat 6, JBoss 4.2.2.GA and Geronimo(with tomcat) 2.0.2. The issue is already mailed to forum but still unresolved. http://www.nabble.com/Re%3A-Issue-Bug-with-Servicemix-web-3.2.1-%28WAR%29-tt15560488s12049.html Regarding Question3: =============== If we change the JettyThreadPoolSize of servicemix-http component using JMX console, will that improve the performance of the application in case of JBoss deployer or not? Please give me some pointer to resolve these issues. Thanks, Puneet gnodet wrote: > > On Tue, Mar 25, 2008 at 8:22 AM, puneetjain <[EMAIL PROTECTED]> > wrote: > >> >> Hi, >> >> We have a servicemix application integrated with JBoss server. >> The application is based on servicemix-http consumer and servicemix-bean >> components. >> I have certain doubts regarding thread pool size: >> >> Question 1: >> ======= >> Could anyone please let me know, what is the default >> thread pool size of the servicemix running with JBoss Application Server? > > > > corePoolSize = 4 > maximumPoolSize = -1 > queueSize = 1024 > > >> >> >> Question 2: >> ======= >> How can I configure the thread pool size? >> > > If you use the JBoss deployer, there is no real way to do that. You would > have to modify the code of the JBoss deployer to create an ExecutorFactory > and configure it the way you want. > > If you deploy ServiceMix using the standard web app distribution, you can > modify the servicemix.xml configuration file that creates the JBI > container > and add the needed definitions for the thread pools so that they can be > configured: > > <sm:container ... > > ... > <sm:executorFactory> > <bean > class="org.apache.servicemix.executors.impl.ExecutorFactoryImpl > "> > <property name="defaultConfig"> > <bean > class="org.apache.servicemix.executors.impl.ExecutorConfig > "> > <property name="corePoolSize" > value="${servicemix.corePoolSize > }"/> > <property name="maximumPoolSize" value="${ > servicemix.maximumPoolSize}"/> > <property name="queueSize" value="${servicemix.queueSize}"/> > </bean> > </property> > </bean> > </sm:executorFactory> > </sm:container> > > >> >> Question 3: >> ======= >> What is the significance of JettyThreadPoolSize of >> servicemix-http component when it is deployed on JBoss Application >> Server? >> > > The JBoss deployer will not reuse the HTTP server from JBoss. It will use > an embedded Jetty server instead. On the other side, the servicemix web > application distribution will reuse the web server onto which it has been > deployed. > > >> >> Environment: >> ======== >> >> Servicemix 3.2.1 >> JBoss 4.2.2.GA >> OS: Redhat Enterprise Linux 4 >> >> Any reply will be appreciated. >> >> Greetings, >> Puneet >> -- >> View this message in context: >> http://www.nabble.com/%28Urgent%29-Default-Thread-Pool-Size-of-Servicemix-running-with-JBoss-tp16269404s12049p16269404.html >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/%28Urgent%29-Default-Thread-Pool-Size-of-Servicemix-running-with-JBoss-tp16269404s12049p16271924.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
