John, URLConnection with default Sun's HTTP handler is much worse. It ignores most timeout settings. HttpClient 3 is doing a good job in general. We only found this one issue when the firewall silently drops packet and connection hangs in the native socket code.
I asked this question several months ago on HttpClient list. It was a known issue and they would not do anything with it because HttpClient 3 was nearing end of life. They asked me to try HttpClient 4. It requires code changes and we haven't got to it yet. I already handle this with a timer thread so I don't really need the fix. Let's wait see if others complain. Zhihong On Jul 28, 10:51 am, John Kristian <jmkrist...@gmail.com> wrote: > Is this a common problem? Perhaps the Apache HTTPClient people know > about it. Do URLConnectionClient and/or HttpClient4 have the same > problem? > > I'm willing to develop a decorator for net.oauth.http.HttpClient that > implements a time limit using an executor and a future. But I'd > rather find a way to make the Apache HTTPClient 3 work. > > On Jul 27, 7:10 pm, Zhihong <zhih...@gmail.com> wrote: > > > > > I found that these timeout values don't work sometimes with HTTPClient > > 3. We had a failcase that connection timeout is several minutes when > > firewall blocks the request. > > > If this problem is widespread, it may be a good idea to add an option > > to run the request in a timer-thread using the technique mentioned by > > Paul. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OAuth" group. To post to this group, send email to oauth@googlegroups.com To unsubscribe from this group, send email to oauth+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/oauth?hl=en -~----------~----~----~----~------~----~------~--~---
