[Seaside] Re: NetNameResolver timeout

[David Farber]

Doing 

[Socket initializeNetwork] fork.
Socket initializeNetwork.

messes up something--most likely a semaphore in the VM. In this case, the name resolver waits for the entire timeout before returning. Exiting Squeak and restarting the image resolves the problem.

The tricky it is that the two lines of code can be spread fairly far apart and the problem still occurs. That makes it tricky to catch.

david

At 05:00 PM 2/5/2003 +0300, you wrote:
>
>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
>_______________________________________________
>Seaside mailing list
>Seaside at lists.squeakfoundation.org
>http://lists.squeakfoundation.org/listinfo/seaside
>
>
--
David Farber
dfarber at numenor.com