Workload not getting distributed

What kind of problem are you seeing?

If none of these problem solution descriptions fixes your problem:

  1. Browse the of the problem deployment manager and application servers:
    1. Look up any error messages by selecting the Reference view of the information center navigation and expanding Messages in the navigation tree.
    2. If Java exceptions appear in the log files, try to determine the actual subcomponent directly involved in the problem by examining the trace stack and looking for a WebSphere Application Server-related class near the top of the stack (names beginning with com.ibm.websphere or com.ibm.ws) that threw the exception. If appropriate, review the steps for troubleshooting the appropriate subcomponent under the Troubleshooting by component: what is not working? topic.

      For example, if the exception appears to have been thrown by a class in the com.ibm.websphere.naming package, review the Naming Services Component troubleshooting tips topic.

  2. Ensure that all the machines in your configuration have TCP/IP connectivity to each other by running the ping command:
    1. From each physical server to the Deployment Manager
    2. From the Deployment Manager to each physical server
  3. Although the problem is happening in a clustered environment, the actual cause might be only indirectly related, or unrelated, to clustering. Investigate all relevant possibilities:
    1. If an enterprise bean on one or more servers is not serving requests, review the Cannot access an enterprise bean from a servlet, JSP, stand-alone program, or other client and Cannot access an object hosted by WebSphere Application Server from a servlet, JSP file, or other client topics.
    2. If problems seem to appear after enabling security, review the Errors or access problems after enabling security topic.
    3. If an application server stops responding to requests, or spontaneously dies (its process closes), review the Web module or application server dies or hangs topic.
    4. If SOAP requests are not being served by some or all servers, review the Errors returned to client trying to send a SOAP request topic.
    5. If you have problems installing or deploying an application on servers on one or more nodes, review the Troubleshooting code deployment and installation problems topic.
  4. If your topology consists of a Windows-based Deployment Manager with UNIX-based servers, browse any recently-updated .xml and .policy files on the UNIX-based platform using vi to ensure that Control-M characters are not present in the files. To avoid this problem in the future, edit these files using vi on the UNIX-based platform, to avoid inserting these characters.
  5. Check the steps for troubleshooting the Workload Management component.
  6. Check to see if the problem is identified and documented by looking at available online support (hints and tips, technotes, and fixes).

Web (HTTP) requests are not distributed to all servers

If HTTP requests are not being distributed to all servers:

EJB requests are not distributed to all servers

If a client cannot reach a server in a cluster thought to be reachable, a server might be marked unusable, or is down. To verify this:

EJB requests are not distributed evenly

There are a number of possible reasons for this behavior, which generally fall into one or more of these categories:

Work load management of WebSphere Application Server is based on a round robin scheme of request distribution. This results in balance being determined by numbers of requests rather than by any other measure. A true balance problem is determined by comparing the number of requests processed by each member of the cluster with the weights that have been set for each of those members. This is done by following the steps in the Troubleshooting the Workload Management component topic.

A failing server still receives enterprise bean requests (failover fails)

Some possible causes of this problem are:

Stopped or hung servers do not share the workload after being restored

This error occurs when the servers that were unavailable are not recognized by the Workload Management component after they are restored. There is an unusable interval determined by the property com.ibm.websphere.wlm.unusable.interval during which the workload manager waits to send to a server that has been marked unusable. By default this is 15 minutes.

You can confirm that this is the problem by ensuring that servers that were down are now up and capable of servicing requests. Then wait for the unusable interval to elapse before checking to determine whether failover occurs.

For current information available from IBM Support on known problems and their resolution, see the IBM Support page.

IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.


Related tasks
Troubleshooting by task: What are you trying to do?
Troubleshooting by component: What is not working?
Related reference
Troubleshooting application runtime and management problems
Errors setting up multiserver environments
Workload Management component troubleshooting tips



Searchable topic ID:   rtrb_wlmprobs
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/rtrb_wlmprobs.html

Library | Support | Terms of Use | Feedback