Job Management Partner 1/Integrated Management - Manager Administration Guide

9.4.1 In Windows

Organization of this subsection

(1) Checking the process status

(2) Outputting a thread dump for JP1/IM

(3) Collecting information related to the Web version of JP1/IM - View

(4) Executing the data collection tool

(5) Checking the operation content

(6) Collecting the error information on the screen

(7) Collecting a user dump (Windows Vista and Windows Server 2008 only)

(8) Collecting a problem report (Windows Vista and Windows Server 2008 only)

(1) Checking the process status

Using Windows Task Manager, check the operating status of processes. This subsection shows the processes that are displayed when the programs are running normally.

(a) JP1/IM - Manager

The table below shows the processes of JP1/IM - Manager. The value inside parentheses ( ) indicates the number of processes that execute simultaneously.

Table 9-15 JP1/IM - Manager processes (Windows)

Parent process name Function Child process name Function

jco_spmd.exe
(1) JP1/IM - Manager process management jcamain.exe
(1) Automatic Action Service
(Process management display name: jcamain)

evtcon.exe
(1) Event Console Service
(Process management display name: evtcon)

evflow.exe
(1) Event Base Service
(Process management display name: evflow)

jcsmain.exe
(1) Central Scope Service^#2
(Process management display name: jcsmain)

jcfmain.exe
(1) IM Configuration Management Service^#2
(Process management display name: jcfmain)

evgen.exe
(2)^#1#3 Event Generation Service^#2
(Process management display name: evgen)

jco_service.exe
(1) JP1/IM - Manager Windows service control -- --

Legend:

--: None

#1: The maximum number is 2, but the normal number is 1. The details are as follows.

This is a process that is temporarily generated when Event Service is connected. It is generated in the following cases:
When Event Generation Service starts
When the event acquisition filter is updated

#2: In the default, this service does not run.

#3: This is the service that is used when the integrated monitoring database is not used.

When JP1/IM - Manager is running in a cluster system, the above processes are executed on each physical host and on each logical host. The number of processes that execute simultaneously can be obtained by multiplying the number of physical hosts and logical hosts that are running by the number of above processes.

In the table, a process whose parent process is jco_spmd.exe is controlled by process management, and you can use the jco_spmd_status command to check the process status.

A display example during normal operations follows.
c:\>jco_spmd_status
KAVB3690-I Processing to report the status of JP1_CONS has started.
Shows processes that are running.
Process name Process ID
    evflow      3672
   jcamain      4088
    evtcon      4236
   jcsmain      4668
   jcfmain      4950
     evgen      5624
KAVB3691-I All the processes have started.
 
jcsmain is displayed only when Central Scope is enabled.

jcfmain is displayed only when IM Configuration Management is enabled.

evgen is displayed only when Event Generation Service is enabled.

(b) JP1/IM - View

The table below shows the processes of JP1/IM - View. The value inside parentheses ( ) indicates the number of processes that execute simultaneously.

Table 9-16 JP1/IM - View processes

Parent process name Function Child process name Function

