Hi Reka, I do not think it should be one thread pool. May be few high-level ones for different features:
1. Application Monitors 2. Message Listeners 3. Any other functionality using threads Thanks On Tue, Jun 23, 2015 at 1:42 PM, Reka Thirunavukkarasu <[email protected]> wrote: > Hi Isuru, > > On Tue, Jun 23, 2015 at 1:00 PM, Isuru Haththotuwa <[email protected]> > wrote: > >> Hi Reka, >> >> >> On Tue, Jun 23, 2015 at 12:20 PM, Reka Thirunavukkarasu <[email protected]> >> wrote: >> >>> Hi >>> >>> While testing found out that we are using different pool for different >>> purposes like application monitor, group monitor, cluster monitor and etc. >>> Is it possible to use one thread pool per component such as autoscaler with >>> higher pool size like 100. Then we can make sure that there will always be >>> threads available to do the job whenever needed. WDYT? >>> >> +1 for the suggestion. Additionally, lets give the threads meaningful >> names using a custom Thread Factory [1] so that we can determine what >> threads are causing issues when debugging a threading related issue. >> > > +1. It is a good suggestion. Will try to incorporate it as well. > >> >> [1]. >> http://docs.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/ThreadFactory.html >> >>> >>> Would you find any issues with merging all the different pools in >>> autoscaler to just with one thread pool? >>> >> >>> >>> Thanks, >>> Reka >>> >>> -- >>> Reka Thirunavukkarasu >>> Senior Software Engineer, >>> WSO2, Inc.:http://wso2.com, >>> Mobile: +94776442007 >>> >>> -- >>> <%2B94776442007> >>> <%2B94776442007> >>> Thanks and Regards, >>> >>> Isuru H. >>> <%2B94776442007> >>> +94 716 358 048 <%2B94776442007>* <http://wso2.com/>* >>> >>> >>> * <http://wso2.com/>* >>> >>> >>> > > > -- > Reka Thirunavukkarasu > Senior Software Engineer, > WSO2, Inc.:http://wso2.com, > Mobile: +94776442007 > > > -- Imesh Gunaratne Senior Technical Lead, WSO2 Committer & PMC Member, Apache Stratos
