IBM Support

PI52161: Liberty collective server status is not in sync with DataPower status query

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Issue with routing to our Collective through the on-demand
    router on Datapower.
    
    After some time, is seems that the status of the servers in
    Datapower does not get updated anymore.
    
    Some applications are marked up, but are not accessible.
    Others are even marked down, but can be accessed.
    Also it seems that the housekeeping is only taking place
    after
    the on Demand Router object has been disabled and enabled
    again.
    
    
    We have a setup with 3 Controllers that are configured in an
    ODR
    connector group.
    To make it work we had to set the Custom Property "api" to
    "/ibm/api/dynamicRouting".
    Initially, it seemed as everything seems to work smoothly,
    but
    after some time there seems to be a discrepancy between the
    Datapower status
    and the real status in Liberty.
    The status only gets
    updated properly after disabling and enabling the On Demand
    Router Object.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile- Virtual             *
    *                  Enterprise/IM Component                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using "show odr-loadbalancer-      *
    *                      status", the status of the application  *
    *                      servers in a Liberty collective is not  *
    *                      in synch with the status of the         *
    *                      application servers shown in the        *
    *                      DataPower appliance                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Information about the transport availability of application
    servers was not being delivered to the DataPower Appliance. Only
    the STARTED/STOPPED state of the servers was provided.
    

Problem conclusion

  • Code was added to deliver the transport availability along with
    the server STARTED/STOPPED state.
    
    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

    PI52161

  • Reported component name

    WAS LIBERTY COR

  • Reported component ID

    5725L2900

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-11-09

  • Closed date

    2016-02-05

  • Last modified date

    2016-02-10

  • 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

    WAS LIBERTY COR

  • Fixed component ID

    5725L2900

Applicable component levels

  • R855 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
17 October 2021