KNAC0603-E
Processing retried 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:
-
Check the following probable causes:
-
The destination JP1/AJS3 was not running.
-
The default gateway was changed while JP1/AJS3 was running.
-
The IP address of the manager on the logical host and the IP address of the agent belong to different networks.
-
There was a problem with the network (includes the hardware).
-
The number of socket ports that can be used in the entire system is insufficient.
-
A memory shortage occurred.
-
In a cluster configuration, the logical IP address is released faster than JP1/AJS3 stops in the failover settings.
Take corrective action for above causes as described below, and then issue the request again.
-
Start JP1/AJS3.
-
Before changing the network configuration, you must stop the JP1/AJS3 service.
-
The same network must be used.
-
Review the network settings, including the hardware settings. For example, execute the ping command to check whether communication is possible.
-
Check the socket status, and wait until there are fewer TIME_WAIT sockets. You can also suppress communication errors by increasing the recovery time for the TIME_WAIT port managed by the OS.
-
Check the memory status, and re-estimate the memory requirement.
-
The settings need to be specified so that the logical IP address is released later than JP1/AJS3 stops.
-
- 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.