If the Configuration Software Process (Logical Server) Terminates Abnormally

The method for restarting the system, when Application Server configuration software process terminates abnormally, is described here.

In a system build on Application Server, if the start order is set up when the component software process (logical server) of Application Server terminates abnormally, the Management Server will automatically restart the component software. In the Management Server, the processing of component software is managed as Logical Server.

When restarting manually, if the abnormally terminated configuration software has startup dependencies, confirm that the configuration software, on which the abnormally terminated configuration software depends for starting, is running. The configuration software, on which the abnormally terminated configuration software depends, varies depending on the configuration of the system. The startup dependencies of the configuration software and the method of restarting the configuration software are explained below:

Hint: In a system using CTM, if component software is restarted immediately by CTM, you can specify settings in such a way so that the system is recovered before the error is returned to the client. However, when the number of maximum registration of the request queue exceeds, an error will return to the client.; For details on a system using CTM, see 3. CTM-based Request Scheduling and Load Balancing in the uCosminexus Application Server Expansion Guide.

Organization of this subsection: (1) Configuration software startup dependencies; (2) Restart method of the process

(1) Configuration software startup dependencies

The startup dependencies of the configuration software process configuring a system built with Application Server are explained here.

Hereafter, the configuration software process startup dependencies are explained for each J2EE server operation mode:

(a) Dependencies of the process

The dependencies of the process are as follows:

Table 2-8 Dependencyof processes

Process type	Dependant process
Performance tracer	--
Smart Agent^{#1, #2}	--
CTM domain manager^#1	Smart Agent^{#1, #2}
CORBA naming service	--
CTM daemon^#1	Performance tracer Smart Agent CTM domain manager CORBA naming service
SFO server	Performance tracer
J2EE server	Performance tracer Smart Agent CTM domain manager^#3 CORBA naming service^#4 CTM daemon^#3
Web server	Performance tracer

Legend:: --: There is no prerequisite process.

#1: It is a process to be started when using CTM.

#2: It is a process to be started when using the transaction service.

#3: This process is a prerequisite when using CTM.

#4: It is a process to be started when using the CORBA naming service in out-process. It is not required when using the CORBA naming service in in-process.

(2) Restart method of the process

The restart method of a process when the process terminates abnormally in a system is as follows.

Hint

When a CTM-related process abnormally terminates and cannot be started, use the following procedure:

When you cannot restart the process, check the cause of the trouble from the output error message.
Execute the ctmrasget command, and acquire backup of the execution environment.

(a) Restart procedure

The procedure of process restart (recovery) is as follows:

Table 2-9 Procedureto restart (recovery) processes

Abnormal process	Start command	Restart (recovery) procedure
Database server	--	Restart the DB server.
OpenTP1	--	Restart the OpenTP1.
Performance tracer	cprfstart	Restart the performance tracer.
Smart Agent^{#1, #2}	Osagent	Restart the Smart Agent.
CTM domain manager^#1	ctmdmstart	Restart the CTM domain manager.
CORBA naming service	Nameserv	Perform actions based on the procedure shown below. Furthermore, when CTM is not used, procedure 1 and 4 are not required. Forcefully terminate the CTM daemon Forcefully terminate the J2EE server Restart the CORBA naming service Restart the CTM daemon J2EE server restart
CTM daemon^#1	ctmstart	Perform actions based on the procedure shown below. CORBA naming service forced termination Forcefully terminate the J2EE server Restart the CORBA naming service Restart the CTM daemon Before restarting the J2EE server
CTM regulator	--	Since restarted automatically by CTM daemon, restart is not required.
SFO server^#3	cjstartsv	Restart the SFO server.
J2EE server	cjstartsv	Restart the J2EE server.
Web server	--	Restart the Web server.

Legend:: --: The start command differs depending on the products used or there is no corresponding start command.

#1: It is a process to be started when using CTM.

#2: It is a process to be started when using the transaction service.

#3: It is the process to be started when using the memory session failover function.

2.5.1 If the Configuration Software Process (Logical Server) Terminates Abnormally

(1) Configuration software startup dependencies

(a) Dependencies of the process

(2) Restart method of the process

(a) Restart procedure