Details
-
Type:
Improvement Request
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.4.0
-
Fix Version/s: 4.4.1
-
Component/s: None
-
Security Level: Public
-
- Environment:
- -
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] | |
| Assignee | Christophe DENEUX [ cdeneux ] | Victor NOËL [ vnoel ] |
| Summary | Rename Component's ws-clients-pool-size-max parameter to ws-clients-per-host-pool-size-max | Remove Component's ws-clients-pool-size-max parameter max-http-connections-per-host |
| Description |
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 of http client that can hold such connections. - We have a maximum number of processor threads that can hold such http client. The maximum number of http client is the same as 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. So the maximum number of connections should be configured based on the maximum number of http client that can hold them, i.e., based on the maximum number of processors. Also, the maximum number of connections to a same host should be configurable, and should default to the maximum number of processor too. |
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 of http client that can hold such connections. - We have a maximum number of processor threads that can hold such http client. The maximum number of http client is the same as 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. So the maximum number of connections should be configured based on the maximum number of http client that can hold them, i.e., based on the maximum number of processors. Also, the maximum number of connections to a same host should be configurable, and should default to the maximum number of processor too. It will be set using the parameter max-http-connections-per-host. |
| Summary | Remove Component's ws-clients-pool-size-max parameter max-http-connections-per-host | Rename Component's ws-clients-pool-size-max parameter to Component's max-http-connections-per-host and add SU Provides ws-clients-pool-size-max. |
| Description |
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 of http client that can hold such connections. - We have a maximum number of processor threads that can hold such http client. The maximum number of http client is the same as 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. So the maximum number of connections should be configured based on the maximum number of http client that can hold them, i.e., based on the maximum number of processors. Also, the maximum number of connections to a same host should be configurable, and should default to the maximum number of processor too. It will be set using the parameter max-http-connections-per-host. |
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 configurable using a SU Provides parameter named ws-clients-pool-size-max. It should default to the maximum number of processor (the idea being that there can't be more clients needed that the number of processors). Note that this default setting potentially can create situations where there is more pooled service client for the whole component than possibly usable... it's ok but it can thus be tweaked using the parameter if needed. 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. 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 (because it is configured for the whole component and not per provides). |
| Summary | Rename Component's ws-clients-pool-size-max parameter to Component's max-http-connections-per-host and add SU Provides ws-clients-pool-size-max. | Rename Component's ws-clients-pool-size-max parameter to Component's max-http-connections-per-host |
| Description |
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 configurable using a SU Provides parameter named ws-clients-pool-size-max. It should default to the maximum number of processor (the idea being that there can't be more clients needed that the number of processors). Note that this default setting potentially can create situations where there is more pooled service client for the whole component than possibly usable... it's ok but it can thus be tweaked using the parameter if needed. 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. 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 (because it is configured for the whole component and not per provides). |
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. |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 4.4.1 [ 10587 ] | |
| Resolution | Fixed [ 1 ] |
| Summary | Rename Component's ws-clients-pool-size-max parameter to Component's max-http-connections-per-host | Remove Component's ws-clients-pool-size-max parameter and add Component's max-http-connections-per-host |