IBM Support

PI32944: Dynamic Routing to some application instances might fail when th e application is installed in multiple clusters.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using Dynamic Routing in a collective with the same
    application installed on multiple clusters, requests to the
    application are all routed to members of the same cluster.
    The application instances on other clusters do not receive
    any requests.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile- Virtual             *
    *                  Enterprise/IM Component                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Routing to some application instances   *
    *                      might fail when the application is      *
    *                      installed in multiple clusters.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In a collective with the same application installed on multiple
    clusters, requests to the application are all routed to members
    of the same cluster. The application instances on other clusters
    do not receive any requests.
    

Problem conclusion

  • For all applications in a Liberty profile collective that can be
    routed to, a relationships between the application and its
    clusters must be created. Requests are only routed to cluster
    members where the cluster to application relationship exists.
    In some cases, we were only creating the relationship for the
    first cluster found with the application. This fix makes sure
    that the application to cluster relationship is created for each
    cluster. After this fix is applied, requests will be routed to
    applications on all clusters where the application is
    available.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.5.  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

    PI32944

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-01-19

  • Closed date

    2015-02-16

  • Last modified date

    2015-02-16

  • 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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
27 April 2022