Setting Maximum Thread Pool Usage for Cloud Requests
When an application developed on Integration Cloud invokes a service on an on-premise Integration Server, the on-premise Integration Server uses a thread from the server thread pool to process the service request. The processing thread invokes the service, posts the response, and then terminates which frees up the thread to process other requests. The on-premise Integration Server can process multiple service requests from Integration Cloud simultaneously.
The watt.server.threadPool.cloudRequests specifies the maximum percentage of the server thread pool that can be used for processing Integration Cloud requests. The default is 75.
Note:
After application of a fix that includes PIE-60686 (IS_10.5_WmCloud_Fix1 and higher), the default is 5 which means that if the maximum size of the server thread pool is 1000, up to 50 server threads at a time can be used to process cloud requests.
At start up, Integration Server uses the 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 Integration Cloud, Integration Server writes the following message and blocks new server requests from Integration Cloud until a thread becomes available.
[ISS.0021.8040W] Server thread pool is using the maximum number of threads allowed for processing requests from the webMethods Cloud. Requests from webMethods Cloud will block until a thread becomes available.
Note:
If watt.server.threadPool.cloudRequests is set to 0, the on-premise Integration Server processes requests from webMethods Cloudone at a time. The on-premise Integration Server blocks processing of further requests from webMethods Cloud until the current service execution completes. This delays processing of requests from webMethods Cloud.