3.3 Notes on starting and stopping
-
If you restart Event Service of JP1/Base, you must also restart JP1/IM - Manager. In addition, you must restart the JP1/IM - View that was connected. If you do not restart it, you will have problems displaying events, for example.
-
If a process does not stop even after you have stopped all services of JP1/IM - Manager for a logical host, you can execute the jco_killall.cluster command to forcibly stop the process. Use this command for stopping a process only when a process does not stop after you have used a normal method and stopped the JP1/IM - Manager services.
-
If you collect a large number#1 of events during startup of JP1/IM - Manager, the startup time#2 will lengthen in proportion to the number of events that are collected. Consequently, the JP1/IM - Manager service (in Windows) or the jco_start command (in UNIX) may time out#3 and return an error value. In such a case, JP1/IM - Manager may appear not to be starting, but startup will be completed after a while.
- #1
-
The number will vary depending on the event collection filtering condition and the number of events that have accumulated in the event database.
- #2
-
The startup time will vary depending on the machine's performance.
- #3
-
The timeout period for the JP1/IM - Manager service (in Windows) or the jco_start command (in UNIX) is 2 minutes.
-
If the IM database fails to start, it may be unstable because it is in restart suspension (after the IM database fails to start, 8 is returned as the return value when the jimdbstatus command is executed).
Factors that cause the IM database to be in restart suspension and to become unstable are as follows:
-
Insufficient disk capacity (not insufficient IM database capacity)
-
Insufficient memory
If the IM database is in restart suspension and is unstable, you cannot normally stop the IM database by stopping services or executing a command. To avoid this state, you must execute the jimdbstop command with the -f option specified to forcibly stop the IM database.
-
-
If you are using the IM database, start JP1/Base, the IM database service, and JP1/IM - Manager in that order.
-
If you are using the IM database, stop JP1/IM - Manager, the IM database service, and JP1/Base in that order.
If JP1/IM - MO is being used, stop the JP1/IM - Message Optimizer service of JP1/IM - MO on the connection source before stopping JP1/IM - Manager.