| Summary | Does forceful shutdown of Orbix leads to corrupted database? Using Kill -9 command to shutdown Orbix services |
|---|---|
| Article Number | 33948 |
| Environment | Orbix 6.3.x All Supported Platforms |
| Question/Problem Description | In situations where normal shutdown is not possible, does forceful shutdown of Orbix services leads to corrupted database? Is it OK to use the command below to forcefully shutdown Orbix services? > itadmin process kill |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | |
| Resolution |
In situations where a normal shutdown of Orbix application is not possible, the command below can be used for forced shutdown. This command will kill the process as well as clean the associated database records of the processes and hence eliminate the chance of database corruption. This command is available for all versions of Orbix 6.3.
> itadmin process kill
The command below provides help for kill command.
> itadmin process kill -help
This command terminates the indicated process that was started by its associated node daemon.
-s[ignal] [POSIX signal number to stop process]
Default, if -signal not specified: 9
WARNING: The -force option should be used with caution. If used, it forces the immediate cleanup of persistent info for the process being killed. It should only be used after first attempting to use the kill command without the -force option.
WARNING: The signal number is ignored for a Win32 process, it is terminated abruptly via the 'TerminateProcess' API. |
| Workaround | |
| Notes | |
| Attachment |
| Created date: | 09 August 2012 |
|---|---|
| Last Modified: | 12 February 2013 |
| Last Published: | 14 August 2012 |
| First Published date: | 09 August 2012 |
#KnowledgeDocs
#Orbix




