On Thu, 2009-02-05 at 14:47 -0500, Dale Worley wrote: > On Thu, 2009-02-05 at 13:56 -0500, Scott Lawrence wrote: > > In a recent sipxsupervisor.log, I find many entries like (timestamp > > removed): > > > > SUPERVISOR:WARNING:sun.qantom.int:HttpServer-3:B7C99B90:Supervisor:'SIPRegistrar': > > > > Received unexpected event evConfigurationChanged while in state 'Running' > > > > I don't think this should be a WARNING - getting new configuration while > > in Running state is not abnormal or unexpected - it's routine. This > > should be reworded and lowered to NOTICE level, I think. > > More important: Do we know that the supervisor handles this case > correctly?
That log entry indicates that the state machine has been told that some resource used by the process has changed (something has been replicated, typically). The current defined behavior of sipXsupervisor is to do nothing with that knowledge (which, aside from this log entry, is what it does). In some future version, we may add the functionality that it notifies the process in some way to reread the configuration. Some data sets (all the IMDB tables) are of course shared, so the process will see the updates. So, the answer is... yes, it does the currently correct thing, but it logs a scary message that looks as though something bad may have happened. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
