On Fri, 2008-09-26 at 13:55 -0400, Dale Worley wrote: > On Fri, 2008-09-26 at 13:31 -0400, Dale Worley wrote: > > Currently, if sipXproxy cannot read forwardingrules.xml, it logs a > > message but continues processing. Unfortunately, the forwardingRules > > object that encapsulates the information in the file then contains a > > null pointer, so sipXproxy crashes the first time it would need the > > information in the file to forward a message. > > There seems to be an idea that the supervisor will avoid running > sipXproxy unless forwardingrules.xml is present, but that seems not to > be working. Indeed, that situation seems to be confused, as there is a > sipXproxy-process.xml.in and sipXproxy.process.xml.in in the code base.
One is the new definition and the other is the old one. The old definitions will be removed next week when the new supervisor process control code is made active (it's not _quite_ ready) _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
