During development, we end up calling a service or a DB call and the current thread generally waits till we get a response back. In most of the cases, we won't even need to wait for the response page to build.Rather we can continue the current thread's processing.
The response page that is built might be needed in the future for processing but not sequentially. In such cases, we have a run in parallel check box for RDB-Calls. Same way we have a Queue method to call the activities in a fire and forget style.
In the help file, i was able to see a reference to the agent / threadpool size in the prconfig.xml or DSS.
1) What is the name of this DSS rule?
2) What are the allowed values for this threadpool size?
3) How to trace an activity that is getting called through a Queue method?
Also, found the background calling method in the API,
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. NOTE: Setting this entry to zero will disable batch requestors (as no threads would be available).
Thanks for the quick response, Kurt. Appreciate it. I am not sure about how to get access to the prconfig.xml. But if my understanding is correct, we can update / create DSS rules that can override the prconfig.xml configurations. If so, how to get access to this threadpoolsize DSS rule? If it doesn't exist by default, what is the name that needs to be given for the newly created DSS rule?