NetNameResolver timeout
David Farber
dfarber at numenor.com
Mon Dec 9 21:56:33 UTC 2002
Markus - I'm not sure if this is related to your problem, but I posted a bug report to the squeak list back in January:
----
i found this bug over Christmas (on Windows2K, 3.1alpha 3880):
[Socket initializeNetwork] fork.
Socket initializeNetwork.
if you execute
NetNameResolver addressForName: 'www.yahoo.com' timeout: 45
after executing the first snippet, the NetNameResolver takes the full 45 seconds to (correctly) return the resolved address, instead of returning as soon as it is finished.
stoping and restarting Squeak (and doing Socket initializeNetwork without forking) eliminated the problem.
david
At 08:40 PM 12/9/2002 +0100, you wrote:
>Ned Konz wrote:
>
>>>I get "nil" after about 3secs when connected, after unconnecting I
>>>get "nil" immediately.
>>>
>>>This is on 3.4beta-5138, also under w2k.
>>>
>>>I have no DNSException class in my image.
>>>
>>>
>>Sorry, I'm using Linux, and I got the message:
>>
>>'DNSException: Could not resolve the server named: asd.afdsahw.de'
>>
>>
>For the curious: Sometimes, when I startup Squeak, I do not get these
>timeouts. The timeout seems to be never reached. Then, trying to
>reproduce this, I quit and restart the image, I get nil after the
>timeout (a heisenbug?).
>
>My hardware router (=§$(=!$, in future, I'll build my routers myself
>again - that's the only way to assure that they're working correctly)
>sometimes quits the internet connection. And I think, if the DNS is
>unreachable (without any notification), squeak does not care for the
>timeout.
>
>Regards, Markus
>
>--
>http://reauktion.de/archer/
>
>
>
>
--
David Farber
dfarber at numenor.com
More information about the Squeak-dev
mailing list
|