Hi,
I am eager to squeeze the most performance out of my usage of HttpClient
4.0 and have been reading the archives where it was suggested to disable
the stale connection check. I have done this, and it does indeed
significantly improve performance, however I am now occasionally getting
the following two exceptions:
1. Exception in thread "main" java.net.SocketException: Connection
reset by peer: socket write error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at
org.apache.http.impl.io.AbstractSessionOutputBuffer.flushBuffer(AbstractSessionOutputBuffer.java:106)
at
org.apache.http.impl.io.AbstractSessionOutputBuffer.flush(AbstractSessionOutputBuffer.java:113)
at
org.apache.http.impl.AbstractHttpClientConnection.doFlush(AbstractHttpClientConnection.java:260)
at
org.apache.http.impl.SocketHttpClientConnection.close(SocketHttpClientConnection.java:248)
at
org.apache.http.impl.conn.DefaultClientConnection.close(DefaultClientConnection.java:154)
at
org.apache.http.impl.conn.AbstractPooledConnAdapter.close(AbstractPooledConnAdapter.java:131)
at
org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:130)
at
org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:447)
at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641)
at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:730)
at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:708)
at
org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:699)
...
2. DefaultRequestDirector:455 - I/O exception
(org.apache.http.NoHttpResponseException) caught when processing
request: The target server failed to respond
DefaultRequestDirector:462 - Retrying request
The first one is problematic because the program terminates (I don't
handle the exception anywhere). The second one usually retries as I am
using the DefaultHttpRequestRetryHandler, but on occasion the program
has just exited too (without doing the 5 retries that I have requested -
I am trying to capture this case in a debugger so I can get a clue as to
what is happening, will post an update if I find anything). The second
error is far more frequent than the first, for example today I have seen
the second error about 50 times, but the 1st error only once.
Anyway, I presume that both these errors are only now apparent because I
have disabled the stale connection check.
What advice can you give me on how to recover from the first problem?
It is important that I don't re-post my requests if they did manage to
get through before the error occurred.
For the second one, is it 100% safe to resume from that error? Is it
fully equivalent in terms of network communications as having the stale
connection check enabled?
Out of interest, what is the history of the stale connection check?
From reading the archives it appears it is a relic of an older
HttpClient, and its usage is not recommended anymore. Is this correct?
If so, why isn't it just removed from the latest version, and
substituted with a robust retry handler that can deal with all the
consequences?
Many thanks,
Tony
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
