IBM Support

PH61621: XHAD1034W: Problem creating standby deployment manager node level ManagementScope

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Using the hadmgrAdd command results in a failure to create
    the ManagementScope for the dmgr being added, logging the
    following warning:
    
    XHAD1034W: Problem creating standby deployment manager node
    level ManagementScope:
    
    createManagementScope unsuccessful for -scopeName
      (cell):cellName:(node):dmgrNodeName -scopeType node
    com.ibm.ws.xd.admin.hadmgr.config.HadmgrAddUtility.createManagem
    entScope(HadmgrAddUtility.java:358)
    com.ibm.ws.xd.admin.hadmgr.config.HadmgrAddUtility.addSecondaryD
    mgrManagementScope(HadmgrAddUtility.java:388)
    hadmgr.config.HadmgrAddUtility.runTool(HadmgrAddUtility.java:341
    )
    com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.j
    ava:281)
    com.ibm.ws.xd.admin.hadmgr.config.HadmgrAddUtility.main(HadmgrAd
    dUtility.java:1922)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  Network Deployment leveraging the High      *
    *                  Availability Deployment Manager feature.    *
    ****************************************************************
    * PROBLEM DESCRIPTION: Using the hadmgrAdd command results in  *
    *                      a                                       *
    *                      failure to create the ManagementScope   *
    *                      for the dmgr being added, logging       *
    *                      XHAD1034W.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Executing the hadmgrAdd command results in failure to create the
    ManagementScope for the deployment manager profile (dmgr) being
    federated if the cell name of the dmgr being added is not
    identical to the cell name it's being federated into and the
    following
    warning will be logged:
    XHAD1034W: Problem creating standby deployment manager node
    level ManagementScope:
    createManagementScope unsuccessful for -scopeName
    (cell):cellName:(node):dmgrNodeName -scopeType node
    com.ibm.ws.xd.admin.hadmgr.config.HadmgrAddUtility.createManagem
    entScope(HadmgrAddUtility.java:358)
    com.ibm.ws.xd.admin.hadmgr.config.HadmgrAddUtility.addSecondaryD
    mgrManagementScope(HadmgrAddUtility.java:388)
    hadmgr.config.HadmgrAddUtility.runTool(HadmgrAddUtility.java:341
    )
    com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.j
    ava:281)
    com.ibm.ws.xd.admin.hadmgr.config.HadmgrAddUtility.main(HadmgrAd
    dUtility.java:1922)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    

Problem conclusion

  • The hadmgrAdd operation was altered to correctly create the
    ManagementScope for the dmgr being federated when it's original
    cell name differs from the cell it's being federated into.
    
    The fix for this APAR is targeted for inclusion in fix packs
    8.5.5.26 and 9.0.5.21. For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH61621

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-05-31

  • Closed date

    2025-04-30

  • Last modified date

    2025-04-30

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

Document Information

Modified date:
01 May 2025