Thanks Sven, I'm gonna try to reinitialize Davide Sven Van Caekenberghe wrote
Zn on its own has a mechanism to stop/start servers on images save/startup. Have a look at the class side of ZnServer. Servers can register themselves to become managedServers for the above behavior.
Now, for Zn itself this only happens for the default server, the one you start with #startDefaultOn: or the one you create with #defaultOn: For all other servers, you will have to send #register yourself.
Seaside does its own management, independent from Zn. The Zn server that is started by WAServerManager using ZnZincServerAdaptor is *not* managed by Zn, but it *is* by Seaside.
It seems that you manually broke things. I would suggest to re-initialize WAServerManager.
HTH,
Sven
-- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill
-- View this message in context: http://forum.world.st/Explore-Pointers-ad-startup-errors-tp4612597p4612964.h... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.