Errors setting up multiserver environments

What kind of problem are you seeing?

If none of these problem solution descriptions fixes your problem:

  1. Browse the 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 in 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).

After creating and starting a cluster, the cluster does not start, and logs show that servers in the cluster are not found

This error can occur when the configuration is not synchronized from the deployment manager to a node. If auto synchronization is enabled, wait until the synchronization has had a chance to run. If you are using manual synchronization, explicitly request a sync to each node on the cluster.

To determine whether synchronization has taken place, look at the configuration on the node machines using the administrative console and verify that the new cluster members are defined on each node.

One or more nodes do not show up in the administrative console

This can occur when there is a basic connectivity problem between the deployment manager server and other servers in the topology. To determine whether this is the problem, look for the fileserverindex.xml in the deployment manager directory structure.

The addNode command fails

This error can occur when the deployment manager Domain Name Server (DNS) configuration is set up improperly. The default installation on Linux uses the loopback address (127.0.0.1) as the default host address. To verify that this is the problem, query the hostname of the suspect machine. If it returns localhost 127.0.0.1, or if file transfer traces at the node show the node trying to upload files to a URL that includes 127.0.0.1, the node has an incorrect DNS configuration.

To correct this problem, update the /etc/hosts file or the name service configuration file, /etc/nsswitch.conf, to query the Domain Name Server or Network Information Server (NIS) before searching hosts.

Application files are not present on all nodes

In the WebSphere Application Server Network Deployment environment, application binary files are transferred to the individual nodes where applications are supported as part of the node sync operation. During node sync, application files are only propagated if their deployment descriptors specify enableDistribution=true. This flag is specified as part of the application installation procedure in the administrative console, and is stored as a property in the install_root/config/cells/cell_name/applications/application_name/deployment.xml file.

To confirm that this is the cause, check to see whether the enableDistribution flag is set. If it is already set to true, ensure that the target node is configured to run auto file synchronization.

If both of these settings are correct and the problem persists, manually perform an explicit synchronization. If the application files still do not appear in the installation directory, use the EARExpander tool (located in install_root/bin) to expand the EAR file from the repository to the installation destination. On remote nodes, the repository should appear in theconfig/cells/cell_name/applications/application_name.ear/ directory.

After downloading the Network Deployment plug-in to my system, my server does not start

If you experience this situation, the most likely cause is that the transport paths in the plug-in must be modified to work in your environment. See the Example: Manually editing transport settings in the server.xml file topic for information on how to modify these settings.

In a clustered environment, a server with debug mode enabled does not start

This problem occurs when the following three conditions exist:

The server will not start because multiple servers processes running on the same physical host machine with debug enabled cannot use the same debug port.

To correct this problem, for each server:

  1. On the Administrative Console select Server > Application Servers > server name > Process Definition > process name> Java Virtual Machine
  2. Update the Debug argument so that the address of the debug port (address=port number) is unique for each server process.

The node agent SystemOut.log file contains a null pointer exception and the node agent fails to start an application server.

The following output is an example of the null pointer exception seen in the node agent SystemOut.log file during node agent startup. The exception occurs if the Node restart state setting is set to running on the Monitoring policy administrative console page and the startup synchronization setting is set to true on the File synchronization service administrative console page.

12/14/04 11:43:29:253 EST] 28680f95 NodeSync E ADMS0012E:
Unable to create administrative client connection:
com.ibm.websphere.management.exception.AdminException: Admin
client connection to deployment manager is unavailable
at
com.ibm.ws.management.sync.NodeSync.getAdminClient(NodeSync.java:484)
at
com.ibm.ws.management.sync.NodeSync.getCellRepositoryEpoch(NodeSync.java:344)
at
com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java:220)
at
com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:139)
at java.lang.Thread.run(Thread.java:567)

The node agent does not start the application servers since the node agent cannot perform the synchronization successfully.

To avoid the exception, do one of the following actions:


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
Workload not getting distributed



Searchable topic ID:   rtrb_multprobs
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_multprobs.html

Library | Support | Terms of Use | Feedback