Updates:
Status: Fixed
Comment #3 on issue 181 by
[hidden email]: WAGsSwazooAdaptor>>start
hangs after listener thread exits
http://code.google.com/p/glassdb/issues/detail?id=181I've looked into this WAGsSwazooAdaptor>>start and while it looks like
somewhat suspicious code, it is not the reason that gems don't fall over
when they are sick ...
If a swazoo gem hits an explicit error or halt, the gem will go ahead an
fall over, so a gem can fall over it this process never exits ... the basic
problem with swazoo is that under certain conditions it will _silently_
stop listening on the port...without an internal indication that something
went wrong, external measures must be taken to determine whether the server
is alive or not ... a solution that Sean used in his installation ...
Oh there is an #isRunning message that could be sent, but it looks like in
the silent death case noone #isRunning continues to return true...
Calling this bug fixed ...
Locked
