Kollipara, Seshu-Babu AVAYA (AMR:9T40) wrote:
> This is regarding issue :http://track.sipfoundry.org/browse/XX-6268
> :"service restart required" message is not displayed until navigated to
> different page or clicked on Apply button again
>  
> Cause of the issue is BackgroundTaskInterceptor is not doing
> marking service for
> restart(ServiceConfiguratorImpl.markServiceForRestart()), before the UI
> calls StatusWarning.showRestartWarning() & renders the web page. So
> StatusWarning.showRestartWarning()  doesn't know that there are services
> for restart & the UI doesn't display the "One or more services need to
> be restarted. For details click: here
> <https://scs6:8443/sipxconfig/admin/commserver/RestartNeededServicesPage.html>"
>  link
> at the top of the page.
>  
> The information that there are services for restart has
> to be marked before UI starts rendering page. This is not happening now.
> Please suggest a approach to solve this issue.

It makes sense to have ServiceConfigurator functions run in a background 
thread, as replications done through this class are blocking. This will free up 
the UI thread to go about its own business. The basic behavior is correct in 
the sense that the message only comes on once the replication is completed, and 
the services are ready to be restarted. The problem is, the notice does not 
show up, until you reload the page. One thing we could look into is using an 
autorefresh form to reload the StatusWarning component every once in a while. 
The Date component used to do this previously, and caused a lot of headaches, 
so we have to be careful here.

> I have made comparison to a working case too, at different place in
> like Paging ->Change the log level ->  Press save
> Here the services are marked for restart using
> LazyDialPlanActivationManager.replicateDialPlan & there is no timing
> problem.

LazyReplication replicates the files in a separate thread, a few minutes after 
the change. We probably shouldn't be displaying the notice, before it has had a 
chance to replicate the files.

Arjun
_______________________________________________
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/

Reply via email to