unable to federate the node [ help help help ]
viikas...@gmail.com
I am trying to fedearate the node but i am getting the error regarding
SOAP Connector port number. I have checked the port number also and
its not used by any other application. I have also tried to change the
port number from the following path "/opt/IBM/WebSphere/AppServer/
profiles/Dmgr01/config/cells/testCell01/nodes/testCellManager01/
serverindex.xml.
But still the server is throwing the error regarding port 8879.
Please see the error mention below:--
root@test bin]# ./addNode.sh server1
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/
addNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0001I: Begin federation of node testNode01 with Deployment Manager
at
server1:8879.
ADMU0113E: Program exiting with
error:com.ibm.websphere.management.exception.ConnectorException:
ADMC0016E: The system cannot create a SOAP connector to connect to
host server1 at port 8879., resulting
from:java.lang.reflect.InvocationTargetException
ADMU4123E: Ensure that the Deployment Manager is running on the
specified host
and port.
ADMU1211I: To obtain a full trace of the failure, use the -trace
option.
ADMU0211I: Error details may be seen in the file:
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/
addNode.log
login as: root
ro...@10.10.10.11's password:
Last login: Mon Sep 17 04:39:18 2007 from 10.10.10.1
[root@test ~]# cd /opt/IBM/WebSphere/AppServer/bin/
[root@test bin]# ./addNode.sh server1
ADMU0116I: Tool information is being logged in file
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/
addNode.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU0001I: Begin federation of node testNode01 with Deployment Manager
at
server1:8879.
ADMU0113E: Program exiting with error:
com.ibm.websphere.management.exception.ConnectorException:
ADMC0016E: The system cannot create a SOAP connector to
connect to
host server1 at port 8879., resulting from:
java.lang.reflect.InvocationTargetException
ADMU4123E: Ensure that the Deployment Manager is running on the
specified host
and port.
ADMU1211I: To obtain a full trace of the failure, use the -trace
option.
ADMU0211I: Error details may be seen in the file:
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/
addNode.log
[root@test bin]# ./versionInfo.sh
WVER0010I: Copyright (c) IBM Corporation 2002; All rights reserved.
WVER0011I: WebSphere Application Server Release 6.0
WVER0012I: VersionInfo Reporter Version 1.15, Dated 9/20/03
--------------------------------------------------------------------------------
IBM WebSphere Application Server Product Installation Status Report
--------------------------------------------------------------------------------
Report at date and time 2007-09-17T04:47:20+05:30
Installation
--------------------------------------------------------------------------------
Product Directory /opt/IBM/WebSphere/AppServer
Version Directory /opt/IBM/WebSphere/AppServer/properties/version
DTD Directory /opt/IBM/WebSphere/AppServer/properties/version/
dtd
Log Directory /opt/IBM/WebSphere/AppServer/logs/update
Backup Directory /opt/IBM/WebSphere/AppServer/properties/version/
backup
TMP Directory /tmp
Installation Platform
--------------------------------------------------------------------------------
Name IBM WebSphere Application Server
Version 6.0
Technology List
--------------------------------------------------------------------------------
ND installed
Installed Product
--------------------------------------------------------------------------------
Name IBM WebSphere Application Server - ND
Version 6.0.0.1
ID ND
Build Level o0445.08
Build Date 11/10/04
--------------------------------------------------------------------------------
End Installation Status Report
--------------------------------------------------------------------------------
[root@test bin]# vi /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/
logs/
addNode.
log
at
com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:
118)
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:
292)
... 17 more
Caused by: java.net.UnknownHostException: server1
at java.net.InetAddress.getAllByName0(InetAddress.java:1089)
at java.net.InetAddress.getAllByName0(InetAddress.java:1054)
at java.net.InetAddress.getAllByName(InetAddress.java:1048)
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.getUrl(SOAPConnectorClient.java:
1034)
... 21 more
[9/17/07 4:41:23:520 IST] 0000000a AdminTool A ADMU0113E:
Program exiting with error:
com.ibm.websphere.management.exception.ConnectorException: ADMC0016E:
The system cannot create a SOAP connector to connect to host server1
at port 8879.
at
com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:
320)
at
com.ibm.ws.management.tools.AbstractNodeConfigUtility.getAdminClient(AbstractNodeConfigUtility.java:
183)
at
com.ibm.ws.management.tools.NodeFederationUtility.doSetUp(NodeFederationUtility.java:
1049)
at
com.ibm.ws.management.tools.NodeFederationUtility.runTool(NodeFederationUtility.java:
402)
at
com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:
209)
at
com.ibm.ws.management.tools.NodeFederationUtility.main(NodeFederationUtility.java:
224)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
85)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
58)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:190)
Caused by: java.lang.reflect.InvocationTargetException
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:
80)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:
44)
at java.lang.reflect.Constructor.newInstance(Constructor.java:
315)
at
com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:
269)
... 11 more
Caused by:
com.ibm.websphere.management.exception.ConnectorNotAvailableException:
com.ibm.websphere.management.exception.ConnectorNotAvailableException:
java.net.UnknownHostException: server1
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:
328)
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.<init>(SOAPConnectorClient.java:
227)
... 16 more
Caused by:
com.ibm.websphere.management.exception.ConnectorNotAvailableException:
java.net.UnknownHostException: server1
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.getUrl(SOAPConnectorClient.java:
1036)
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.access
$200(SOAPConnectorClient.java:85)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient
$2.run(SOAPConnectorClient.java:299)
at
com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:
118)
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:
292)
... 17 more
Caused by: java.net.UnknownHostException: server1
at java.net.InetAddress.getAllByName0(InetAddress.java:1089)
at java.net.InetAddress.getAllByName0(InetAddress.java:1054)
at java.net.InetAddress.getAllByName(InetAddress.java:1048)
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.getUrl(SOAPConnectorClient.java:
1034)
... 21 more
, resulting from: java.lang.reflect.InvocationTargetException
at
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:
80)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:
44)
at java.lang.reflect.Constructor.newInstance(Constructor.java:
315)
at
com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:
269)
at
com.ibm.ws.management.tools.AbstractNodeConfigUtility.getAdminClient(AbstractNodeConfigUtility.java:
183)
at
com.ibm.ws.management.tools.NodeFederationUtility.doSetUp(NodeFederationUtility.java:
1049)
at
com.ibm.ws.management.tools.NodeFederationUtility.runTool(NodeFederationUtility.java:
402)
at
com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:
209)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:190)
Caused by:
com.ibm.websphere.management.exception.ConnectorNotAvailableException:
com.ibm.websphere.management.exception.ConnectorNotAvailableException:
java.net.UnknownHostException: server1
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:
328)
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.<init>(SOAPConnectorClient.java:
227)
... 16 more
Caused by:
com.ibm.websphere.management.exception.ConnectorNotAvailableException:
java.net.UnknownHostException: server1
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.getUrl(SOAPConnectorClient.java:
1036)
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.access
$200(SOAPConnectorClient.java:85)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient
$2.run(SOAPConnectorClient.java:299)
at
com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:
118)
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:
292)
... 17 more
Caused by: java.net.UnknownHostException: server1
at java.net.InetAddress.getAllByName0(InetAddress.java:1089)
at java.net.InetAddress.getAllByName0(InetAddress.java:1054)
at java.net.InetAddress.getAllByName(InetAddress.java:1048)
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.getUrl(SOAPConnectorClient.java:
1034)
... 21 more
[9/17/07 4:41:23:525 IST] 0000000a AdminTool 3 Returning from
auxiliary method issueMessage with return code: 113
[9/17/07 4:41:23:542 IST] 0000000a AdminTool A ADMU4123E: Ensure
that the Deployment Manager is running on the specified host and port.
[9/17/07 4:41:23:545 IST] 0000000a AdminTool A ADMU1211I: To
obtain a full trace of the failure, use the -trace option.
[9/17/07 4:41:23:548 IST] 0000000a AdminTool A ADMU0211I: Error
details may be seen in the file: /opt/IBM/WebSphere/AppServer/profiles/
AppSrv01/logs/addNode.log
[9/17/07 4:41:23:550 IST] 0000000a AdminTool 3 Returning from
auxiliary method issueMessage with return code: 211
[9/17/07 4:41:23:550 IST] 0000000a AdminTool 3 Returning from
executeUtility method with return code: -1
Gabriel
Hi,
Last time I federated a Portal node so let me see if I get this
straight.
First thing first,
Is your DMGR and WAS on the same box?
If NO, is your server1 and Dmgr running? Are you connecting to Dmgr,
from the error it seems that you are trying to connect to serevr1.
If YES, it seems that you are trying to connect to server1 SOAP port
from server1.
You might have both DMgr and WAS on the same box listening to the same
SOAP default port. You will have to chnage one of the ports. I am not
sure if you can do that in serverindex.xml. Maybe server.xml.
Hope this helps,
Gabriel
Infyniti
your DMGR host name is not server1.
addNode log
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The system cannot create a SOAP connector to connect to host server1
at port 8879.
... 17 more
Caused by: java.net.UnknownHostException: server1
at java.net.InetAddress.getAllByName0(InetAddress.java:1089)
at java.net.InetAddress.getAllByName0(InetAddress.java:1054)
at java.net.InetAddress.getAllByName(InetAddress.java:1048)
at
com.ibm.ws.management.connector.soap.SOAPConnectorClient.getUrl(SOAPConnect
orClient.java: 1034)
... 21 more
[9/17/07 4:41:23:542 IST] 0000000a AdminTool A ADMU4123E: Ensure
that the Deployment Manager is running on the specified host and
port.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Here is the command for addnode, in which the dmgr_port is optional.
If the ports are not changed during installation, it will use 8879.
addNode dmgr_host [dmgr_port]
First I would check if the DMGR is up and running and then get the
correct hostname and port from the serverindex.xml (on DMGR) file and
try adding the node again.
Thanks
Anant
Gabriel
the above post too.
Hi,
Last time I federated a Portal node so let me see if I get this
straight.
First thing first,
Is your DMGR and WAS on the same box?
If NO, is your server1 and Dmgr running? Are you trying to connect to
Dmgr?
>From the error it seems that you are trying to connect to serevr1.