Siebel Services Not Stopping Gracefully And Shows Orphan Processes Requiring Manual Killing For Proper Startup
(Doc ID 2590520.1)
Last updated on JUNE 20, 2023
Applies to:
Siebel CRM - Version 16.16 [IP2016] and laterInformation in this document applies to any platform.
Symptoms
When attempting to stop the Siebel servers in the enterprise, the Siebel server might not stop gracefully.
When it happens and a trace is run for the stop_server, below call stack definition can be seen that shows a possible hang behavior.
580 rt_sigprocmask(SIG_SETMASK [] NULL 8) = 0
581 wait4(-1 [{WIFEXITED(s) && WEXITSTATUS(s) == 108}] WSTOPPED|WCONTINUED NULL) = 29326
582 --- SIGCHLD {si_signo=SIGCHLD si_code=CLD_EXITED si_pid=29326 si_status=108 si_utime=1 si_stime=0} ---
583 rt_sigreturn() = 29326
584 wait4(-1 0x7ffe4840f0dc WNOHANG|WSTOPPED|WCONTINUED NULL) = -1 ECHILD (No child processes)
585 wait4(-1 0x7ffe4840f0dc WNOHANG|WSTOPPED|WCONTINUED NULL) = -1 ECHILD (No child processes)
586 rt_sigaction(SIGCHLD {0x42ae60 SA_RESTORER|SA_INTERRUPT 0x313ee32510} {0x42ae60 [SA_RESTORER|SA_INTERRUPT 0x313ee32510} 8) =
The issue can be replicated with below steps:
1. Setup Siebel IP2016 or later environment
2. Make sure that the application servers startup and process requests.
3. Stop the server using stop_server ALL command and check to see if the servers are stopping gracefully
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |