Hi Ashwin, Thanks for the reply. Btw by 'every' servicemix.zip u also mean the individual lwc component zips that we develop and deploy for our business needs as well ..right? I will myself give it a try as well now.
Soumya --- On Mon, 23/2/09, Ashwin Karpe <[email protected]> wrote: > From: Ashwin Karpe <[email protected]> > Subject: Re: Threadpool confusion in servicemix 3.2.1 > To: [email protected] > Date: Monday, 23 February, 2009, 5:53 PM > Hi, > > Yes, every component (i.e. very servicemix...zip file in > the hotdeploy > directory is allocated the abilit to individually affect > the parameters > specified in the link. > > It is quite similar to Apache Web Server where each servlet > can be > individually configured for threads and resources. > > Hope this helps. > > Cheers, > > Ashwin... > > > Soumya-5 wrote: > > > > > > Hi friends, > > I have the following question - > > > > Well I am using Servicemix 3.2.1 and the default > > config settings. > > servicemix.corePoolSize = 4 > > servicemix.maximumPoolSize = 32 > > servicemix.queueSize = 256 > > > > > > > > > > Now I have deployed several of my own business > > components as a LWC zips and each has it's own > > servicemix.xml. > > > > Here are my doubts - > > > > 1) I read through > > http://servicemix.apache.org/thread-pools.html > > > > There it says every component has it's own > threadpool. > > By "component" does it mean every individual > > > application zip I put in 'hotdeploy'? > > Will it inherit the properties from the base > > conf/servicemix.xml and have their individual > > threadpools? i.e. does the respective servicemix.xml > > of every LWC component just extend the executorfactory > > config on the parent servicemix.xml? > > > > 2) I see in the link > > http://servicemix.apache.org/thread-pools.html and > > example > > <property name="configs"> > > <map> > > <entry > key="flow.jms.servicemix-http"> > > <bean > > > class="org.apache.servicemix.executors.impl.ExecutorConfig"> > > <property > name="corePoolSize" > > value="32"/> > > <property > name="maximumPoolSize" > > value="-1"/> > > <property name="queueSize" > > value="1024"/> > > </bean>..... > > > > What is "flow.jms.servicemix-http" ? Does it > mean the > > Heavyweight JBI component identified by > > servicemix-http-3.2.1-installer.zip http zip? In that > > case my question (1) is wrong itself. As then it would > > mean threadpools are configured based on Heavyweight > > components and not individual business LWC or Bean > > components. > > > > 3) If 2 is correct what should be the corresponding > > <entry key="xxxx"> value for lwc and > bean components? > > where can I find that info? something similar to > > "flow.jms.servicemix-http" ? > > > > 4) The example snippet given in > > > > http://servicemix.apache.org/thread-pools.html ... > > > > which servicemix.xml do we configure that? the base > > conf/servicemix.xml file? or individual lwc > > servicemix.xml files? > > > > I am know I have flooded you with a lot of questions > > but will appreciate your help a lot! > > > > Regards, > > Soumya > > The road to success is always under construction :P > > > > > > Add more friends to your messenger and enjoy! Go > to > > http://messenger.yahoo.com/invite/ > > > > > > > ----- > --- > Ashwin Karpe, Principal Consultant, PS - Opensource Center > of Competence > Progress Software Corporation > 14 Oak Park Drive > Bedford, MA 01730 > --- > +1-972-304-9084 (Office) > +1-972-971-1700 (Mobile) > ---- > Blog: http://opensourceknowledge.blogspot.com/ > > > -- > View this message in context: > http://www.nabble.com/Threadpool-confusion-in-servicemix-3.2.1-tp22121300p22160546.html > Sent from the ServiceMix - User mailing list archive at > Nabble.com. Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/
