15.2.15 Changing the timeout value for pipe communication of the agent
Pipe communication between job execution control agent processes sometimes times out. For example, any of the following conditions could cause a timeout:
-
Many jobs are being executed in a very short period.
-
The CPU is not available for 300 or more seconds because it is busy.
-
The job execution control agent process is swapped out and is not executed for at least 300 seconds because of a shortage of real memory.
If any of these conditions persists and pipe communication times out frequently, we recommend that you increase the timeout value for pipe communication on the host on which the agent process runs. The default timeout value is 300 seconds.
The following describes how to change the timeout value for pipe communication of the agent.
- Organization of this subsection
(1) Definition procedure
-
Stop the JP1/AJS3 service.
Execute the following commands to confirm that all processes have stopped:
# /etc/opt/jp1ajs2/jajs_stop#1 # /opt/jp1ajs2/bin/jajs_spmd_status
- #1:
-
Confirm that automatic termination has been set.
-
Execute the following command to set the environment setting parameter described in (2) below:
jajs_config -k "definition-key" "parameter-name"=value
-
Restart JP1/AJS3.
The new settings are applied.
(2) Environment setting parameter
|
Definition key |
Environment setting parameter |
Explanation |
|---|---|---|
|
[{JP1_DEFAULT|logical-host}\JP1NBQAGENT\Job]# |
"PipeComTimeout"= |
Specifies the timeout value for pipe communication of the agent. |
- #:
-
The specification of the {JP1_DEFAULT|logical-host} part depends on whether the host is a physical host or a logical host. For a physical host, specify JP1_DEFAULT. For a logical host, specify the logical host name.
For details about the definition of this environment setting parameter, see 20.5.2(59) PipeComTimeout.