jcoview.exe
(3+3^#) JP1/IM - View process management jcoview_evt.exe
(3) Sends thread dump output events.

java.exe
(3+3^#) Controls the JP1/IM - View window.

#: Added when JP1/IM - View (the part linked to JP1/IM - Rule Operation) is running.

(c) JP1/IM - IM Configuration Management - View

The table below shows the processes of JP1/IM - IM Configuration Management - View. The value inside parentheses ( ) indicates the number of processes that execute simultaneously.

Table 9-17 JP1/IM - IM Configuration Management - View processes

Parent process name Function Child process name Function

jcfview.exe
(3) Controls the JP1/IM - IM Configuration Management - View window. jcfview_evt.exe
(3) Sends thread dump output events.

java.exe
(3) Controls the JP1/IM - IM Configuration Management - View window.

You can start a maximum of three JP1/IM - IM Configuration Management - View instances when you log in from a single machine. Each time JP1/IM - IM Configuration Management - View is started, one process starts.

Parent process name	Function	Child process name	Function
jco_spmd.exe (1)	JP1/IM - Manager process management	jcamain.exe (1)	Automatic Action Service (Process management display name: jcamain)
evtcon.exe (1)	Event Console Service (Process management display name: evtcon)
evflow.exe (1)	Event Base Service (Process management display name: evflow)
jcsmain.exe (1)	Central Scope Service^#2 (Process management display name: jcsmain)
jcfmain.exe (1)	IM Configuration Management Service^#2 (Process management display name: jcfmain)
evgen.exe (2)^#1#3	Event Generation Service^#2 (Process management display name: evgen)
jco_service.exe (1)	JP1/IM - Manager Windows service control	--	--

Parent process name	Function	Child process name	Function
jcoview.exe (3+3^#)	JP1/IM - View process management	jcoview_evt.exe (3)	Sends thread dump output events.
java.exe (3+3^#)	Controls the JP1/IM - View window.

Parent process name	Function	Child process name	Function
jcfview.exe (3)	Controls the JP1/IM - IM Configuration Management - View window.	jcfview_evt.exe (3)	Sends thread dump output events.
java.exe (3)	Controls the JP1/IM - IM Configuration Management - View window.

(2) Outputting a thread dump for JP1/IM

(a) JP1/IM - View

Follow the procedure described below to output a dump file.

Start Task Manager.

On the Applications page, select JP1/IM - View, and then from the pop-up menu, choose Bring To Front.
In this way, you can determine whether JP1/IM - View is disabled. If you have identified a disabled JP1/IM - View, proceed to the next step.

From the pop-up menu, choose Go To Process.
The display switches to the Process page. Since java.exe of JP1/IM - View is displayed in the selected state, use this to identify the process ID (PID).^#
#: If no PID is displayed, from the menu, choose Display and then Select Columns, and then, from the Select Columns window, select the PID (Process Identifier) check box.

Using the process ID that has been identified as the argument, execute the jcothreaddmp command.

For details about the jcothreaddmp command, see jcothreaddmp (Windows only) (1. Commands) in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

(b) JP1/IM - Manager

When the health check function detects an abnormality in Event Console Service or Event Generation Service of JP1/IM - Manager, output a dump file for JP1/IM - Manager. Execute the jcogencore command as follows.
jcogencore
 
For details about the jcogencore command, see jcogencore (1. Commands) in the manual Job Management Partner 1/Integrated Management - Manager Command and Definition File Reference.

(3) Collecting information related to the Web version of JP1/IM - View

When a problem occurs in the Web version of JP1/IM - View, collect the following data in addition to the data described in this section.

View side

Java stack trace log

The collection procedure follows.

1. Choose the Java Console window and enter v.

The Java stack trace log is output to the Java Console window.

2. Copy the log and manually paste it to a text file, for example.

3. Save the text file.

Java trace file of Java^TM Plug-in

The Java trace file is located in the following directory:

system-drive:\Documents and Settings\login-user-name\Application Data\Sun\Java\Deployment\log\

Note

The Java trace file of Java^TM Plug-in is erased when Java^TM Plug-in restarts. Therefore, if a problem occurs, save the content of this file to another file before restarting.

Manager side

HTTP server error log

HTTP server access log

(4) Executing the data collection tool

This subsection describes execution of the data collection tool (jim_log.bat or jcoview_log.bat).

When you execute the jim_log.bat command, which is provided by JP1/IM - Manager, you can collect the data necessary for troubleshooting JP1/IM - Manager and JP1/IM - View on the same host.

If you execute the jcoview_log.bat command, which is provided by JP1/IM - View, you can collect the data necessary for troubleshooting JP1/IM - View.

Use one of above commands according to the application that is being used.

Because the total volume of data collected by a data collection tool is massive, you need to estimate it before you execute the command and make sure the machine you are using has sufficient free space.

For the volume of data that will be collected by the jim_log.bat command, see the JP1/IM - Manager release notes.

For the volume of data that will be collected by the jcoview_log.bat command, see the JP1/IM - View release notes.

A tool execution example follows.
C:\>"C:\Program Files\HITACHI\JP1IMM\tools\jim_log.bat" -f data-storage-folder
Specify the data storage folder as an absolute path. If the data storage folder path contains a space, enclose the path in double quotation marks.

When you execute the tool, the jp1_default folder is created under the folder specified as the data storage folder, and the collected data is copied into this folder. Use a data-compression tool to compress the collected data.

(5) Checking the operation content

Check the content of the operation that was taking place when the problem occurred, and record it. The following types of information must be checked:

Operation content details

Time of problem occurrence

Reproducibility

Login user name that was used to log in from JP1/IM - View

Machine configuration (version of each OS, host name, and Central Console configuration)

(6) Collecting the error information on the screen

If an error is displayed on the screen, collect that information as well. Collect a hard copy of the following:

Error dialog box
Copy the content displayed by the Details button, if available.

(7) Collecting a user dump (Windows Vista and Windows Server 2008 only)

If an application error causes a JP1/IM - View process to stop in Windows Vista or Windows Server 2008, use the following procedure to collect a user dump, with the error dialog box displayed.

Start Task Manager.
You can use either of the following procedures to start Task Manager:

Right-click a blank area on the task bar and choose Task Manager.

Press Ctrl + Shift + Esc keys to start Task Manager.

Click the Process tab.

Right-click the name of the JP1/IM - View process that was stopped by an application error, and then choose Create Dump File.

When a dialog box showing the user dump output destination path opens, collect a dump from there.

Note

If the error dialog box is closed, a normal dump cannot be collected, and consequently you will not be able to collect a user dump. If you closed the error dialog box by mistake (by clicking OK, for example) before collecting a user dump, reproduce the error and then collect a user dump.

(8) Collecting a problem report (Windows Vista and Windows Server 2008 only)

If an application error causes a JP1/IM - View process to stop in Windows Vista or Windows Server 2008, use the following procedure to collect a problem report.

In the Run text box, enter wercon and click OK.
The Problem Report and Solution dialog box opens.

On the left pane, click Show Problem History.

Double-click the applicable problem.
Details of the problem report are displayed.

Choose Copy to Clipboard.

Copy the copied content and save it in a text file.
Use the saved problem report for troubleshooting.

[Contents][Back][Next]

[Trademarks]