Hi!
I just wanted to load the PackageLoader. The somehow, the name couldn't be resolved (I think that's my fault). But: NetNameResolver class>>addressForName:timeout: should timeout after five seconds (the given time out from the SqueakMap load script), but I think it doesn't care for this timeout; it seems that NetNameResolver waiting for the name of 'map1.squeakfoundation.org' after a longer period of time (on Windows). Could anyone reproduce this behavior, or do I understand the meaning of "timeout" wrong?
NetNameResolver addressForName: 'asd.afdsahw.de' timeout: 5 does not raise an error or return after five seconds here.
Regards, Markus
Markus Fritsche wrote:
NetNameResolver addressForName: 'asd.afdsahw.de' timeout: 5 does not raise an error or return after five seconds here.
Hm, it seems like I ran into some weird again :-) (for the curious: I took an 3.0 image and updated it to 3.4alpha by the online-update mechanism. It seems that this way the NetNameResolver somehow got broken).
Mea culpa!
Regards, Markus
Markus Fritsche Fritsche.Markus@gmx.net wrote:
Markus Fritsche wrote:
NetNameResolver addressForName: 'asd.afdsahw.de' timeout: 5 does not raise an error or return after five seconds here.
Hm, it seems like I ran into some weird again :-) (for the curious: I took an 3.0 image and updated it to 3.4alpha by the online-update mechanism. It seems that this way the NetNameResolver somehow got broken).
Mea culpa!
Not relevant perhaps but just so you know: map1 is mapped to anakin.bluefish.se but there is no SqueakMap server there yet.
This whole NetNameResolver/proxy-mess is getting on my nerves - can someone come up with a working mechanism here? The problems:
1. The above (which I didn't know about). 2. The httpGet: doesn't fail properly - that is why I inserted the "precheck" using NetNameResolver in the first place. 3. NetNameResolver doesn't work when using a proxy - but that is probably correct I guess.
Number 1 I don't know much about but number 2 would really be nice to have eliminated since it would "solve it all" for SqueakMap at least. And I faintly recall that someone posted a fix about this - was it Bijan? Perhaps that should be picked up. :-)
regards, Göran
Markus Fritsche wrote:
NetNameResolver addressForName: 'asd.afdsahw.de' timeout: 5 does not raise an error or return after five seconds here.
Could some of you do a print it of the above code line and report the result, please, one time with the network plugged, one time not (so that the nameserver is not reachable)?
Tia, Markus
On Monday 09 December 2002 07:12 am, Markus Fritsche wrote:
Markus Fritsche wrote:
NetNameResolver addressForName: 'asd.afdsahw.de' timeout: 5 does not raise an error or return after five seconds here.
Could some of you do a print it of the above code line and report the result, please, one time with the network plugged, one time not (so that the nameserver is not reachable)?
I get a DNSException in both cases (at least after doing an ifdown eth0).
Ned Konz wrote:
I get a DNSException in both cases (at least after doing an ifdown eth0).
You're using KMail, so I think you're under Unix/Linux, right? Under w2k this error isn't signalled correctly - at least with my image.
Regards, Markus
Markus Fritsche wrote:
Ned Konz wrote:
I get a DNSException in both cases (at least after doing an ifdown eth0).
You're using KMail, so I think you're under Unix/Linux, right? Under w2k this error isn't signalled correctly - at least with my image.
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.
On Monday 09 December 2002 10:53 am, Joern Eyrich wrote:
Markus Fritsche wrote:
Ned Konz wrote:
I get a DNSException in both cases (at least after doing an ifdown eth0).
You're using KMail, so I think you're under Unix/Linux, right? Under w2k this error isn't signalled correctly - at least with my image.
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'
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
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
-- David Farber dfarber@numenor.com
I'm on Mac OS X. Squeak 3.4 beta. Everything was working fine until one day NetNameResolver decided not to return and only to hang (I am connected to the network). Nothing is changed or different, that I can perceive. I don't deal with socket code (that I know of). NetNameResolver only hangs now.
Thank you in advance, Derek
On Monday, December 9, 2002, at 01:56 PM, David Farber wrote:
[Socket initializeNetwork] fork.
Nerd on a Wire: Web and Information Solutions Website Design - Database Systems - Site Hosting 604.874.6463 mailto:info@nerdonawire.com For more information, visit http://nerdonawire.com
I've seen the name resolver's semaphore get locked without being released. That results in the behavior Derek describes. I have no idea how this happens, but you can solve it by enterring a debugger and signalling the semaphore that is being waited on.
Note, this fix may end up screwing up your image later, though, in case there really is some process blocked inside a name lookup and it finally returns. So this is more of a temporary fix, and you should probably reload everything in a new image. Project fileouts can make this very smooth.
-Lex
squeak-dev@lists.squeakfoundation.org
-
David Farber -
Derek Brans -
goran.hultgren＠bluefish.se -
Joern Eyrich -
Lex Spoon -
Markus Fritsche -
Ned Konz