Hitachi

Job Management Partner 1 Version 10 Job Management Partner 1/Automatic Job Management System 3 Messages 2


KNAC0602-E

Processing timed out during TCP/IP communication process-name(connection destination host name: destination-host-name, IP address: IP-address, port number: port-number, system call: system-call-name, system error number: system-error-number).

An error occurred during TCP/IP communication.

(S)

Cancels the requested processing.

(O)
When the process-name is connect or accept:

The status of the destination host might be as described below.

Check the host status, remove the cause of the error, and then issue the request again.

  • If JP1/AJS3 at the connection destination is not running, start it.

  • If the default gateway was changed while JP1/AJS3 was running, stop the JP1/AJS3 service before execution starts.

  • The IP address of the manager on the logical host and the IP address of the agent must belong to the same network.

  • Review the network settings to determine whether there is a problem with the network (includes the hardware). For example, execute the ping command to check whether communication is possible.

  • In a cluster configuration, if the logical IP address is released earlier than JP1/AJS3 stops in the failover settings, change the settings so that the logical IP address is released later than JP1/AJS3 stops.

  • Be careful that the values for timeouts, number of retries, and retry interval for communication connections are not too small. Values that are too small will reduce the retry interval for communication, making it difficult to avoid communication faults that could result in frequent errors of the types described.

When the process-name is send or recv:

The destination JP1/AJS3 might have terminated abnormally. In a cluster configuration, JP1/AJS3 might have been forcibly terminated because of a failover. Check the JP1/AJS3 status on the destination host and the contents of the integrated trace log. After determining the cause of the error, remove it. If JP1/AJS3 has stopped, restart it and then issue the request again. If you cannot determine the cause, obtain the internal trace log and then contact the system administrator.