-
Bug
-
Resolution: Fixed
-
High
-
2.1
-
None
The Apache HttpClient used by Crowd's REST client by default only makes at most 2 connections to the same host. This can be overridden by calling the setMaxConnectionsPerHost method. Currently the Crowd client only calls setMaxTotalConnections, which sets the size of the pool, but does not raise the limit on the maximum number of connections to each host. Since the Crowd host is always the same, this effectively means we have a connection pool size of 2 to Crowd. This leads to poor performance, especially in environments where session.validationinterval is set to 0
Resolution
Upgrade the Crowd REST client to 2.3.3 or above.
Patch
If you are unable to upgrade for some reason, then use the attached patched Crowd 2.2.8 REST client.
- is related to
-
-
- Closed
-
-
JSTDEV-153 Loading...
- mentioned in
-
[CWD-2646] http.max.connections is not respected by the Crowd REST client
| Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 1511095 ] | New: JAC Bug Workflow v3 [ 3365425 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Simplified Crowd Development Workflow v2 [ 1393151 ] | New: Simplified Crowd Development Workflow v2 - restricted [ 1511095 ] |
| Workflow | Original: Crowd Development Workflow v2 [ 343164 ] | New: Simplified Crowd Development Workflow v2 [ 1393151 ] |
| Remote Link | Original: This issue links to "Wiki Page (Extranet)" [ 23825 ] | New: This issue links to "Page (Extranet)" [ 23825 ] |
| Link | New: This issue relates to CWD-3695 [ CWD-3695 ] |
| Remote Link | New: This issue links to "JSTDEV-153 (JIRA (SDOG))" [ 51613 ] |
| Remote Link | New: This issue links to "Wiki Page (Extranet)" [ 23825 ] |
Tim Moore [Atlassian]
made changes -
| Labels | New: jirastudio |
| Description |
Original:
The Apache HttpClient used by Crowd's REST client by default only makes at most 2 connections to the same host. This can be overridden by calling the {{setMaxConnectionsPerHost}} method. Currently the Crowd client only calls {{setMaxTotalConnections}}, which sets the size of the pool, but does not raise the limit on the maximum number of connections to each host. Since the Crowd host is always the same, this effectively means we have a connection pool size of 2 to Crowd. This leads to poor performance, especially in environments where {{session.validationinterval}} is set to {{0}}
h3. Resolution Upgrade the Crowd REST client to 2.3.3 or above. |
New:
The Apache HttpClient used by Crowd's REST client by default only makes at most 2 connections to the same host. This can be overridden by calling the {{setMaxConnectionsPerHost}} method. Currently the Crowd client only calls {{setMaxTotalConnections}}, which sets the size of the pool, but does not raise the limit on the maximum number of connections to each host. Since the Crowd host is always the same, this effectively means we have a connection pool size of 2 to Crowd. This leads to poor performance, especially in environments where {{session.validationinterval}} is set to {{0}}
h3. Resolution Upgrade the Crowd REST client to 2.3.3 or above. h3. Patch If you are unable to upgrade for some reason, then use the attached patched Crowd 2.2.8 REST client. |
| Attachment | New: crowd-integration-client-2.2.8-cwd-2646-patched.jar [ 52190 ] |