Scott Lawrence wrote:
On Wed, 2010-01-27 at 21:21 -0500, Paul Mossman wrote:
Cosmin wrote:
...
after updating the software(please see the comments). This
issue tells that after an update, sipxconfig.(jar/war) and
others are changed, but the installation page is still
running and refreshing, so an error will occur(HTTP ERROR:
500 - maybe because jetty doesn't support hot deploy). It
seems to happen only when sipxconfig rpm is updated. The
error shown that time is displayed bellow:
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.
The error page will be displayed while the updates are installing. What
I am using for the refresh is an AutoRefresh component which ask the
server to update periodically the log content.
I was thinking for an easier solution described in the following scenario:
The user enters in the "Software Updates" page. Clicks "Check for
updates" button and then "Install updates" button.
On the installation process, all the rpms are updated with the exception
of sipxconfig rpm(for this we'll have to change in the pyton script "yum
update -y --disablerepo=* --enablerepo=sipxecs*" with "yum
*--exclude=sipxconfig** update -y --disablerepo=*
--enablerepo=sipxecs*"). So almost all the sipx rpms are installed, but
not the sipxconfig rpm, so the UI will continue to work. Immediately
after this update, the user is redirected to the Waiting page, where the
sipxconfig rpm is installed(if there exists an update for it) and the
server is restarted.
I belive using this way the user won't see any more the 500 HTTP error page.
_______________________________________________
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/
