IBM Support

PI20340: ODR AFFINITY LOGIC FAILS AND IS UNABLE TO ROUTE THE REQUEST TO THE CORRECT APPLICATION SERVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a request arrives, it's initially classified based on
    its URI pattern alone, the affinity logic has not yet run.
    Later, the ODR runs the affinity logic, and it identifies the
    proper destination based on the clone ID present in the session
    cookie.  However, due to a bug in the code, the ODR does not
    switch to the affinity destination.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of WebSphere Virtual Enterprise   *
    *                  who have multiple editions of an            *
    *                  application in which the application root   *
    *                  is not the same as the module root.         *
    *                  Application root refers to the name of the  *
    *                  installed application and module roots      *
    *                  refer to the context roots of different     *
    *                  web modules in the application here.        *
    ****************************************************************
    * PROBLEM DESCRIPTION: When an affined request is sent to      *
    *                      the On Demand Router(ODR), the ODR may  *
    *                      not send the request to the affined     *
    *                      destination.                            *
    *                      Let's suppose a request is sent to      *
    *                      edition A of an application and         *
    *                      affinity is established. Now when       *
    *                      edition B is rolled out, and the        *
    *                      second request is sent with affinity,   *
    *                      the request does not reach the          *
    *                      destination to which the affinity was   *
    *                      established.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    There is a bug in the selection of the right affinity
    destination.
    

Problem conclusion

  • The code has been fixed to choose the right destination now.
    
    This issue will be resolved in the next available fix pack for
    WebSphere Virtual Enterprise V7.0 and V.8.5.5.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI20340

  • Reported component name

    WEBSP VIRTUAL E

  • Reported component ID

    5655V6403

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2014-06-18

  • Closed date

    2014-08-07

  • Last modified date

    2014-08-07

  • 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

    WEBSP VIRTUAL E

  • Fixed component ID

    5655V6403

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"7.0"}]

Document Information

Modified date:
07 September 2021