IBM Support

PI66664: Application edition validation with inconsistent policies breaks affinity on the default edition

Fixes are available

9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Application edition validation with inconsistent
    affinity policies breaks affinity on the default edition.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
    *                  WAS ND edition - Virtual Enterprise/IM      *
    *                  Component - using application edition       *
    *                  validation.                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION: Application edition validation with inc *
    *                      onsistent affinity policies may         *
    *                      break affinity on requests using active *
    *                      editions                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using application editions and performing validation of a
    new edition, the configuration of the multiple editions must be
    consistent.  However, mistakes are sometimes made that can cause
    problems for the active edition. For example, if the affinity
    policy of the validation edition is not consistent with the
    affinity policy of an active edition it may cause affinity to be
    broken for requests to the active edition. This is because the
    validation affinity policy may be selected when processing a
    request rather than the affinity policy of the active edition.
    When application configuration is consistent, as it should be,
    this will not create a problem. However, if application
    configuration is not consistent it may cause problems such as
    broken affinity for requests destined for an active edition.
    

Problem conclusion

  • The ODR request processing code has been changed to evaluate the
    edition rules earlier in the request flow such that the affinity
    policy that is considered is the affinity policy for the edition
    that is selected based upon the application edition rules. This
    will provide some protection for requests destined for active
    editions of the application from being impacted by inconsistent
    configuration when a new application edition is being validated.
    The customer must still correct any inconsistencies in
    configuration between the validation application edition and the
    active application editions prior to rollout of the validation
    edition unless the changes are intended.  Failure to validate
    consistent configuration may cause unexpected results when the
    new edition is activated.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.11.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Ensure that the configuration is consistent for multiple
    editions of the application prior to performing validation on a
    new edition.
    

Comments

APAR Information

  • APAR number

    PI66664

  • 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

    2016-07-28

  • Closed date

    2016-09-06

  • Last modified date

    2016-09-06

  • 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

  • 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":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 November 2021