IBM Support

PI47476: CWWKT0022E IN LIBERTY SERVER WHEN USING DVIPA HOSTNAME DEFINED BY VIPARANGE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a httpEndpoint is defined with a host of a DVIPA
    hostname
    defined by VIPARange, the following error is seen in the
    log:
    CWWKT0022E: The configured host DVIPA.hostname for HTTP
    endpoint defaultHttpEndpoint could not be resolved. The
    endpoint has been disabled.
    
    This happens because the server is doing an additional check
    on
    the IP address resolved from the hostname, to ensure this IP
    address is already active in TCPIP.  But when using
    VIPARange,
    this IP address is not activated until the server does a
    bind
    on the IP address to create it, and that happens later in
    the
    process.
    

Local fix

  • Use an IP address that already exists before the server is
    started.  Ths can be done by using a different IP address, or
    using a VIPADefine statement instead of VIPARange or using
    MODDVIPA to create the DVIPA before the server is started.
    
    If using z/OSMF, you can add 2 steps to the z/OSMF proc, to
    create/delete the DVIPA.  There is an example of how to do this
    in this redbook IBM z/OS Management Facility V2R1.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile for z/OS             *
    ****************************************************************
    * PROBLEM DESCRIPTION: Liberty HTTP endpoint fails             *
    *                      (CWWKT0022E) when using DVIPA hostname  *
    *                      defined via VIPARANGE                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using a DVIPA hostname defined via VIPARANGE for Liberty's
    HTTP endpoint hostname, the HTTP endpoint fails to start. The
    following message is produced:
    
    CWWKT0022E: The configured host {DVIPA hostname} for HTTP
    endpoint defaultHttpEndpoint could not be resolved. The endpoint
    has been disabled.
    
    The problem occurs because Liberty attempts to verify the
    hostname (via DNS) before binding to it.  Since the hostname is
    defined dynamically via VIPARANGE at bind time, it is not yet
    defined to DNS when Liberty verifies it.  Thus the verification
    fails and the HTTP endpoint is not started.
    

Problem conclusion

  • The verification code was removed.  This allows a VIPARANGE
    hostname to be defined dynamically when the HTTP endpoint binds
    to it. If the hostname is indeed bad, then the bind will fail as
    expected.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.8.  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

    PI47476

  • Reported component name

    LIBERTY PROF -

  • Reported component ID

    5655W6514

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-08-24

  • Closed date

    2015-10-28

  • Last modified date

    2015-10-28

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

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

    PI48029

Fix information

  • Fixed component name

    LIBERTY PROF -

  • Fixed component ID

    5655W6514

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
28 October 2015