More info: I found out that the web site returns multiple IP addresses on the DNS lookup (see the "Resolving i2.sinaimg.cn line below). This appears to be for load balancing purposes. Could this be the reason that got Android confused?
$ wget http://i2.sinaimg.cn/IT/2009/1014/20091014235428.jpg --23:20:59-- http://i2.sinaimg.cn/IT/2009/1014/20091014235428.jpg => `20091014235428.jpg.1' Resolving i2.sinaimg.cn... 61.172.207.61, 61.172.207.62, 61.172.207.64, ... Connecting to i2.sinaimg.cn|61.172.207.61|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 93,820 (92K) [image/jpeg] On Oct 14, 9:53 pm, "[email protected]" <[email protected]> wrote: > My problem may not be the same. I got this only on actual G1 device, > not on emulator. > > Also, if G1 is connect to my home WiFi network (comcast), the DNS for > i0.sinaimg.cn is resolved without any problem. However, if I > disconnect Wifi and use TMO USA 3G network, the DNS never resolves. > > On Oct 14, 9:29 pm, for android <[email protected]> wrote: > > > > >http://code.google.com/p/android/issues/detail?id=2764 > > > On Thu, Oct 15, 2009 at 4:40 AM, [email protected] < > > > [email protected]> wrote: > > > > Hello, > > > > This happens only when my G1 phone is on T-Mobile network: > > > > I found that when I try to go to the browser, and type the address > > > > http://i0.sinaimg.cn/ > > > > The browser tries to load the page, but no progress is shown for more > > > than 2 minutes. > > > > (I have full 3G signal; all other addresses work just fine) > > > > Eventually when I tried to access this URL in my Java code, I found a > > > similar long delay when I try to open the HttpUrlConnection, and > > > eventually I get this exception: > > > > I/InetAddress( 1940): Unknown host i0.sinaimg.cn, throwing > > > UnknownHostException > > > W/System.err( 1940): java.net.UnknownHostException: Host is > > > unresolved: i0.sinaimg.cn:80 > > > W/System.err( 1940): at java.net.Socket.connect(Socket.java:1002) > > > > Why would DNS take so long? Also, if my program tries to issue the > > > same HTTP request again, the same 2+ minute blocking happened. > > > > Is this an Android bug or a T-Mobile infrastructure bug? It seems the > > > Android API should try to time-out faster, especially on the second > > > attempt.- Hide quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
