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
Back to discussions
Expand all | Collapse all

A federated node profile creation fails with the message "dmgrHost: Unable to connect to the deployment manager on the specified hostname and port".

  • 1.  A federated node profile creation fails with the message "dmgrHost: Unable to connect to the deployment manager on the specified hostname and port".

    Posted Wed March 30, 2022 02:15 AM

    * Symptom *

    A federated node profile creation fails with the message below.

    [root]# /opt/IBM/WebSphere/AppServer90ND/bin/manageprofiles.sh -create -profileName Custom01 -templatePath /opt/IBM/WebSphere/AppServer90ND/profileTemplates/managed -dmgrHost localhost -dmgrPort 8879 -dmgrAdminUserName admin -dmgrAdminPassword admin The following validation errors were present with the command line arguments: dmgrHost: Unable to connect to the deployment manager on the specified hostname and port.

    In the ProfileName_create.log, it just tells us “com.ibm.ws.profile.validators.DmgrConnectionValidator” fails without any obvious reason.

    Of course, dmgrHost is reachable and dmgrPort is listening.



    #Support
    #SupportMigration
    #WebSphereApplicationServer(WAS)


  • 2.  RE: A federated node profile creation fails with the message "dmgrHost: Unable to connect to the deployment manager on the specified hostname and port".
    Best Answer

    Posted Wed March 30, 2022 02:19 AM

    This is due to PH36842 which was introduced at 8.5.5.21 and 9.0.5.11. You can fix this by application of the interim fix for PH44602. You can also create the profile with the lower fixpack version.

    https://www.ibm.com/support/pages/ph44602nullpointerexception-websphere-socket-factory-85521-and-90511

    If we increase the profile log level, you will see the “NullPointerException” with the stack below in <WAS_ROOT>/logs/manageprofiles/ProfileName_create.log

    <WAS_ROOT>/properties/wasprofile.properties(WS_WSPROFILE_LOG_LEVEL=7)

    Caused by: [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: java.lang.NullPointerException; targetException=java.lang.IllegalArgumentException: Error opening socket: java.lang.NullPointerException] at org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnection.java:475) at org.apache.soap.rpc.Call.WASinvoke(Call.java:510) at com.ibm.ws.management.connector.soap.SOAPConnectorClient$4.run(SOAPConnectorClient.java:397) at com.ibm.ws.security.util.AccessController.doPrivileged(AccessController.java:118) at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:382) ... 54 more



    #Support
    #SupportMigration
    #WebSphereApplicationServer(WAS)


Related Content