On Tue, 2016-11-08 at 10:48 -0500, Murat Balkan wrote: > Hi Oleg, > > From the documentation , I understand that this exception is thrown after > the TCP socket is opened and client sends GET / request. We then start > waiting the response from the server, but it never responds but drops the > connection after 50 seconds in my case (which I believe a server parameter) > > My question is, shouldn't socket timeout timer kick in as soon as the > socket is open? Does it need at least 1 packet to arrive at the client? >
Yes, socket (read) timeout setting should apply. Oleg > Thanks > > On 8 November 2016 at 07:35, Oleg Kalnichevski <ol...@apache.org> wrote: > > > On November 7, 2016 9:16:19 PM GMT+01:00, Murat Balkan <mrbal...@gmail.com> > > wrote: > > >Hi, > > > > > >Which timer does the NoHttpResponseException use? My socket timeout is > > >set > > >around 30 and connection timeout is set to 20. However, I see that in > > >some > > >cases, this exception is thrown after more than 50 seconds. > > > > > >Is there a timeout for org.apache.http.NoHttpResponseException? > > > > > >Thanks > > >Murat > > > > There is no timer. This exception is thrown if the server closes the > > connection on its end without any response what so ever > > > > Oleg > > -- > > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org For additional commands, e-mail: httpclient-users-h...@hc.apache.org
