Cosmin wrote: > Paul Mossman wrote: > > Scott wrote: > > > >>> Maybe we change the RPM to install sipxconfig.(jar/war) > with a .new > >>> suffix, and then have the start-up script move the files when the > >>> process is re-started? > >>> > >> No... that's not the issue. > >> > >> You need to look at how the refresh is being done on that > page. If > >> the page is maintaining a connection to the server and the > server is > >> periodically sending new content, then doing the upgrade > will break > >> the refresh. If the refresh is being done by a local > script on the > >> page periodically checking for new content, it can be made > to work. > >> The periodic check needs to be to some URL that does not > require any > >> jetty context to fetch (a REST api, probably); something > that returns > >> a value that will be updated after the reboot is complete. > >> > > Hi! > > I will summarize some ideas related to issue > http://track.sipfoundry.org/browse/XX-6524 - Software Update > Screen needs a status indicator. The ideas are about how to > avoid the UI crash(which happens when sipxconfig rpm is > updated) on installation update. So, if you have a > suggestion/opinion related to this, pls share it with us so > we can chose the best way to fix this issue.
So the problem occurs when sipXconfig is updated while it is still serving up the Installation page, which requires a Jetty context. How does the WaitingPage currently work without a Jetty context? -Paul [email protected] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
