IBM Support

PM48578: WLM EXTERNAL CLIENT DATA PROPAGATION INCOMPLETE

Fixes are available

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.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

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM48578

Modified date: 31 October 2011