Hi Isuru, These jars are from CEP 3.0.0. Siddhi-2.0.0.wso2v5 was a release done with some bug fixes for the PPaaS release.
That version of Siddhi also should have the same behaviour with regard to thread creation. Thanks, Lasantha On 4 January 2016 at 15:54, Isuru Haththotuwa <[email protected]> wrote: > Hi Lasantha, > > Thanks for the reply. > > These are the siddhi versions found in Stratos latest packs, AFAIK from > CEP 3.1.0 [1]. > > Not seeing any issues, but thought of finding if there is a way to fine > tune the thread/thread pool usage since its starting quite a number of > thread pools at startup. So if this is not configurable, suppose there is > no way to control the thread usage. > > [1]. > siddhi-api_2.0.0.wso2v5.jar > siddhi-core_2.0.0.wso2v5.jar > siddhi-query_2.0.0.wso2v5.jar > > On Mon, Jan 4, 2016 at 2:33 PM, Lasantha Fernando <[email protected]> > wrote: > >> Hi Isuru, >> >> Is PPaaS using the old CEP 3.1.0 features? What is the Siddhi version >> that is being used? >> >> In Siddhi-2.x, usually a thread pool was created per Siddhi Manager, and >> each Execution plan had its own Siddhi manager. So the number of pools >> would correlate to the number of execution plans. >> >> Unfortunately, for CEP 3.1.0, these thread pool sizes were not >> configurable using CEP features. But the default values worked in most use >> cases. Are you seeing any issues due to the large number of Siddhi threads >> that are created? >> >> Thanks, >> Lasantha >> >> On 4 January 2016 at 13:49, Isuru Haththotuwa <[email protected]> wrote: >> >>> Hi CEP team, >>> >>> When the PPaaS single JVM pack (with CEP features) is started, there are >>> quite a number of Siddhi-Scheduler-pool-xx [1] thread pools visible. >>> Threads are mostly in WAITING state [1]. What is the usage of these thread >>> pools? Can we configure the number of pools/threads? >>> >>> [1]. >>> "Siddhi-Scheduler-pool-12-thread-20" prio=10 tid=0x00007f96d44f7000 >>> nid=0x3636 waiting on condition [0x00007f96b7fbe000] >>> java.lang.Thread.State: WAITING (parking) >>> at sun.misc.Unsafe.park(Native Method) >>> - parking to wait for <0x0000000781e97af8> (a >>> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) >>> at >>> java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) >>> at >>> java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043) >>> at >>> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1085) >>> at >>> java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:807) >>> at >>> java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1068) >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>> at java.lang.Thread.run(Thread.java:745) >>> >>> -- >>> Thanks and Regards, >>> >>> Isuru H. >>> +94 716 358 048* <http://wso2.com/>* >>> >>> >>> >> >> >> -- >> *Lasantha Fernando* >> Senior Software Engineer - Data Technologies Team >> WSO2 Inc. http://wso2.com >> >> email: [email protected] >> mobile: (+94) 71 5247551 >> > > > > -- > Thanks and Regards, > > Isuru H. > +94 716 358 048* <http://wso2.com/>* > > > -- *Lasantha Fernando* Senior Software Engineer - Data Technologies Team WSO2 Inc. http://wso2.com email: [email protected] mobile: (+94) 71 5247551
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
