Hi Dignesh I did some digging around on this. There are two parameters on a ResourceAdapter you can specify:
<resource id>.MaximumPoolSize = XX <resource id>.CorePoolSize = XX Which will allow you to have a variable size thread pool. If you swap out threadPoolSize for these you should get what you're after. Note that these need the resource id on the front - so if your resource adapter has an id of "test", you might define it as below: <Resource id="test" type="ActiveMQResourceAdapter"> BrokerXmlConfig = broker:(tcp://localhost:54545) ServerUrl = tcp://localhost:54545 test.MaximumPoolSize = 100 test.CorePoolSize = 10 </Resource> Kind Regards Jon On Wed, Jul 8, 2020 at 5:01 PM David Blevins <[email protected]> wrote: > Hey Jon and Dignesh, > > Could I politely ask we move this thread to the users@ list? > > I've sent a couple similar notes to others last week asking for the same > so want to be fair/consistent to everyone. > > Ok to post to dev@ if the thread changes to how to contribute towards the > fix. > > > -David > > > On Jul 8, 2020, at 5:04 AM, Dignesh <[email protected]> wrote: > > Hello Jon, > > I don't see any messages to be processed in ActiveMQ. So it means these > threads are waiting for some work to do. I would expect these threads to go > back to pool after few seconds/minutes after the work is completed., but > curious why would it show in thread dumps for such longer time. Also these > threads are nowt shown in dumps during the initial startup or for some > time. > This gets shown up once there is certain load is on the system. And even > after the system goes back to normal, the dumps still show this threads in > timed waiting. Any tuning that you can suggest ? > > > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html > > >
