13.7.2 Troubleshooting in JP1/IM and JP1/Base
System operation management is affected by any failure that causes JP1/IM or JP1/Base to stop. JP1/IM and JP1/Base therefore provides the following functionality to enhance failure tolerance:
-
Automatic restart if a process ends abnormally (process management)
-
Issuing of a JP1 event when an error is detected during process start or stop processing (process management)
-
Issuing of a JP1 event and execution of a notification command when a hangup is detected in a process (health check function)
Consider enabling these functions. They are disabled by default.
- About process error troubleshooting and reporting:
-
-
Process management
-
Setting to enable process restart after an error
See Extended startup process definition file (jp1co_service.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
-
Setting to enable issuing of a JP1 event when a process error occurs
See IM parameter definition file (jp1co_param_V7.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
-
Health check function
-
Setting to enable issuing of a JP1 event and execution of a notification command on detection of a process hangup
See Health check definition file (jcohc.conf) in Chapter 2. Definition Files in the manual JP1/Integrated Management 2 - Manager Command, Definition File and API Reference.
-
JP1/Base troubleshooting and error reporting
See the description of setup for troubleshooting JP1/Base errors in the JP1/Base User's Guide.
-
To enable prompt retrieval of relevant information in the event of a failure, JP1/IM provides dump output commands and data collection tools. These are normally used to collect data when a problem occurs in JP1/IM.
- Dump output commands
-
JP1/IM - View and JP1/IM - Manager each have their own dump output command.
Table 13‒10: Dump output commands Command
Description
jcothreaddmp
Dump output command for JP1/IM - View.
Outputs the following dump as diagnostic data when a hangup occurs in JP1/IM - View:
-
Java thread dump
jcogencore
Dump output command for JP1/IM - Manager.
Outputs the following dump as diagnostic data when a hangup occurs in JP1/IM - Manager processes:
-
Java thread dump: Outputs failure data for the evflow, evtcon, evgen, and jcfmain processes.
-
Core dump (UNIX only)#: Outputs failure data for the evtcon, evgen, jcamain, evflow, and jcfmain processes.
To check for a process hangup, use the health check function.
-
- Data collection tools
-
The data collection tools are provided as a batch files (in Windows) or scripts (in UNIX).
Table 13‒11: Data collection tools provided by JP1/IM OS
Data collection tool
Description
Windows
jcoview_log.bat
Tool for collecting in a batch all data required for error investigation in JP1/IM - View
jim_log.bat
Tool for collecting in a batch all data required for error investigation in JP1/IM - Manager#
UNIX
jim_log.sh
Tool for collecting in a batch all data required for error investigation in JP1/IM - Manager#
For details about the collected data, see 11.3 Data that needs to be collected when a problem occurs in the JP1/Integrated Management 2 - Manager Administration Guide. In Windows, a memory dump or crash dump might be required if a problem occurs. We recommend that you set Windows to output these dump files in case they are needed.
However, note the following points:
-
The size of the memory dump depends on the real memory size. The larger the installed physical memory, the larger the memory dump. Allocate sufficient disk space to collect a memory dump. For details, see STOP errors in the Windows help.
-
Not only JP1 event information but also error data for other application programs is output in a crash dump. Output of a crash dump reduces the amount of available disk space by the volume of output data. Allocate sufficient disk space if you have set Windows to output a crash dump.
-