Thread pool usage for cloud requests

Know how the on-premises Integration Server uses a thread from the server thread pool to process service requests.

When an application that is developed on webMethods Integration starts a service on an on-premises Integration Server, the on-premises Integration Server uses a thread from the server thread pool to process the service request. The processing thread starts the service, posts the response, and then ends, which releases the thread to process other requests. The on-premises Integration Server can process multiple service requests from webMethods Integration simultaneously.

The watt.server.threadPool.cloudRequests specifies the maximum percentage of the server thread pool that can be used for processing webMethods Integration requests. By default, this value is set to 5. For example, if the server thread pool allows up to 1000 threads, a maximum of 50 threads can be used simultaneously for cloud request processing. If the watt.server.threadPool.cloudRequests value is either undefined or configured to generate fewer than 25 threads, Integration Server automatically adjusts the thread count to a minimum of 25 to handle webMethods Integration requests effectively.

At the start, Integration Server uses the specified percentage to calculate the number of threads that can be used, and logs a message with that information to the server.log. At run time, when Integration Server reaches the maximum number of threads that can be used to process requests from webMethods Integration, Integration Server writes the following message and blocks new server requests from webMethods Integration until a thread becomes available: The server thread pool is using the maximum number of threads that are allowed for processing requests from webMethods Cloud. Requests from webMethods Cloud block until a thread becomes available.