PM48578: WLM EXTERNAL CLIENT DATA PROPAGATION INCOMPLETE

Fixes are available

APAR status

Closed as program error.

Error description

In the scenario in which a customer has an external client to
the target cluster (defined as either a java thin client, or a
WebSphere Application Server process acting as a client which
is either in a separate, non-bridged cell, or in the same cell
but in a separate, non-bridged coregroup), the cluster data
passed back to the client after certain events may be
incomplete, or new data may not be passed back at all. An
example of this is if a customer uses the cluster MBean to
explicitly mark a  particular cluster member unavailable.  This
data would not end up being  propagated back to an already
connected external client, so the client would continue to
route to the member that was marked unavailable.  Note that the
problem only affects the middle of the lifecycle of a client.
Any new clients which tried to connect and route to that cluster
after the setUnavailable call was made would get the correct
data.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  Users of WLM-enabled java thin clients and  *
*                  WebSphere Application Server Network        *
*                  Deployment edition                          *
****************************************************************
* PROBLEM DESCRIPTION: Incomplete data propagation back to     *
*                      thin                                    *
*                      clients.                                *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
In the scenario in which a customer has an external client to
the target cluster (defined as either a java thin client, or a
WebSphere Application Server process acting as a client which
is either in a separate, non-bridged cell, or in the same cell
but in a separate,non-bridged coregroup), the cluster data
passed back to the client after certain events may be
incomplete, or new data may not be passed back at all. An
example of this is if a customer uses the cluster MBean to
explicitly mark a  particular cluster member unavailable.  This
data would not end up being  propagated back to an already
connected external client, so the client would continue to
route to the member that was marked unavailable.  Note that the
problem only affects the middle of the lifecycle of a client.
Any new clients which tried to connect and route to that
cluster
after the setUnavailable call was made would get the correct
data.

Problem conclusion

This APAR is a continuation of PM42959.  The code was modified
to ensure in the setUnavailable and other data setting scenarios
that the data will be updated and propagated to the java thin
clients properly to allow for more correct routing behaviors.

In order to enable this function, you must set a cell-level
custom property by going through the administrative console
from:

System Administration -> Cell -> Custom Properties

and define a new custom property with the name:

IBM_CLUSTER_ENABLE_THIN_CLIENT_UPDATES

and a value of true.  Save, and synchronize to the nodes and
the next time each of the cluster members are restarted, the
custom property will be picked up and the change in behavior
come into effect.

The fix for this APAR is currently targeted for inclusion in
fix pack 7.0.0.23, 8.0.0.3.  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
PM48578
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
2011-09-23
Closed date
2011-10-31
Last modified date
2011-10-31

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

Document Information

Modified date:
28 October 2021

Tips

PM48578: WLM EXTERNAL CLIENT DATA PROPAGATION INCOMPLETE

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

R800 PSY

Document Information

Share your feedback

Need support?