madawei2699
commented
2 years ago After going through clj-http code, I write a sample java version to compare the results.
public class Main {
public static void main(String[] args) throws IOReactorException {
RequestConfig requestConfig = RequestConfig.custom()
.setConnectTimeout(1)
.setSocketTimeout(500)
.setRedirectsEnabled(true)
.build();
HttpUriRequest httpUriRequest = new HttpGet("http://255.255.33.44:8001/");
httpUriRequest.addHeader("Connection", "close");
IOReactorConfig reactorConfig = IOReactorConfig.custom()
// .setConnectTimeout(500)
// .setSoTimeout(500)
.setShutdownGracePeriod(1)
.build();
DefaultConnectingIOReactor defaultConnectingIOReactor = new DefaultConnectingIOReactor(reactorConfig);
Registry registry = RegistryBuilder.create()
.register("http", NoopIOSessionStrategy.INSTANCE)
.build();
PoolingNHttpClientConnectionManager connectionManager = new PoolingNHttpClientConnectionManager(defaultConnectingIOReactor, registry);
HttpClientContext context = new HttpClientContext();
context.setRequestConfig(requestConfig);
connectionManager.setMaxTotal(1);
CloseableHttpAsyncClient client = HttpAsyncClients.custom()
.setConnectionManager(connectionManager)
.build();
client.start();
long startTime = System.nanoTime();
client.execute(httpUriRequest, context, new FutureCallback<HttpResponse>() {
@Override
public void completed(HttpResponse httpResponse) {
StatusLine statusLine = httpResponse.getStatusLine();
int statusCode = statusLine.getStatusCode();
long stopTime = System.nanoTime();
System.out.print("=====completed, timeElapsed: ");
System.out.print(TimeUnit.MILLISECONDS.convert(System.nanoTime() - startTime, TimeUnit.NANOSECONDS));
System.out.println(" ms");
System.out.print(statusCode);
}
@Override
public void failed(Exception e) {
System.out.print("=====failed, timeElapsed: ");
System.out.print(TimeUnit.MILLISECONDS.convert(System.nanoTime() - startTime, TimeUnit.NANOSECONDS));
System.out.println(" ms");
System.out.print("=====error msg: " + e.getMessage());
try {
connectionManager.shutdown();
} catch (IOException ex) {
ex.printStackTrace();
}
}
@Override
public void cancelled() {
httpUriRequest.abort();
try {
connectionManager.shutdown();
} catch (IOException e) {
e.printStackTrace();
}
}
});
}
}When setConnectTimeout(1), the time elapsed is ~1129ms.
When setConnectTimeout(500), the time elapsed is ~1142ms.
When setConnectTimeout(1000), the time elapsed is ~1115ms.
When setConnectTimeout(1100), the time elapsed is ~2099ms.
When setConnectTimeout(1200), the time elapsed is ~2106ms.
When setConnectTimeout(1300), the time elapsed is ~2091ms.
When setConnectTimeout(1500), the time elapsed is ~2095ms.
When setConnectTimeout(2000), the time elapsed is ~2110ms.
When setConnectTimeout(2500), the time elapsed is ~3121ms.
When setConnectTimeout(3000), the time elapsed is ~3098ms.
When setConnectTimeout(4000), the time elapsed is ~4117ms.
When setConnectTimeout(5000), the time elapsed is ~5110ms.
So it seems like code execute time is about ~1000ms, it takes at least 1 second from the start of the request to fail if the connect timeout is less than ~1000ms.
But synchronous requests do not have such high latency (interval from request to failure), I guess because asynchronous requests require a lot of setup code to be processed, including the creation of connection pools, so the creation of asynchronous request clients is time-consuming expensively.
DerGuteMoritz
Backgroud
When using clj-http async requests some do not exist URL and set the connection timeout, but the connection timeout is delayed 2-3 seconds.
Test
The test version is
3.12.2, and the test way islein repl, my lein config in~/.lein/profiles.clj:and then, run
lein replto go to the repl environment.Example 1
Expectation
Cause the URL does not exist, so the time will be conn-timeout which is ~1ms.
Test Result
"Elapsed time: 3019.764098 msecs" {:error "Timeout connecting to [/255.255.33.44:8001]"}
Example 2
Expectation
Cause the URL does not exist, so the time will be conn-timeout which is ~5000ms.
Test Result
"Elapsed time: 7203.527474 msecs" {:error "Timeout connecting to [/255.255.33.44:8001]"}
Example 3
Expectation
Cause the URL does not exist, so the time will be conn-timeout which is ~5000ms.
Test Result
"Elapsed time: 5010.862797 msecs" "caught exception: connect timed out"
Example 4
Expectation
Cause the URL does not exist, so the time will be conn-timeout which is ~1ms.
Test Result
"Elapsed time: 8.649284 msecs" "caught exception: connect timed out"
Bug
As in the above test, Example 1 and Example 2 are test requests in
asyncmode, and Example 3 and Example 4 are control requests insyncmode. Thesyncmode request is as expected, but the async mode request is 2-3 seconds longer than the set conn-timeout.