IBM Support

PH26451: ODRLIB should consider all VCs when searching for the server app a request has affinity with in multi-cell topologies

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

  • In a multi-cell environment where there are identical
    web-modules in more than one cell, affinity will not be
    preserved unless the first module we check happens to be the
    one we have affinity with.  Since we load balance across the
    cells, choosing sequentially among them, this gives you only
    a 1 in N chance to keep affinity, where N is the number of
    cells with that web-module available.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server WAS ND edition- Virtual              *
    *                  Enterprise/IM Component                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Request sent to different server        *
    *                      instead of the one it has affinity      *
    *                      with                                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    There was a programming error that caused us to break affinity
    if the first server we considered wasn't the one the request had
    affinity with.
    

Problem conclusion

  • We retain affinity with the server now unless there is some
    other reason that affinity is not retained.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 9.0.5.6.  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

    PH26451

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-06-15

  • Closed date

    2020-10-05

  • Last modified date

    2020-10-05

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850"}]

Document Information

Modified date:
06 October 2020