Limiting Server Threads for webMethods Messaging Triggers
Integration Server provides parameters that you can use to limit how many threads in the server thread pool retrieve and process documents for webMethods messaging triggers. You can specify what percentage of the server thread pool can be used to retrieve documents from the messaging provider. You can also specify the percentage of the server thread pool that can be used to process documents received by triggers.
For example, suppose that the server thread pool can contain up to 80 threads. If you specify that the maximum threads for document retrieval is 50% of the server thread pool, then Integration Server can use up to 40 threads for retrieving documents from the messaging provider.
Limiting the number of server threads that can retrieve and process documents from the messaging provider keeps server threads available to perform other server functions such as responding to http requests or server administration. These parameters help to ensure that retrieving and processing documents from the messaging provider will not monopolize the entire server thread pool.
Note: | When Integration Server uses a thread for document retrieval, the thread retrieves documents for one trigger from the messaging provider. The thread does not retrieve documents for all triggers. A thread used for document processing addresses one document in a trigger queue. (Document processing includes determining which trigger condition the document satisfies and executing the associated service.) |
Contact Support
|
Community
|
Feedback