One of the customer reported that it has been observer that Case Management Server stop script does not stop the Case Management Server process correctly
1. Start case manager
$ /app/arcot/CA/AdvAuth/bin/casemanagementserver start
Operation start being performed on Server CaseManagement Server
All environment variables are set
Arcot arrfcasemgmtserver Watchdog Service initializing ...
2. Case Management Server and watchdog started.
$ ps -ef | grep case
cmcsso 72783 1 0 16:00 ? 00:00:00 /app/arcot/CA/AdvAuth/sbin/arrfwatchdog /app/arcot/CA/AdvAuth/sbin/arrfcasemgmtserver
cmcsso 72784 72783 4 16:00 ? 00:00:00 /app/arcot/CA/AdvAuth/sbin/arrfcasemgmtserver
cmcsso 72791 48518 0 16:00 pts/2 00:00:00 grep --color=auto case
3. Now stop Case Management Server:-
$ /app/arcot/CA/AdvAuth/bin/casemanagementserver stop
Operation stop being performed on Server CaseManagement Server
* * *
Processing sd localhost 7780
* * *
Initiated the shutdown operation with TCP.
Transaction ID:
4. On inspection of the process it seems Case Management Server is still running and only the watchdog has shutdown - it seems that the PPID has become 1
$ ps -ef | grep case
cmcsso 72784 1 1 16:00 ? 00:00:00 /app/arcot/CA/AdvAuth/sbin/arrfcasemgmtserver
cmcsso 72902 48518 0 16:00 pts/2 00:00:00 grep --color=auto case
5. Start Case Management Server again
$ /app/arcot/CA/AdvAuth/bin/casemanagementserver start
Operation start being performed on Server CaseManagement Server
All environment variables are set
CaseManagement Server already running
CA Advanced Authentication 9.1.04
The Case Management script tries to kill the PPID which is “1” which it will never be allowed to do.
Operation stop being performed on Server CaseManagement Server
/app/arcot/CA/AdvAuth/bin/casemanagementserver: line 254: kill:(1)- Operation not permitted
We have developed a new case management stop script which will kill the PID of the process instead of PPID. Please use this patch/hotfix from attachment to install in your environment if you face similar issues.