Is it safe to use a single Apache HttpClient 5 (with PoolingHttpClientConnectionManager) for accessing both fast and slow endpoints?

Question

I'm using Apache HttpClient (version 5.4.x) with PoolingHttpClientConnectionManager, which pools connections on a per-route basis. According to the documentation, each route has its own pool of connections.

However, I’m concerned that a surge of slow, long-running requests could tie up enough connections to delay or block the faster requests.

My question is: Does the per-route connection pooling fully isolate these two types of requests, or is there a risk of one affecting the other under heavy load?

@ChinHuang, thanks for the link to the related question. However, it’s not quite what I was asking. I’ve edited my question, and I hope it’s clearer now. — Max Alex
– Max Alex, Commented Feb 5 at 20:48

ok2c · Accepted Answer · 2025-02-12 16:09:08Z

0

HttpClient manages persistent connections in the pool based on their routes, not their performance characteristics. If a particular route has a higher priority than others one may allow that route to allocate more concurrent connections but this has nothing to do with performance of individual message exchanges. Connections for that specific route will always be allocated regardless of other routes as long as the total max number of connections has been reached

answered Feb 12 at 16:09

ok2c

27.9k5 gold badges66 silver badges74 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Is it safe to use a single Apache HttpClient 5 (with PoolingHttpClientConnectionManager) for accessing both fast and slow endpoints?

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related