IBM Support

PM46408: WLM CLIENT FAILS TO CONNECT

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 a scenario in which a customer has either a java thin client
    performing the routing, or a WebSphere Application Server
    process routing to a cluster in another cell, if a naming
    lookup is performed on a cluster member after the cluster
    member has begun to start up, but before the cluster member
    has fully come up for e-business, that client will not receive
    back the necessary cluster data to continue to make routing
    attempts. This will leave the client in an unusable state for
    that cluster unless it is essentially restarted, a new
    bootstrap, initial context, and naming lookup.
    
    This problem behavior is due to how workload management (WLM)
    uses the original bootstrap location as a point of failover,
    which can only happen once per client, as well as the client
    performing the naming lookup before the server is open for
    e-business.  To remove the possibility of the client process
    getting into a bad state, there is a custom property added to
    the WLM code to allow the client to reuse the original
    bootstrap location more than once as a location to route
    requests to.  This will allow the client, assuming it is
    sending load while the servers are in the process of coming
    up, to make continous connection attempts until the LSDCluster
    data is available to be passed back to the client, at which
    time that data will be used for future requests.  To enable
    this custom property, a customer would go through the
    administrative console under:
    
    System Administration -> Cell -> Custom Properties
    
    and define a new custom property with the name:
    
    IBM_CLUSTER_REUSE_ORIGINAL_IOR
    
    and a value of true.  Save, sync with nodes, and restart the
    client processes for it to pick up the custom property.
    

Local fix

  • na
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
    *                  V7.0 and V8.0 Network Deployment edition    *
    ****************************************************************
    * PROBLEM DESCRIPTION: WLM-enabled client fails to connect to  *
    *                      remote cell                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In a scenario in which a customer has either a java thin client
    performing the routing, or a WebSphere Application Server
    process routing to a cluster in another cell, if a naming
    lookup is performed on a cluster member after the cluster
    member has begun to start up, but before the cluster member
    has fully come up for e-business, that client will not receive
    back the necessary cluster data to continue to make routing
    attempts. This will leave the client in an unusable state for
    that cluster unless it is essentially restarted, a new
    bootstrap, initial context, and naming lookup.
    

Problem conclusion

  • This problem behavior is due to how WLM uses the original
    bootstrap location as a point of failover, which can only
    happen once per client, as well as the client performing the
    naming lookup before the server is open for e-business.  To
    remove the possibility of the client process getting into a bad
    state, there is a custom property added to the WLM code to
    allow the client to reuse the original bootstrap location more
    than once as a location to route requests to.  This will allow
    the client, assuming it is sending load while the servers are
    in the process of coming up, to make continous connection
    attempts until the LSDCluster data is available to be passed
    back to the client, at which time that data will be used for
    future requests.  To enable this custom property, you would go
    through the administrative console under:
    
    System Administration -> Cell -> Custom Properties
    
    and define a new custom property with the name:
    
    IBM_CLUSTER_REUSE_ORIGINAL_IOR
    
    and a value of true.  Save, sync with nodes, and restart the
    client processes for it to pick up the custom property.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 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

    PM46408

  • 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-08-25

  • 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 #: PM46408

Modified date: 31 October 2011