IBM Support

PM37851: WLM TO ALLOW PERMANENT LSD RETRY

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

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



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM37851

Modified date: 23 June 2011