PM06705: WLM PASSIVEAFFINITY ROUTING IN WEBSPHERE APPLICATION SERVER PROXY NOT HONORED

Fixes are available

APAR status

Closed as program error.

Error description

Given a v7 WebSphere Application Server Proxy Server with a
configuration to use PassiveAffinity. If that Proxy Server
also routes to a separate cluster or application which is
configured to use a different type of session based routing or
affinity (for example, use of the JSESSIONID cookie), it is
possible that this may conflict with the PassiveAffinity
settings in the Proxy Server, resulting in the Proxy Server
not honoring the defined PassiveAffinity settings.  This can
result in requests being sprayed between multiple cluster
members instead of sticking to the one member with the
established affinity.

Local fix

```
n/a
```

Problem summary

****************************************************************
* USERS AFFECTED:  Users of the IBM WebSphere Application      *
*                  Server Proxy v7 using Passive Affinity      *
****************************************************************
* PROBLEM DESCRIPTION: WorkLoad Management (WLM) Passive       *
*                      Affinity Routing in Proxy is not        *
*                      honored                                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In a scenario in which you have configured the WebSphere
Application Server Proxy to route to a GenericCluster with the
Passive Affinity function, and the same WebSphere Application
Server proxy also routes session based requests to a WebSphere
Application Server Cluster, it is possible for the two differnet
types of Affinity to conflict with each other, leading to the
Passive Affinity settings that were configured for the Generic
Cluster to not be honored.

Problem conclusion

The code was rewritten to ensure that all necessary
ProxyRouteActions (Passive Affinity being an example), will
be run on a Generic Cluster, irregardless of other functions
and configurations being used by the WebSphere Application
Server Proxy.

As PassiveAffinity is new function for Version 7, this APAR is
only applicable to the Version 7 release.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.13.  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
PM06705
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-03
Closed date
2010-04-13
Last modified date
2010-04-13

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

R700 PSY
UP

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

Document Information

Modified date:
25 October 2021

Tips

PM06705: WLM PASSIVEAFFINITY ROUTING IN WEBSPHERE APPLICATION SERVER PROXY NOT HONORED

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?