TechNote

Flash Media Interactive Server application unexpectedly quits after reloadApp is called

Issue

In Adobe Flash Media Interactive Server, the reloadApp administrator API or HTTP command may not work properly when the numprocs value of the <Distribute> tag in Application.xml is greater than one and no instance is defined.

Reason

The <Distribute> tag in Application.xml contains settings to distribute the load of Flash Media Interactive Server applications over multiple core processes. The numprocs value identifies the number of core processes to distribute the load. The <Scope> tag identifies the level at which to distribute the load (VHost, Application, etc). If numprocs is greater than one, any core may be running any application instance because the load is randomly distributed. If reloadApp is called without naming an application instance, only the _definst_ instance will reload and any other instances that share the same core as the _definst_ instance will be shut down. Instances on cores that do not contain _definst_ will be left running.

Solution

Call reloadApp and specify a target instance of the application that needs to reload. For example, if the two instances _definst_ and redinst need to be reloaded, call reloadApp twice and specify _definst_ in one call and redinst in the other call.