31
FLASH
MEDIA
SERVER
4.5
CONFIGURATION
AND
ADMINISTRATION
Configuring the server
Last updated 11/28/2012
Configure the number of core processes and how long each process runs
❖
Specify the number of core processes in the
MaxCores
tag (the maximum number of core processes that can exist
concurrently) and the number of seconds that a core process can run in the
RollOver
tag. When a core process
reaches the limit, any new connections roll over to a new core process.
The following diagram depicts the way in which the server rolls over processes. In the XML, the rollover time is set
to 3600 seconds (1 hour), indicating that every hour a new process should start, and the maximum core processes
value is set to 3, indicating that the maximum number of processes at any given time is 3:
<Process>
<Scope>app</Scope>
<LifeTime>
<RollOver>3600</RollOver>
<MaxCores>3</MaxCores>
</LifeTime>
...
A. Client connections B. Process 1 starts C. Process 2 starts D. Process 3 starts E. Process 4 starts; Process 1 ends, because the maximum core
processes limit was reached
When each process starts, it accepts new connections until the next process starts: that is, when process 1 starts, it
accepts new client connections to the application until process 2 starts; process 2 then accepts new client
connections until process 3 starts; and so on.
Note that the duration of process 1 might or might not be the full duration specified by the rollover value, because
rollover values are calibrated to the real clock time. The duration of process 1 is partially determined by the current
time when process 1 starts. For example, as shown in the diagram, when process 1 starts, the current time is 12:20,
so the duration of process 1 is only 40 minutes (because it is 40 minutes until the beginning of the hour in real time).
The duration of the first process is determined by the clock time; subsequent processes have a duration equal to the
specified rollover time.
To disable this feature, set
RollOver
to 0. This feature is disabled by default.
Note:
If you have multiple VHosts with
Process/Scope
set to
adaptor
, you must set an identical
RollOver
value
for each VHost.
In stateless applications, such as vod applications, old core processes continue to serve earlier connections. In this
case, you can specify a value in the
MaxCores
tag to limit the maximum number of core processes that can run
simultaneously. If the application is not stateless, the server ignores any value you assign to
MaxCores
and sets it to
1
. This ensures that an application instance is not split across multiple processes, but clients are disconnected
periodically. To disable this feature, set
MaxCores
to 0. This feature is disabled by default.
Note:
An application is considered stateless if you configure it to distribute clients over multiple processes. To do this,
set the
Distribute numprocs
attribute to a value greater than 1, then set the
Distribute
tag to
clients
or set the
Scope
tag to
inst
.
12:00
1:00
2:00
3:00
4:00
5:00
12:20
A
E
D
B
C