IBM Support

PI89813: XSLD fails if restricting restAdminServer

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

  • For security reasons we need to bind the Liberty instances to a
    dedidated host  instead of "bind to any".
    So we changed in the Liberty instances the HTTP endoint settings
    for the
    restAdminServer from:
        <httpEndpoint host="*" httpPort="9082" httpsPort="9445"
    id="defaultHttpEndpoint"/>
    to:
        <httpEndpoint host="xsldserver02" httpPort="9082"
    httpsPort="9445"
    id="defaultHttpEndpoint"/>
    
    But now we run into two issues:
    1. The nanny cannot validate that the restAdminServer is still
    running
    and restarts it every 20 seconds.
    2. The XSLD console fails as it cannot reach the local
    restAdminServer
    (the internal request seems to be against localhost).
     If we change the host settings to "localhost" the WXS UI works
    but the
    restAdminServer cannot be used from remote.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of eXtreme Scale Liberty Deployment   *
    *                  that attempt to restrict XSLD processes to  *
    *                  a single host interface.                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: When XSLD servers are restricted to     *
    *                      one interface the monitoring process    *
    *                      fails to validate their statuses.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    XSLD by default listens on all interfaces and programmatically
    determines the appropriate interface to self monitor on. When
    the interface is manually changed via the server.xml this
    causes inconsistencies with the self monitoring process.
    

Problem conclusion

  • An environment variable, XSLD_MEMBER_HOST_ADDRESS, has been
    introduced that must be set during installation and runtime to
    restrict the XSLD host interface. An interim fix is available
    for this APAR upon request for eXtreme Scale version 8.6.1.2.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI89813

  • Reported component name

    WS EXTREME SCAL

  • Reported component ID

    5724X6702

  • Reported release

    860

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-11-03

  • Closed date

    2018-05-02

  • Last modified date

    2018-05-02

  • 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

    WS EXTREME SCAL

  • Fixed component ID

    5724X6702

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"860","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 May 2018