[jersey-dev] ApacheConnector, PoolingHttpClientConnectionManager and Web

[Martynas Jusevičius <martynas@xxxxxxxxxxxxx>]

Hi,

can someone show me an example of Jersey Client being configured with
ApacheConnector and PoolingHttpClientConnectionManager which does not
cause "Connection pool shutdown" as in
https://github.com/eclipse-ee4j/jersey/issues/4449?

I emphasize that there was no such problem using the
ThreadSafeClientConnManager with Jersey 1.19.

Also, is this content still valid?
https://blogs.oracle.com/japod/how-to-use-jersey-client-efficiently
It recommends avoiding WebTarget::property and WebTarget::register for
performance reasons.
If so, then WebTarget-specific ClientRequestFilters become useless,
and require a less cleaner implementation by explicitly setting header
values.


Martynas