For information about port numbers, see port number settings in WebSphere Application Server versions.
Unix/Linux users: Some Unix or Linux systems create an association between the host name of the machine and the loopback address -- 127.0.0.1 (Red Hat installations do this by default). In addition, the /etc/nsswitch.conf file is set up to use the /etc/hosts path before trying to look up the server using a name server. This setup can cause failures when trying to add or administrate nodes when the deployment manager or application server is running on the Red Hat system or an Unix/Linux system with the same setup.
hosts: dns files
com.ibm.SOAP.requestTimeout=180
If you need to change the default you can edit this line to set the timeout to a value more appropriate for your situation (Note: setting the above value to 0 will disable the timeout check altogether). If the timeout value is set too high you will have to wait a long time to determine if the addNode command will successfully complete its request to the deployment manager. If the value is set too short the deployment manager will not have sufficient time to complete the request before the addNode command concludes that the deployment manager is not responding and will respond with an error. Other factors that may affect server timeouts include the processing load or excessive paging on the deployment manager and network latency. Some of these conditions may be transient.Related reference
addNode command
removeNode command
Port number settings in WebSphere Application Server versions