Observed that a single connection handles one request at a time and returns to the connection pool only after its request's response finishes.
This artificially limits the concurrency when it's greater than client's max connections.
Is this intended feature?
Observed that a single connection handles one request at a time and returns to the connection pool only after its request's response finishes.
This artificially limits the concurrency when it's greater than client's max connections.
Is this intended feature?