java – Spring RestTemplate SocketException快速连续执行时连接重置
内容导读
互联网集市收集整理的这篇技术教程文章主要介绍了java – Spring RestTemplate SocketException快速连续执行时连接重置，小编现在分享给大家，供广大互联网技能从业者学习和参考。文章包含7834字，纯文字阅读大概需要12分钟。
内容图文
建立
本地运行的简单服务器和客户端应用服务器端点接收具有休眠时间的POST请求以模拟工作. Client是一个使用RestTemplate进行HTTP调用的SpringBoot应用程序.模拟每个请求在服务器上的500ms延迟并发出700个多线程请求.
问题
在快速连续执行客户端程序时,我得到java.net.SocketException：连接重置.堆栈跟踪：
org.springframework.web.client.ResourceAccessException: I/O error on POST request for "http://localhost:8081/server/site": Connection reset; nested exception is java.net.SocketException: Connection reset
java.util.concurrent.ExecutionException: org.springframework.web.client.ResourceAccessException: I/O error on POST request for "http://localhost:8081/server/site": Connection reset; nested exception is java.net.SocketException: Connection reset
at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[na:1.8.0_74]
at java.util.concurrent.FutureTask.get(FutureTask.java:192) ~[na:1.8.0_74]
at com.sample.client.rest.RestClient.invokeServer(RestClient.java:75) ~[classes/:na]
at com.sample.client.SampleClientApplication.main(SampleClientApplication.java:13) [classes/:na]
Caused by: org.springframework.web.client.ResourceAccessException: I/O error on POST request for "http://localhost:8081/server/site": Connection reset; nested exception is java.net.SocketException: Connection reset
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:673) ~[spring-web-4.3.13.RELEASE.jar:4.3.13.RELEASE]
at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:620) ~[spring-web-4.3.13.RELEASE.jar:4.3.13.RELEASE]
at org.springframework.web.client.RestTemplate.postForEntity(RestTemplate.java:414) ~[spring-web-4.3.13.RELEASE.jar:4.3.13.RELEASE]
at com.sample.client.rest.RestClient.lambda$invokeServer$0(RestClient.java:68) ~[classes/:na]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[na:1.8.0_74]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[na:1.8.0_74]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[na:1.8.0_74]
at java.lang.Thread.run(Thread.java:745) ~[na:1.8.0_74]
Caused by: java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:209) ~[na:1.8.0_74]
at java.net.SocketInputStream.read(SocketInputStream.java:141) ~[na:1.8.0_74]
at org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:137) ~[httpcore-4.4.8.jar:4.4.8]
at org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:153) ~[httpcore-4.4.8.jar:4.4.8]
at org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:282) ~[httpcore-4.4.8.jar:4.4.8]
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:138) ~[httpclient-4.5.3.jar:4.5.3]
at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56) ~[httpclient-4.5.3.jar:4.5.3]
at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259) ~[httpcore-4.4.8.jar:4.4.8]
at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:163) ~[httpcore-4.4.8.jar:4.4.8]
at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:165) ~[httpclient-4.5.3.jar:4.5.3]
at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273) ~[httpcore-4.4.8.jar:4.4.8]
at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125) ~[httpcore-4.4.8.jar:4.4.8]
at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:272) ~[httpclient-4.5.3.jar:4.5.3]
at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185) ~[httpclient-4.5.3.jar:4.5.3]
at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89) ~[httpclient-4.5.3.jar:4.5.3]
at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:111) ~[httpclient-4.5.3.jar:4.5.3]
at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) ~[httpclient-4.5.3.jar:4.5.3]
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) ~[httpclient-4.5.3.jar:4.5.3]
at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) ~[httpclient-4.5.3.jar:4.5.3]
at org.springframework.http.client.HttpComponentsClientHttpRequest.executeInternal(HttpComponentsClientHttpRequest.java:89) ~[spring-web-4.3.13.RELEASE.jar:4.3.13.RELEASE]
at org.springframework.http.client.AbstractBufferingClientHttpRequest.executeInternal(AbstractBufferingClientHttpRequest.java:48) ~[spring-web-4.3.13.RELEASE.jar:4.3.13.RELEASE]
at org.springframework.http.client.AbstractClientHttpRequest.execute(AbstractClientHttpRequest.java:53) ~[spring-web-4.3.13.RELEASE.jar:4.3.13.RELEASE]
at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:659) ~[spring-web-4.3.13.RELEASE.jar:4.3.13.RELEASE]
如果客户端没有快速连续执行,则没有错误.
调试/分析
>分析了Wireshark捕获.服务器正在发送RST数据包
>没有关闭PoolingHttpClientConnectionManager和CloseableHttpClient？为正常关闭添加了@PreDestroy关闭方法.没运气.
>港口用尽？仅配置了200个同时连接.
Spring RestTemplate配置
@Configuration
public class Config {
private static final int CONNECT_TIMEOUT = 5000;
private static final int CONNECTION_MANAGER_CONNECTION_REQUEST_TIMEOUT = 0;
private static final int SOCKET_TIMEOUT = 5000;
private static final int MAX_TOTAL = 200;
private static final int MAX_PER_ROUTE = 200;
@Bean
public PoolingHttpClientConnectionManager poolingHttpClientConnectionManager() {
PoolingHttpClientConnectionManager connectionManager = new PoolingHttpClientConnectionManager();
connectionManager.setMaxTotal(MAX_TOTAL);
connectionManager.setDefaultMaxPerRoute(MAX_PER_ROUTE);
connectionManager.setValidateAfterInactivity(CONNECT_TIMEOUT);
return connectionManager;
}
@Bean
public RequestConfig requestConfig() {
RequestConfig result = RequestConfig.custom()
.setConnectionRequestTimeout(CONNECTION_MANAGER_CONNECTION_REQUEST_TIMEOUT)
.setConnectTimeout(CONNECT_TIMEOUT)
.setSocketTimeout(SOCKET_TIMEOUT)
.build();
return result;
}
@Bean
public CloseableHttpClient httpClient(PoolingHttpClientConnectionManager poolingHttpClientConnectionManager, RequestConfig requestConfig) {
CloseableHttpClient result = HttpClientBuilder
.create()
.setConnectionManager(poolingHttpClientConnectionManager)
.setDefaultRequestConfig(requestConfig)
.build();
return result;
}
@Bean
public RestTemplate restTemplate() {
HttpComponentsClientHttpRequestFactory factory = new HttpComponentsClientHttpRequestFactory();
factory.setHttpClient(httpClient(poolingHttpClientConnectionManager(), requestConfig()));
RestTemplate restTemplate = new RestTemplate();
restTemplate.setRequestFactory(factory);
return restTemplate;
}
}
天真的客户端程序：
public void invokeServer(long sleepTime, int concurrentThreads) {
Site site = new Site();
site.setMerchantId("MERC");
site.setSiteId("SITE 100");
CreateSiteRequest request = new CreateSiteRequest();
request.setSite(site);
request.setSleepTime(sleepTime);
ResponseEntity<Site> response = null;
if (concurrentThreads > 1) {
ExecutorService executor = Executors.newFixedThreadPool(concurrentThreads);
Future<ResponseEntity<Site>>[] futures = new Future[concurrentThreads];
Callable<ResponseEntity<Site>> callable;
for (int i = 1; i <= concurrentThreads; i++) {
callable = () -> restTemplate.postForEntity(SAMPLE_SERVER_URL + "site", request, Site.class);
futures[i - 1] = executor.submit(callable);
}
for (int i = 0; i < futures.length; i++) {
try {
response = futures[i].get();
} catch (Exception e) {
log.error("Thread " + i + " " + e.getMessage(), e);
}
}
}
}
@PreDestroy
private void shutdown() throws IOException {
client.close();
connectionManager.close();
}
感谢任何输入.谢谢.
解决方法:
我们遇到了类似的间歇性问题 – 我们离开了RestTemplate并使用了HttpUrlConnection.
内容总结
以上是互联网集市为您收集整理的java – Spring RestTemplate SocketException快速连续执行时连接重置全部内容，希望文章能够帮你解决java – Spring RestTemplate SocketException快速连续执行时连接重置所遇到的程序开发问题。 如果觉得互联网集市技术教程内容还不错，欢迎将互联网集市网站推荐给程序员好友。
内容备注
版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 gblab@vip.qq.com 举报，一经查实，本站将立刻删除。
内容手机端
扫描二维码推送至手机访问。
来源：【匿名】