PM16855: IF A SERVER IS REMOVED FROM THE PRIMARYSERVER OF THE PLUGIN CONFIGURATION, AFFINITY REQUESTS CONTINUE TO GO TO THE SERVER

Fixes are available

APAR status

Closed as program error.

Error description

Plug-in might forward the affinity request even though the
server is commented out in Memory to memory session replication.

We have expected the plug-in not to send the request that was
commented out in PrimaryServers of plugin-cfg.xml even though it
was in the server affinity. This is working fine in non-memory
to memory session replication environment.

With the memory to memory session replication, the plug-in might
use the partition table to choose the server even though the
server is commented out.

Local fix

Comment out the Server clause in ServerCluster additionally with
the Server in PrimaryServers of plugin-cfg.xml.

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server V6.1 and   *
*                  V7.0 web server plugin users                *
****************************************************************
* PROBLEM DESCRIPTION: If a server is removed from the         *
*                      primaryserver of the plugin             *
*                      configuration, affinity requests        *
*                      continue to go to the server            *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If a server is removed from the primaryserver of the plugin
configuration, affinity requests continue to go to the server.
You may want to remove a server from the primaryserver list
so that you can perform service on the server and prevent
requests from being sent to that server during the service
period.

Problem conclusion

A change was made so that affinity requests would ensure that
the server is in the primaryserver list (if defined) before
using that server.

The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.35 and 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
PM16855
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-06-21
Closed date
2010-06-28
Last modified date
2010-09-24

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

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
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:
24 October 2021

Tips

PM16855: IF A SERVER IS REMOVED FROM THE PRIMARYSERVER OF THE PLUGIN CONFIGURATION, AFFINITY REQUESTS CONTINUE TO GO TO THE SERVER

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

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?