> -----Original Message----- > From: Oleg Kalnichevski [mailto:[email protected]] > Sent: Tuesday, May 18, 2010 3:04 PM > To: HttpClient User Discussion > Subject: Re: With HttpClient 3.0.1, is there some situation where > setting the "SoTimeout" would be ignored? > > On Tue, 2010-05-18 at 14:36 -0700, KARR, DAVID (ATTSI) wrote: > > I'm looking at a situation where I'm setting the "SoTimeout" in > > HttpClientParams to 90000 (90 seconds). This makes a call to a web > > service that under certain circumstances takes quite a while to > > complete, and sometimes times out. In fact, the data in my log file > > indicates that I often get start-to-return intervals of just about > 120 > > seconds. If the back-end server is still working on the request > after > > 90 seconds, will HttpClient be able to cause the request to abort? > > > > David, > > The setting is not ignored, rather your expectation is wrong. The > socket > timeout is the maximum period of inactivity between two _consecutive_ > data transmissions. As long as the server sends a packet every 90 > seconds the request will not time out. > > Hope this clarifies things a little
Yup, that clarifies this perfectly. Thanks.
