Question
WellCare
US
Last activity: 12 Nov 2015 15:16 EST
Batch requestors unable to exceed 10 in JBoss 6.1 EAP
Any one has this issue?
Pegasystems Inc.
US
Hi Fabian,
There is a prconfig setting called threadPoolSize
Functionality: This setting entry adjusts the size of the batch requestor pool, to provide the number of available Java threads on which agents and batch requestors may run. The maximum number of threads is limited by operating system considerations.
Try specifying some value with the below prconfig setting and verify.
<env name="agent/threadpoolsize" value="30" />
There is a related support article on PDN for this issue
https://community.pega.com/support/support-articles/batch-requestors-unable-exceed-10
WellCare
US
I added it but still does not show.
Do you know what they mean by this..
"you must configure the work manager and specify a limit to the number of worker
threads. This configuration is discussed in the installation manual for the
product."
Pegasystems Inc.
US
For JBoss 6.x, you can edit the ejb-jar.xml (which will require redeploy the ear with the updated xml, the xml is part of prbean.jar), looking for PRAsync mdb segment:
Adding this:
<activation-config-property-name>maxSession</activation-config-property-name>
<activation-config-property-value>100</activation-config-property-value>
Also this is limited by the mdb-strict-max-pool setting in standalone.xml (by default it is 20). Redhat recommend both set to the same value.
WellCare
US
Thanks, Kevin for all your support. As always outstanding
Thank you,
Pedro “Fabian” Diaz, RHCSA
Sr Systems Eng.
WellCare Health Plans, Inc.
3950 Premier N. Dr. Tampa, FL 33618
813.206-6614 (O)
727.459-6577 (C)
Pegasystems Inc.
US
Hello Fabian, Harish,
The WorkManager configuration is specific to IBM WebSphere. This is covered in the installation manual for WebSphere deployments (search for the word "WorkManager" to find the relevant content). JBOSS doesn't utilize a work manager, however the JMS topic *can* have a minimum and maximum pool size defined. Please see the content in the installation manual for JBOSS. To quickly find the relevant content search for the word "min-pool-size" in this manual: https://pdn.pega.com/documents/pega-719-platform-installation-guide-for-oracle-on-jboss-red-hat-eap-0
It's not clear to me that you're having a problem with the JMS topic pool size though. Can you please clarify what you're doing to create batch requestors? For example, are you running a lot of agents? Or, are you perhaps spawning a large number of child-batch requestors? Child requestors are created when you run connectors (for example, Connect-SOAP) in parallel, or you use the queueBatchActivity functionality. Please tell me more about your particular use case - there may be another setting that applies. Thanks -Ian