This won't work. The executor factory can not be configured that way. It has to be configured on the JBI container.
On Tue, Mar 25, 2008 at 11:54 AM, puneetjain <[EMAIL PROTECTED]> wrote: > > Hi Gnodet, > > Thanks for your valuable input. > > I am still a bit confused with the thread pooling in servicemix. > Could you please explain that what is difference between servicemix thread > pool size and servicemix component thread pool size? The example of > servicemix component thread pool size is the JettyThreadPoolSize of > servicemix-http component. > > How both of them are function togather in case of servicemix running with > Jboss using jboss deployer? > > Secondly, I have configured the ExecutorFactoryImpl in my xbean.xml files > of > servicemix-http and servicemix-bean components. The xbean.xml file for > servicemix-http is given below: > > <?xml version="1.0" encoding="UTF-8"?> > <!-- > This is the configuration file for servicemix-http binding > component. > @author Puneet Jain > --> > > <beans xmlns:http="http://servicemix.apache.org/http/1.0"; > xmlns:ex="http://www.servicemix.org/example";> > > <http:consumer service="ex:httplistener" > endpoint="listenerEndpoint" > locationURI="http://0.0.0.0:8192/upload/"; > defaultMep="http://www.w3.org/2004/08/wsdl/in-out"; > targetService="ex:lineReverse" > marshaler="#marshaler" /> > > <bean id="marshaler" class="com.oki.us.esb.sm.perftester.HTTPMarshaler" > /> > > <bean id="executorFactory" > class="org.apache.servicemix.executors.impl.ExecutorFactoryImpl"> > <property name="defaultConfig"> > <bean class="org.apache.servicemix.executors.impl.ExecutorConfig"> > <property name="corePoolSize" value="32"/> > <property name="maximumPoolSize" value="40"/> > <property name="queueSize" value="500"/> > </bean> > </property> > </bean> > > </beans> > > Will this override the default thread pool size for the servicemix > components in case of servicemix running with Jboss Application Server. > (Integrated using jboss deployer). > > Thanks, > Puneet > > > gnodet wrote: > > > > On Tue, Mar 25, 2008 at 10:23 AM, puneetjain <[EMAIL PROTECTED]> > > wrote: > > > >> > >> Hi Gnodet, > >> > >> Thanks for your quick reply. > >> > >> Regarding Question1: > >> =============== > >> It means that servicemix uses same thread pool size running on JBoss as > >> well > >> standalone. > > > > > > Not really. The standalone version override the default settings with > the > > following ones: > > > > corePoolSize = 4 > > maximumPoolSize = 32 > > queueSize = 256 > > > > > >> > >> > >> Regarding Question2: > >> =============== > >> Firstly, what are the steps to create and configure ExecutorFactory for > >> jboss deployer. > > > > > > In the java code of the JBoss deployer, try to modify the > > JBIService#startService() method. > > > > ExecutorFactoryImpl executorFactory = new ExecutorFactoryImp(); > > ExecutorConfig config = new ExecutorConfig(); > > config.setCorePoolSize(32); > > ... > > executorFactory.setDefaultConfig(config); > > jbiContainer.setExecutorFactory(executorFactory); > > > > > >> > >> > >> 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 > >> > > > > I'll have a look at it. > > > > > >> > >> 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? > > > > > > Yes, there will be an impact. The jetty thread pool size controls how > > many > > threads will be used by the embedded jetty server to service incoming > > requests. You may want to try changing the configuration and see if it > > improves the performances. > > > > > >> > >> > >> 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. > >> > >> > > > > > > -- > > 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-tp16269404s12049p16273573.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
