| Summary | This article outlines the recommended approach to stopping Orbix servers and services. |
|---|---|
| Article Number | 27429 |
| Environment | Orbix 6.3, all supported platforms |
| Question/Problem Description |
How to stop an Orbix process correctly. |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | |
| Resolution |
The following command will gracefully shut down an Orbix process:
itadmin process stop <Orbix Process Name>
To confirm an Orbix service has been shutdown gracefully, please check the relevant log file. For example, in the case of the Orbix Configuration Repository, the following entries will be logged on a successful shut down:
(IT_OTS_LITE:203) I - OTS (Lite) Transaction Service plug-in - shutdown complete (IT_OTS:221) I - OTS Current and Propagation plug-in - shutdown complete
Please note, in the above example, the messages will be logged if the relevent event log filters are configured to provide at least the following level:
event_log:filters = ["IT_OTS_LITE=INFO", "IT_OTS=INFO"];
In the case fo the Orbix Configuration Repository, the above confiruration should be set in the file:
<Orbix Home>\\etc\\domains\\cfr-<Domain Name>.cfg |
| Workaround | |
| Notes |
By default the "itadmin process stop" command sends SIGINT(2) to the process. This is preferable to calling the OS process-kill commands, as it will allow the process to shut down its connections correctly (For example, TCP ports, database connections). |
| Attachment |
| Created date: | 22 December 2011 |
|---|---|
| Last Modified: | 12 February 2013 |
| Last Published: | 04 December 2012 |
| First Published date: | 22 December 2011 |
#KnowledgeDocs
#Orbix
