You can configure an Application Server to spawn processes externally to the Application Server process. If you configure an Application Server in this way, a separate dedicated process (the process spawner) is used only for spawning processes. When the Application Server needs to spawn a process, it contacts the process spawner, which starts a new child process. The Application Server transfers the necessary information to the child process. Spawning processes externally can be beneficial for memory management. Primarily, an Application Server spawns processes for Network Shell Script Jobs and some types of extended objects.
To configure the process spawner, perform the following procedures:
blasadmin -s JobServer1
To specify that processes be spawned externally from the Application Server process, enter the following:
set ProcessSpawner SpawnExternally true
Setting this value to false indicates the process spawner runs within the Application Server process. By default, this value is set to false.
If you set the
ProcessSpawner SpawnExternally value to
true, BMC recommends that you run the following command before starting the Application Server service (to avoid
connection refused failures for any scheduled jobs):
run/etc/init.d/blprocserv start (UNIX)
net start "BladeLogic Process Spawner" (Windows)
set ProcessSpawner RegistryPort #
blasadmin -s _spawner
set AppServer RegistryPort #