https://issues.apache.org/bugzilla/show_bug.cgi?id=56841
--- Comment #4 from Dzmitry Kashlach <[email protected]> --- (In reply to Milamber from comment #2) > Some issues remain (I think) between DNSCacheManager and DNSCachePanel on > configure/modifyTestElement methods. (no time tonight to fix them) Can you show logs/description? > Why use a PoolingClientConnectionManager in HTTPHC4Impl.java? > BasicClientConnectionManager don't sufficient? The JMeter(httpclient) > default client connection manger is change with Pooling? > > + PoolingClientConnectionManager poolingClientConnectionManager= > + new > PoolingClientConnectionManager(SchemeRegistryFactory.createDefault(), > resolver); > + PoolingClientConnectionManager is extended BasicClientConnectionManager, it has constructor, which allows to pass instance of DnsResolver to httpclient to get flexibility. BasicClientConnectionManager does not allow to do that. PoolingClientConnectionManager.java public PoolingClientConnectionManager(final SchemeRegistry schreg,final DnsResolver dnsResolver) { this(schreg, -1, TimeUnit.MILLISECONDS,dnsResolver); } Added screenshot -- You are receiving this mail because: You are the assignee for the bug.
