Deployment Manager could manage node

nor...@mesiniaga.com.my

unread,

Jan 25, 2008, 8:27:37 AM1/25/08

to

Hi everyone,

I am having a problem which the deployment manager could not manage the nodeagent after I federate the node to the deployment manager. The federation is successful and the nodeagent is started but in the deployment manager the status of the nodeagent is stopped. The deployment manager is enable with security. I use the addNode command and provide the username and password when I federate. The WASND system are running of an AIX 5.3 platform. Is there any other steps that I didn't do? please help. Thanks.

Sincerely,
Sani

jtpape

unread,

Jan 25, 2008, 3:24:42 PM1/25/08

to

There should be errors in the logs on one or both of the processes as the Dmgr and nodeagent are communicating via SOAP/HTTP. Check for that output and post here if possible.

John Pape
WebSphere Advisory Software Engineer

nor...@mesiniaga.com.my

unread,

Jan 26, 2008, 12:37:02 AM1/26/08

to

Hi John,

Thanks for replying. In the NodeAgetn the following message is thrown. I have tired to synch both dmgr and nodeagent to ensure that the configuration of both DMGR and NodeAgent are in synch but the problem still persist. Is there any other setting the I need to do?

Nodeagent
[1/26/08 12:41:25:937 WST] 00000012 RoleViewLeade I DCSV8030I: DCS Stack DefaultCoreGroup at Member hawk101Cell01\hawk102Node01\nodeagent: Failed a join attempt with member [hawk101Cell01\hawk101CellManager01\dmgr]. The reason is Not all candidates are connected ConnectedSetMissing= [ ] ConnectedSetAdditional [ hawk101Cell01\hawk201Node01\catosweb02 hawk101Cell01\hawk201Node01\nodeagent ].

Thanks so much for your assistance,

Sanni

Brian S Paskin

unread,

Jan 30, 2008, 9:48:24 AM1/30/08

to

Hi, Which version of WebSphere and WebSphere ND are you using? Also, are both Dmgr and Nodeagent on the same LPAR? Regards, Brian

nor...@mesiniaga.com.my

unread,

Jan 30, 2008, 10:48:27 AM1/30/08

to

Hi Brian, 
 
Both WebSphere are version 6.0.2.23. The Dmgr and the NodeAgent are both on two different AIX machines.

Brian S Paskin

unread,

Jan 31, 2008, 6:26:23 AM1/31/08

to

Hi, The error was supposed to be fixed in FP17 (<a class="jive-link-external" href="http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg1PK27434">http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg1PK27434</a>). Make sure that a firewall is not blocking any of the ports that WebSphere uses and make sure the Dmgr unicast port is not something that is used on your network. Also make sure that there is not a port conflict. Regards, Brian

nor...@mesiniaga.com.my

unread,

Jan 31, 2008, 6:41:34 AM1/31/08

to

Hi Brian,

Thanks for the information and I manager to solve the above error. However, I am now facing with another error. The following are the error. Just to let you know the WAS version are all upgraded to WAS 6.0.2.23 and firewall ports are all open. I hope you guide me on this matter. Once again Brian and everyone else thanks so much for you help 
 
Sincerely, 
Sanni 

 
<strike>1/26/08 11:50:56:941 WST</strike> 0000000a SOAPConnector > reconnect Entry 
<strike>1/26/08 11:50:56:953 WST</strike> 0000000a SOAPConnector 3 reconnect setting context 1.0.0 
<strike>1/26/08 11:50:56:963 WST</strike> 0000000a SOAPConnector 3 SOAPConnectorClient.getUrl, InetAddress No. 0, url=http://192.168.1.40:8879/ 
<strike>1/26/08 11:50:56:963 WST</strike> 0000000a SOAPConnector 3 soap url: <a class="jive-link-external" href="http://192.168.1.40:8879/">http://192.168.1.40:8879/</a> 
<strike>1/26/08 11:50:57:119 WST</strike> 0000000a SOAPConnector < reconnect Exit 
<strike>SOAPException: faultCode=SOAP-ENV:Client; msg=Error parsing HTTP status line " ": java.util.NoSuchElementException; targetException=java.lang.IllegalArgumentException: Error parsing HTTP status line " ": java.util.NoSuchElementException</strike> 
at org.apache.soap.transport.http.SOAPHTTPConnection.send(Unknown Source) 
at org.apache.soap.rpc.Call.invoke(Unknown Source) 
at com.ibm.ws.management.connector.soap.SOAPConnectorClient$2.run(SOAPConnectorClient.java:264) 
at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118) 
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:257) 
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.<init>(SOAPConnectorClient.java:188) 
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:305) 
at com.ibm.ws.management.tools.AbstractNodeConfigUtility.getAdminClient(AbstractNodeConfigUtility.java:191) 
at com.ibm.ws.management.tools.NodeSyncUtility.runTool(NodeSyncUtility.java:114) 
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:229) 
at com.ibm.ws.management.tools.NodeSyncUtility.main(NodeSyncUtility.java:58) 
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.run(WSLauncher.java:219) 
at java.lang.Thread.run(Thread.java:568)