I committed several major changes that affect sipXconfig star-up and
activation.

There were many issues opened recently that we could not solve (or
sometimes even reproduce easily) because of the way sipXconfig used to
manage services. Basically service config replication, setting the
timestamp and service restart were all even driven and might have happen in
pretty much random order.

The idea behind the changes is that sipXconfig will only set the config
stamp once all the configuration files for a service are replicated and
will only (re)start the service once the config stamp is set.

I am not saying that this will automatically solve all the restart issues
with all the services, but at least it will make the initialization process
predictable and hopefully will let us to kill the remaining bugs effectively.

So give it a try: if you have the old issue related to restart please
retest it. If you notice a new issue please open it.

More details in comments here:
http://sipxecs.sipfoundry.org/ViewVC/sipXecs?view=rev&rev=14751
http://sipxecs.sipfoundry.org/ViewVC/sipXecs?view=rev&rev=14752
http://sipxecs.sipfoundry.org/ViewVC/sipXecs?view=rev&rev=14753
http://sipxecs.sipfoundry.org/ViewVC/sipXecs?view=rev&rev=14754

For sipXconfig hackers:
ServiceConfigurator is now responsible for safe service replication and
restart. It's using eager replication context which makes it easy to write
code that does something after replication happens (no need to handle the
events). ServiceConfigurator is itself proxied through background executor:
which means that all its methods will execute in a separate thread.

SipxServiceManager handles "static" aspects of the service management only.
DB access, model retrieval etc.

There is also a ConfigVersionManager utility but probably no other
component apart from ServiceConfigurator needs to use it.

D.

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to