WebSphere Application Server & Liberty

WebSphere Application Server & Liberty

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  Deployment Manager cannot connect to remote server - WAS ND 6.0.2.27

    Posted Wed August 11, 2010 10:36 AM
    Deployment Manager cannot connect to remote server - WAS ND 6.0.2.27

    --------------------------------

    I am trying to add a new node which is a remote WebSphere Application Server instance via the WebSphere Application Admin Console (System administration > Nodes). However, I get the error message:

    /"The add node operation failed because the deployment manager could not connect to the remote server. Check the hostname and port (post_id, thread_id, post_subject, post_timestamp, post_content) VALUES and make sure the server is running/".

    I verified that the remote server is running but the default port 8880 for SOAP and RMI is not. I verified this by running netstat -an | grep 8880.

    I have no idea how to activate this port on the remote server via the WebSphere Application Admin Console or how to verify what JXM connector type it is using. I am also not sure if I have to Enable JMX by adding additional parameters to the remote servers Generic JVM settings. I found the following for WAS 6.1 but I am not sure if I have to do this 6.0.2.27.

    ecommunity.groupintelligence.com/websphe...

    I believe this is the first step I have to take to setup clustering and any help would be greatly appreciated.

    Thanks

    --------------------------------

    Posted By: aplata at Jan 31 2009 11:07PM


  • 2.  Deployment Manager cannot connect to remote server - WAS ND 6.0.2.27

    Posted Wed August 11, 2010 10:44 AM
    Try from this
    Go to appln server profile
    D://WebSphere//AppServer//bin>addNode dmgrhost 8879

    port 8879 default port for SOAP connector.

    --------------------------------

    Posted By: anilnawade at Feb 4 2009 1:46PM


  • 3.  Deployment Manager cannot connect to remote server - WAS ND 6.0.2.27

    Posted Wed August 11, 2010 10:48 AM
    [quote=anilnawade;7355]Try from this
    Go to appln server profile
    D://WebSphere//AppServer//bin>addNode dmgrhost 8879

    port 8879 default port for SOAP connector.[/quote]


    Hi Guys,

    I've been looking repeatedly at this for the last coupe of days waiting to se the www.landlordinsurance.org.uk and wondering if what Landlords Insurance suggested did work but nothing has been said here.

    So just wondering if aplata could confirm that the changes had worked for him??

    Thanks

    --------------------------------

    Posted By: nathan3011 at Mar 10 2009 2:43PM


  • 4.  Deployment Manager cannot connect to remote server - WAS ND 6.0.2.27

    Posted Wed August 11, 2010 10:48 AM
    addNode failed for remote server

    --------------------------------

    Hi,

    8880 is the default SOAP port in WAS6.0/6.1.

    I tried adding node from adminConsole (deployment manager). Sometimes it works and sometimes not. So, try at back end giving the command -
    addNode.sh -conntype SOAP

    -conntype SOAP is not really required, as SOAP would the default protocol.

    Try it and let us know.

    --------------------------------

    Posted By: texaco at Mar 10 2009 8:54PM