Christiaan Lamprecht wrote:
Hi all,
Just a quick question on some "abnormally" large timeouts if anyone can help.
Socket timeout defines a maximum of period inactivity between two
_consecutive_ I/O operations.
Hope this helps
Oleg
I have a couple of clients sending requests to a server and I'm
measuring the response time. Some simple code:
start = System.currentTimeMillis();
statusCode = httpclient.executeMethod(hostconfig, method, null);
end = System.currentTimeMillis();
I have also set the following (and using SSL):
httpClient.getParams().setParameter("http.protocol.version",
HttpVersion.HTTP_1_1);
httpClient.getParams().setParameter("http.socket.timeout", new Integer(6000));
httpClient.getParams().setParameter("http.connection.timeout", new
Integer(6000));
httpClient.getParams().setParameter("http.tcp.nodelay", true);
httpClient.getParams().setParameter(HttpMethodParams.RETRY_HANDLER,
new DefaultHttpMethodRetryHandler(0, false));
As the server gets busier I start to get quite a few
SocketTimeoutExceptions. From the data collected I can see the ones
which timed out, as their durations are all just above 6000, there are
however a large number of request durations (for this particular
experiment) in the range 10000-70000. I've checked the CPU load on the
clients and it's quite low. I've also tried smaller timeout values but
still get large response time values (though understandably not quite
as large as the previous example)
I checked previous posts on the newsgroup but not quite sure what to look for!?
Thanks again for any help
Christiaan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
