Currently, the BC SOAP component supports a parameter named ws-clients-pool-size-max parameter that actually tunes the number of maximum connections that can exist concurrently per host (for Provides thus).
It makes no sense to configure such things knowing that:
- We have a maximum number, per provides, of http client that can hold such connections.
- We have a maximum number, per component, of processor threads that can hold such http client.
The maximum number of http client should be equal to the maximum number of processor (the idea being that there can't be more clients needed that the number of processors).
The maximum number of processor is configurable (see the CDK configuration).
So the maximum number of connections should be configured based on the maximum number of http client that can hold them, i.e., the maximum number of processors.
Also, the maximum number of connections to a same host should be configurable using the parameter max-http-connections-per-host.
It should default to the maximum number of processor too.