WebSphere Application Server 5.0, addNode command fails with Error
 Technote (troubleshooting)
 
Problem(Abstract)
Attempt to federate a node to the deployment manager cell fails. The addNode utility adds a stand alone node to an existing cell. The syntax used for adding the node is: addNode <deployment manager host> <deployment manager SOAP port>
Exception:
[5/21/03 12:43:58:380 EDT] 6dd33e47 AdminTool A ADMU0111E: Program exiting with error: com.ibm.websphere.management.exception.ConnectorException: ADMC0016E: Could not create SOAP Connector to connect to host simbae1.raleigh.ibm.com at port 8880
at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:274)
at com.ibm.ws.management.tools.AbstractNodeConfigUtility.getAdminClient(AbstractNodeConfigUtility.java:155)
at com.ibm.ws.management.tools.NodeFederationUtility.runTool(NodeFederationUtility.java:213)
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:159)
at com.ibm.ws.management.tools.NodeFederationUtility.main(NodeFederationUtility.java:127)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
---- Begin backtrace for nested exception
java.lang.reflect.InvocationTargetException: com.ibm.websphere.management.exception.ConnectorNotAvailableException
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:168)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.<init>(SOAPConnectorClient.java:120)
at java.lang.reflect.Constructor.newInstance(Native Method)
at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:230)
at com.ibm.ws.management.tools.AbstractNodeConfigUtility.getAdminClient(AbstractNodeConfigUtility.java:155)
at com.ibm.ws.management.tools.NodeFederationUtility.runTool(NodeFederationUtility.java:213)
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:159)
at com.ibm.ws.management.tools.NodeFederationUtility.main(NodeFederationUtility.java:127)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
---- Begin backtrace for nested exception
[SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: java.net.NoRouteToHostException: Host unreachable: connect; targetException=java.lang.IllegalArgumentException: Error opening socket: java.net.NoRouteToHostException: Host unreachable: connect]
at org.apache.soap.transport.http.SOAPHTTPConnection.send(Unknown Source)
at org.apache.soap.rpc.Call.invoke(Unknown Source)

 
Cause
The mapping of the host name to an IP address in the Operating System's etc/hosts file is pointing to a wrong IP address.
 
Resolving the problem
Ping the deployment manager node and the base server node individually to ensure both are running.
  1. Use the 'ipconfig' command to see both node's IP addresses.
  2. Ensure that the mapping of the IP address to the host name is correct on both the deployment manager node and the base node by checking the <OS>/hosts file. The above problem was resolved by editing the ~/etc/hosts file's host name to match the IP address.
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Administrative Console (all non-scripting)
Operating system(s): Windows
Software version: 5.0
Software edition:
Reference #: 1110725
IBM Group: Software Group
Modified date: Aug 26, 2003