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
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