; in HttpClient 3.0 could be particularly useful for this.
>
> Do you have a particular use in mind?
>
> Mike
>
>
>
> On Oct 4, 2004, at 1:24 PM, Vijay wrote:
>
> > Sorry if this is a very basic question:
> >
> > I would li
method
in HttpClient 3.0 could be particularly useful for this.
Do you have a particular use in mind?
Mike
On Oct 4, 2004, at 1:24 PM, Vijay wrote:
Sorry if this is a very basic question:
I would like to set 3 timeouts (connect, send and receive). I found
the following in HttpClient package.
HttpClient.
Sorry if this is a very basic question:
I would like to set 3 timeouts (connect, send and receive). I found
the following in HttpClient package.
HttpClient.setTimeout -- sets socket RECEIVE timeout
HttpClient.setConnectionTimeout -- sets socket CONNECT timeout
Is there any method available for
gzilla/show_bug.cgi?id=31322
SO Timeouts should be finer grained
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
gzilla/show_bug.cgi?id=31322
SO Timeouts should be finer grained
Summary: SO Timeouts should be finer grained
Product: Commons
Version: 2.1 Final
Platform: All
OS/Version: Windows XP
Status: NEW
Severity: Enhancement
Pr
Great, well then I'll start testing 3.0 alpha within our application.
thanks!
Mark
Oleg Kalnichevski wrote:
Mark,
This is not that much of a problem as HttpClient always resets socket
timeout on the active connection prior to executing a method. The
problem is socket timeout setting is simply not t
On Wed, 2004-06-02 at 17:58, Mark R. Diggory wrote:
> So far I'm looking at something like:
>
> HttpConnection connection =
> client.getHttpConnectionManager().getConnection(client.getHostConfiguration());
> connection.setConnectionTimeout(...)
>
> But, my big concern is that this is again just
I've been trying to alter the request timeout period across requests.
For some requests executed in the client, I want to be able to restict
the timeout period, for others I really need to have a much longer
timeout period. This poses a problem, I currently use the
HttpClient.execute method per
Commons HttpClient Project
Subject: RE: Question on Timeouts
Hi ...
Apologies for the lack of an introduction. My name is Mike Coffey (if you
didn't already catch that part) and I'm currently working at CMP Media on a
website project. CMP is a publishing company (we publish DDJ
enough,
sometimes we see the timeouts work appropriately and sometimes the thread the
thread hangs indefinitelyfigures it's one of "those" problems...sigh !
1. We will update to the latest CVS branch, this is something I had in progress
anyway given the problems we're
Kalnichevski, Oleg wrote:
(1) upgrade to 2.0rc3 release. Better yet, upgrade to the latest CVS HTTPCLIENT_2_0_BRANCH snapshot (which is quite likely to be the 2.0 final). We've just recently fixed a minor bug with socket timeouts in persistent connections. I do not think you are affect
snapshot (which is quite likely to be the 2.0 final). We've just
recently fixed a minor bug with socket timeouts in persistent connections. I do not
think you are affected by this bug, but just to be on the safe side
(2) Try setting timeout to a ridiculously low value just to see whether
You seem to be using threads and so I assume you are using the
MultithreadedConnectionManager (you definitely should be!). Oleg just
fixed a bug regarding this issue:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26500
Using the current CVS HEAD (or nightly build) could fix your problem.
asia.com>bcc:
Subject: Re: Question on Timeouts
[EMAIL PROTECTED] wrote:
Hello,
I'm using your product for an application that we're building (that fetches some
HTTP content) and I'm running into an issue where it isn't timing out
< ..snip...>
--This is how we're connecting -
HttpClient client = new Http
Hello,
I'm using your product for an application that we're building (that fetches some
HTTP content) and I'm running into an issue where it isn't timing out and was
wondering if anyone else has seen this before? I've looked through the
FAQ's/Intros/and archives to this list, but haven't quit
I ran into a HttpClient hang at 3 this morning so I now call:
client.setConnectionTimeout(connTimeOut);
client.setTimeout(sockTimeOut);
What are reasonable values, I'm not waiting for the connection to finish
correct, just waiting for valid data? At first I was thinking it's
going to wait for th
17 matches
Mail list logo
