On Fri, 2010-03-05 at 11:32 -0500, Paul Mossman wrote: > Regarding XX-6524 [1], we had an earlier discussion [2] of a problem > Cosmin found where the update of sipxconfig.(jar/war) causes HTTP ERROR > 500 on a refreshing Software Installation page. We didn't reach > consensus on how to get around this problem. > > I would like to re-propose a work-around: Change the RPM to install > sipxconfig.(jar/war) with a .new suffix, and then have the sipxconfig.sh > script move the file(s) when the process is re-started? > > Unless someone can suggest a simpler work-around, I'd like Cosmin to > give this a try.
Apologies for not responding sooner - this slipped by me. This suggested workaround would be very poor practice, since it would misrepresent the ownership of the files installed by the rpms. You can't make an rpm responsible for a file it doesn't install, and if you rename it then rpm will loose track of it. In an earlier post, Cosmin suggested: > - another idea is to use a REST service(outside Jetty context) for > getting the installation log, so this way UI won't crash. Here, the > question is where the REST service should be placed so that it won't > be affected by the installation? If you implement it as an apache cgi, then it won't be affected by an upgrade in progress (frankly, I'm not sure why jetty can't cope with this, but that would just start me on a java rant, so I won't go there). _______________________________________________ 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/
