6.3.8 Applying a timeout for receiving data in inter-process communication by event/action control
If event/action control cannot perform inter-process communication normally due to heavy network load or a line error, the following problems could occur:
-
The status of a job does not change when, for example, the job is registered for execution or forcibly terminated.
-
A jobnet does not start at the scheduled time.
-
An event monitored by an event job or start condition is not detected.
-
The scheduler service does not stop when the jajs_spmd_stop or ajsstop command is executed.
-
The JP1/AJS3 service takes a long time to stop.
You can prevent these problems from occurring by enabling the option that applies a timeout for receiving data in inter-process communication by event/action control.
The following describes how to enable this option.
- Organization of this subsection
(1) Definition procedure
-
In Windows Control Panel, open the Services administrative tool, and stop the following service:
-
JP1/AJS3 service
-
-
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\JP1AOMAGENT]# |
"RecvTimeout"= |
Specifies whether to apply the timeout for receiving data in event job socket communication. |
- #:
-
The specification of this parameter is effective on the physical host and all logical hosts.
For details about the definition of this environment setting parameter, see 20.6.2(34) RecvTimeout.