Limiting the Processing of Concurrent Requests for a Service
At times, a few services might consume the majority of the Integration Server resources available to process requests. To minimize the impact of requests for these frequently invoked services, you can limit the number of concurrent executions of the service in the service properties when you invoke a service as a top-level service. Nested invocations of the service do not contribute to the limit. When the service meets the maximum allowed concurrent executions, subsequent requests for the service receive a "503 Service Unavailable" response.
To configure the concurrent request limit for a service
1. In Package Navigator view, select the service.
2. Under Concurrent requests limit, select the following properties.
Property | Description |
Enabled | Specifies whether the limit for concurrent executions of the service is enabled when invoked as a top-level service or not. |
| Select... | To... |
| True | Enable the limit for concurrent service executions. |
| False | Disable the use of a concurrent service execution limit. This is the default. |
Max concurrent requests | Specifies the maximum concurrent executions of the service when it is invoked as a top-level service. When the maximum concurrent executions limit is met, subsequent invocations of the service fail with a service exception. A subsequent request for the service does not execute until the current execution completes. |