[RTFACT-17916] Access Http Client max connections should be matched to the max connections per route Created: 30/Nov/18  Updated: 03/May/19  Resolved: 30/Nov/18

Status: Resolved
Project: Artifactory Binary Repository
Component/s: Access Client
Affects Version/s: None
Fix Version/s: 6.6.0

Type: Task Priority: Normal
Reporter: Shay Bagants Assignee: Shay Bagants
Resolution: Fixed Votes: 0
Labels: None

Assigned QA: Konstantin Shenderov

 Description   

 

Modifying the Access max connections (artifactory.access.client.max.connections) might still allow only 50 connections to be used as the max connections per route parameter is hardcoded.

An example for scenario that Illustrates the problem:

1. Configure artifactory.access.client.max.connections to 1000 and the server.xml connector to match

2. Create 1000 concurrent continuing requests that will cause Artifactory to use Access client to perform login operation (even with anonymous)

3. Response time start climb up

4. Take a thread dump and see that only 50 connections are in use (RUNNABLE threads on AccessHttpClient.restCall) while all other requests are waiting for a connection from the pool (WAITING on PoolEntryFuture.await)



 Comments   
Comment by Erik Michael Purins [ 14/Feb/19 ]

Was version 6.1.4 impacted by this? What range of other versions were impacted?

Generated at Sun Oct 20 11:13:47 UTC 2019 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.