PM37851: WLM TO ALLOW PERMANENT LSD RETRY

Fixes are available

APAR status

Closed as program error.

Error description

There are possible scenarios in which the LSDCluster data can
get in a bad state, which if the cluster members are recycled,
can lead to a client being unable to connect to a remote
cluster, resulting in NO_IMPLMENT exceptions.  This APAR adds
the ability to configure the WLM code such that the LSDCluster
data will be refreshed on every request, which if the nodeagents
are up and running, would result in the client breaking out of
the bad LSDCluster state and being able to reconnect properly to
the remote cluster.

Local fix

```
na
```

Problem summary

****************************************************************
* USERS AFFECTED:  Users of IBM WebSphere Application Server   *
*                  Network Deployment edition V7.0 and v8.0    *
*                  Clustering                                  *
****************************************************************
* PROBLEM DESCRIPTION: NO_IMPLEMENT exceptions seen after      *
*                      cluster member restarts                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
There are possible scenarios in which the LSDCluster data can
get in a bad state, which if the cluster members are recycled,
can lead to a client being unable to connect to a remote
cluster, resulting in NO_IMPLMENT exceptions.  This APAR adds
the ability to configure the WLM code such that the LSDCluster
data will be refreshed on every request, which if the nodeagents
are up and running, would result in the client breaking out of
the bad LSDCluster state and being able to reconnect properly to
the remote cluster.

Problem conclusion

The workload management (WLM) code added a new custom property
to force the WLM code to reset and rebuild the list of LSDs it
can use in any scenario or situation they become unusable.

In order to enable this custom property, in the
administrative console click on "System Administration"
on the left side, click on "Cell" underneath that, then click
on "Custom Properties" in the middle frame.

Create a new custom property with the name:

IBM_CLUSTER_LSD_CLUSTER_RESET

and a value of true.  Save the changes, synchronize with the
nodes and on the next restart of the processes the custom
property will get picked up.

It should be noted that this is an extremely rare
condition to encounter.  Any customer seeing NO_IMPLEMENT
exceptions should consider this APAR a last resort.  There are
many other APARs, configuration errors and runtime problems
which can cause a NO_IMPLEMENT exception and it is much more
likely any of those are occurring than this APAR.


The fix for this APAR is currently targeted for inclusion in
fix packs 7.0.0.19 and 8.0.0.1.  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
PM37851
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-04-27
Closed date
2011-06-23
Last modified date
2011-06-23

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:
27 October 2021

Tips

PM37851: WLM TO ALLOW PERMANENT LSD RETRY

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?