Workload not getting distributed

What kind of problem are you seeing?

If none of these problem solution descriptions fixes your problem:

  1. Browse the JVM logs 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.
  4. 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:

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

Some possible causes of this problem are:

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



Searchable topic ID:   rtrb_wlmprobs
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/rtrb_wlmprobs.html

Library | Support | Terms of Use | Feedback