当我使用httpclient 4.3时如下
static {
try {
SSLContextBuilder builder = new SSLContextBuilder();
builder.loadTrustMaterial(null, new TrustSelfSignedStrategy());
SSLConnectionSocketFactory sslsf = new SSLConnectionSocketFactory(builder.build());
CookieSpecProvider easySpecProvider = new CookieSpecProvider() {
public CookieSpec create(HttpContext context) {
return new BrowserCompatSpec() {
@Override
public void validate(Cookie cookie, CookieOrigin origin) throws MalformedCookieException {
// Oh, I am easy
}
};
}
};
Registry<CookieSpecProvider> r = RegistryBuilder.<CookieSpecProvider> create()
.register(CookieSpecs.BEST_MATCH, new BestMatchSpecFactory())
.register(CookieSpecs.BROWSER_COMPATIBILITY, new BrowserCompatSpecFactory())
.register("easy", easySpecProvider).build();
RequestConfig requestConfig = RequestConfig.custom().setConnectionRequestTimeout(5000)
.setSocketTimeout(10000).setConnectTimeout(10000).setCookieSpec("easy").setRedirectsEnabled(false)
.build();
PoolingHttpClientConnectionManager cm = new PoolingHttpClientConnectionManager();
cm.setMaxTotal(100);
cm.setDefaultMaxPerRoute(10);
client = HttpClients.custom().setConnectionManager(cm).setDefaultCookieSpecRegistry(r)
.setSSLSocketFactory(sslsf).setDefaultRequestConfig(requestConfig).build();
} catch (Exception e) {
logger.error("http client init fail!", e);
}
}
public static String execute(HttpRequest httpRequest) {
CloseableHttpResponse response = null;
HttpGet httpGet = null;
HttpEntity httpEntity = null;
try {
httpGet = new HttpGet(httpRequest.getUrl());
httpGet.setHeader("Connection", "close");
if (httpRequest.isUseGzip()) {
httpGet.addHeader("Accept-Encoding", "gzip,deflate,sdch");
}
if (!StringUtils.isEmpty(httpRequest.getContentType())) {
httpRequest.setContentType(httpRequest.getContentType());
}
httpGet.addHeader("User-Agent",
"Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63");
response = client.execute(httpGet);
httpEntity = response.getEntity();
byte[] bytes = null;
try {
bytes = EntityUtils.toByteArray(httpEntity);
} catch (Exception e) {
return null;
}
if (response.getStatusLine().getStatusCode() != 200) {
logger.warn("error! StatusCode: " + response.getStatusLine().getStatusCode() + ", url: "
+ httpRequest.getUrl());
return null;
}
@SuppressWarnings("deprecation")
String charset = EntityUtils.getContentCharSet(httpEntity);
if (StringUtils.isEmpty(charset)) {
Matcher match = charsetPatterm.matcher(new String(bytes));
if (match.find()) {
charset = match.group(1);
}
}
if (!StringUtils.isEmpty(charset)) {
String strUtf8 = new String(new String(bytes, charset).getBytes(), GlobalConfig.ENCODING);
return StringEscapeUtils.unescapeHtml4(strUtf8);
}
} catch (Exception e) {
logger.error("error! url [" + httpRequest.getUrl() + "]", e);
} finally {
try {
if (httpEntity != null) {
EntityUtils.consume(httpEntity);
}
if (response != null) {
response.close();
}
if (httpGet != null) {
httpGet.abort();
}
} catch (Exception e) {
// ignore
}
}
return null;
}
线程将阻止.. jstack显示如下。我只是用它来抓取一些网站。当statusCode为404时会发生这种情况 Using Java Apache PoolingClientConnectionManager leaks the Memory,How to solve it? 我的问题与此类似。
"pool-1-thread-10" prio=10 tid=0x00007f7168003000 nid=0x3e4d waiting on condition [0x00007f717c398000]
java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for <0x00000000e69d7350> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
at org.apache.http.pool.PoolEntryFuture.await(PoolEntryFuture.java:133)
at org.apache.http.pool.AbstractConnPool.getPoolEntryBlocking(AbstractConnPool.java:282)
at org.apache.http.pool.AbstractConnPool.access$000(AbstractConnPool.java:64)
at org.apache.http.pool.AbstractConnPool$2.getPoolEntry(AbstractConnPool.java:177)
at org.apache.http.pool.AbstractConnPool$2.getPoolEntry(AbstractConnPool.java:170)
at org.apache.http.pool.PoolEntryFuture.get(PoolEntryFuture.java:102)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.leaseConnection(PoolingHttpClientConnectionManager.jav
a:244)
at org.apache.http.impl.conn.PoolingHttpClientConnectionManager$1.get(PoolingHttpClientConnectionManager.java:231)
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:173)
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
如何解决？
答案 0 :(得分：7)
我有同样的问题，这是第一个回复。我使用Ironluca的评论来解决我的问题，但觉得这需要一个完整的答案。
quick start guide有一个如何设置和使用基本HttpClient的简洁示例。
// In order to ensure correct deallocation of system resources
// the user MUST call CloseableHttpResponse#close() from a finally clause.
// Please note that if response content is not fully consumed the underlying
// connection cannot be safely re-used and will be shut down and discarded
// by the connection manager.
try {
System.out.println(response1.getStatusLine());
HttpEntity entity1 = response1.getEntity();
// do something useful with the response body
// and ensure it is fully consumed
EntityUtils.consume(entity1);
} finally {
response1.close();
}
回顾你的问题，似乎你有关闭和消费代码 您还有一个自定义连接池。它与默认值相同，但我猜你的配置不同。
答案 1 :(得分：3)
我遇到过类似的错误。看来我们需要在返回之前使用HttpEntity。在你的情况下，当你遇到非200个回复时，我发现你没有这样做。你只是返回null。您可能需要在返回之前使用它。 另外，我建议使用HttpClientUtils.closeQuietly（响应）;这是EntityUtils.consume
的包装器答案 2 :(得分：0)
("Bus", "Vehicle")正在等待的condition字段表示池中有可用的连接槽。 HttpClient默认情况下未配置连接超时，因此在getPoolEntryBlocking上调用await时没有超时，如果由于某种原因无法将连接返回到池，则可能导致死锁。最可能的原因是缺少超时，因此请配置合理的连接超时以保护自己免受主机行为的影响。
如果您致电Future，则不会看到连接泄漏。不使用实体只会导致连接无法被池重用，从而导致更多新连接。