IBM Support

PK22694: HMGR0024W SEEN DURING START UP USING HOST NAME VARIABLE FOR DCS_UNICAST_ADDRESS

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Problem is seen when running with APAR fixes for PK21641,
    PK20362. These fixes allow the admin to create a variable
    for the host name and use that variable to define
    endpoints (ports). When serverindex.xml defines
    DCS_UNICAST_ADDRESS to host="${dmgr_host_name}" or host="*" the
    errors are seen.
     -
    This is an example of a problematic serverindex.xml entry:
     -
    <specialEndpoints xmi:id="NamedEndPoint_10"
                      endPointName="DCS_UNICAST_ADDRESS">
      <endPoint xmi:id="EndPoint_10"
                host="${dmgr_host_name}"
                port="9367"/>
    </specialEndpoints>
      -
    These are the error messages that are seen in the systemout.log:
      -
    HMGR0024W: An error was encountered while looking up the IP
    address
    for the host name of a core group member. The host name is
    ${dmgr_host_name} and the server name is
    mshenT41Cell02\mshenT41CellManager02\dmgr. The member will be
    excluded from the core group.
     -
    HMGR0002E: HA Manager services on this process were not
     started. This server is not a member of a core group.
     -
    WSVR0009E: Error occurred during startup
    RuntimeError: Unable to start the CoordinatorComponentImpl
    

Local fix

  • Do not use host name variables.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users needing to use Websphere Application   *
    *                 Server variable syntax for the host name     *
    *                 field within the serverindex.xml Application *
    *                 Server configuration document.               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Application Server fails to start       *
    *                      after using WebSphere variables within  *
    *                      the host field of serverindex.xml.      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    You will see a java.net.UnknownHostException logged
    within SystemOut.log after changing serverindex.xml
    to use WebSphere Variable index for the host name field.
    

Problem conclusion

  • Parsing logic for serverindex.xml within HAManager and
    ChannelFramework now utilize the WebSphere variable expansion
    service to expand WebSphere variables used in the host field.
    The fix for this APAR is currently targeted for inclusion in
    fixpack 6.0.2.11. Please refer to the recommended updates page
    for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK22694

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    60S

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-04-03

  • Closed date

    2006-04-17

  • Last modified date

    2006-09-08

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

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

Modules/Macros

  • HAMGR
    

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R60A PSY

       UP

  • R60H PSY

       UP

  • R60I PSY

       UP

  • R60P PSY

       UP

  • R60S PSY

       UP

  • R60W PSY

       UP

  • R60Z PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 6.0

Reference #: PK22694

Modified date: 08 September 2006