Kbase P98384: What processes are started when the AdminServer starts?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
4/14/2010 |
|
Status: Verified
GOAL:
What processes are started when the AdminServer starts?
GOAL:
How many _mprosrv processes are spawned at database startup?
GOAL:
How many processes are spawned for the Database, NameServer, AppServer Broker, and WebSpeed broker ?
GOAL:
How many Java processes are started when the AdminServer starts?
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
FIX:
The number of processes started when the AdminServer is started depends on what AdminServer components are set to auto start.
If NameServer, database broker, AppServer broker and WebSpeed broker are all set to auto start when admin server starts, here is a list of processes that will start:
The following is a list of AdminServer components and the processes that will be started be started for each:
AdminServer process = One java process.
NameServer process = One java process (1 is auto-started by default).
Per Database:
One _mprosrv process per broker.
One _mprosrv process for each remote server that is spawned (up to -Mn).
One _mprshut process for each APW (1 is configured to autostart by default).
One _mprshut process for BIW (1 is configured to autostart by default).
One _mprshut process for WatchDog (1 is configured to autostart by default).
Per AppServer broker:
One Java process per broker.
One _proapsv process for each AppServer Agent that is spawned (can be configured to pre-start when the broker starts).
Per WebSpeed broker:
One Java process per broker.
One _progres process for each WebSpeed Agent that is spawned (can be configured to pre-start when the broker starts).
The DataServers and Adapters will also start a related process per DataServer or Adapter, if they are autostart enabled.