Gustavo, (1) The only way I can think of to provide control over socket timeout during method's execution is to override GetMethod#executeMethod, store the reference to the connection object, and provide direct access to its properties.
(2) The connection timeout on the method level makes no sense to me of what so ever. Most likely the connection will be kept alive between subsequent method executions, anyways. It is (almost) completely non- deterministic. There's no way to say if you get a new connection or an open connection from the pool. I may be wrong here as I do not really know what you are trying to achieve with your application but I would urge you to rethink the design. Oleg On Mon, 2004-12-13 at 16:04 -0600, Gustavo Hexsel wrote: > I can't, the values are different for each run. The reason is because I > have a "general timeout" which includes retrieving and parsing a variable > number of pages. > > []s Gustavo > > > -----Original Message----- > From: Jilles van Gurp [mailto:[EMAIL PROTECTED] > Sent: December 13, 2004 2:41 PM > To: HttpClient User Discussion > Subject: Re: How to set timeout parameters for a method? > > > Don't set the timeouts on the method but on the HttpClient instance. You > can use the setConnectionTimeout and setTimeout methods. > > Jilles van Gurp > > Gustavo Hexsel wrote: > > > Greetings, > > > > does anyone know how to set the timeout parameters (if possible, both > >socket and connection) for a particular method? I tried to make an > accessor > >to the HttpConnection, but as I suspected, it is not created until you try > >to execute the method, and by then is too late, as both connection and > first > >read already happened. > > I tried to do something like this: > > > > method.getParams().setIntParameter("http.socket.timeout", > >remainingTime); // in my logs, remaining time is about 300s > > method.getParams().setIntParameter("http.connection.timeout", > >remainingTime); > > > > Even though "connection timeout" is not supposed to be a valid parameter > >for the method. The log indicated that the parameters were set, but the > >values remained the same as the defaults set before, and I get a > >"SocketTimeout: Read timed out" after about 10s (my default param setting). > > Similarly, even if the first "read()" doesn't time out, I've set the > >connection timeouts to the remaining time (over 280s by then), but still > >times out in the default values (10s). This is the code I'm using: > > > > HttpConnectionParams connParams = > >method.getResponseConnection().getParams(); // I just provided an accessor > >here > > connParams.setConnectionTimeout(remainingTime); > > connParams.setSoTimeout(remainingTime); > > > > > > Any ideas? > > > > > > Thanks a lot, > > > > Gustavo > > > > > >--------------------------------------------------------------------- > >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] > > --------------------------------------------------------------------- > 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]
