I've implemented such a feature locally, but the version I'm using has
many additional changes to make HttpClient work with Java 1.1.8. Once I
find a bit of free time to incorporate the patch into CVS HEAD (is that
what you would like patches submitted against?), I will submit the patch
and of
> The only solution I can see is that perhaps HTTPClient could follow IE's
> approach and close & remove free connections from the connection manager
> pool after a configurable period of inactivity?
>
Matthew,
This sounds like a reasonable addition to HttpClient connection
management capabilit
Ortwin Glück write:
> There is an option to disable stale checking.
Thanks, though turning stale checking off doesn't change the outcome -
the readResponse call still blocks for 30s. I don't think it's the stale
checking that's causing the problem, but for some reason the server
ignores or closes
There is an option to disable stale checking.
Matthew McGowan wrote:
Any ideas how I go about fixing this?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Greetings,
With HttpClient, I'm using the MultiThreadedHttpConnectionManager, with
all timeout values set to 30s, and I'm seeing a problem against a server
that discards unused connections after several minutes. It seems the
connection close isn't detected by the HttpConnection.isStale() method,
w