+

Search Tips   |   Advanced Search

Multiserver environment errors

Use this information to troubleshoot problems with setting up multiserver environments.

What kind of problem are you seeing?

If none of these problem solution descriptions fixes our problem:

  1. Browse the logs of the problem deployment manager and applications servers.

    View the JVM logs.

    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 are displayed 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 created the exception.

      For example, if the exception seems to be created 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 the 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 occurring in a clustered environment, the actual cause might be 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 Enterprise bean cannot be accessed from a servlet, a JSP file, a stand-alone program, or another client and Application access problems topics.

    2. If problems seem to occur after enabling security, review the Access problems after enabling security topic.

    3. If an application server stops responding to request, or spontaneously fails (its process closes), review the Web module or application server stops processing requests topic.

    4. If SOAP requests are not served by some servers, review the Application client SOAP request troubleshooting tips topic.

    5. If we have problems installing or deploying an application on servers on one or more nodes, review the Application deployment problems topic.

  4. If our 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 the vi editor to ensure that Control-M characters are not present in the files. Edit these files using the vi editor 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).

(Dist)

When trying to create a new profile in a mixed cell environment, a mismatch of templates can occur

This problem occurs because profile templates are not updated when a version 6.0.x fixpack is applied on top of version 6.0.x of WAS. To Lift restrictions on a mixed cell environment, we can run a command from the bin directory of the WAS installation root to update the profile.

For the Windows platform, issue the following command... root:

For UNIX and Linux platforms, issue the following commands:

    • For non-AIX platforms issue the following command:

        USER_INSTALL_ROOT=app_server_root/profiles/your_DM_profile/

    • For AIX issue the following command:

        USER_INSTALL_ROOT=app_server_root/profiles/your_DM_profile/

  2. export USER_INSTALL_ROOT
  3. app_server_root/bin/ws_ant -buildfile updateNDProfileTemplates.xml


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 run. If we are using manual synchronization, explicitly request a synchronization to each node on the cluster.

To determine whether synchronization has occurred, 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 display in the administrative console

This problem can occur when a basic connectivity problem exists between the deployment manager server and other servers in the topology. Look for the serverindex.xml file 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 systems uses the loopback address (127.0.0.1) as the default host address. To verify this problem, query the host name of the suspect machine. If the query returns localhost 127.0.0.1, or if the file transfer traces at the node show that the node is trying to upload files to a web address 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 WAS ND environment, application binary files are transferred to the individual nodes where applications are supported as part of the node synchronization operation. During node synchronization, 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 app_server_root/config/cells/cell/applications/application_name/deployment.xml file.

(iSeries) In the WAS ND 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 profile_root/config/cells/cell/applications/application_name/deployment.xml file.

To confirm this problem, 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 a synchronization. If the application files still do not display in the installation directory, use the EARExpander tool in app_server_root/bin directory to expand the EAR file from the repository to the installation destination. On remote nodes, the repository displays in the config/cells/cell/applications/application_name.ear/ directory.


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

This problem occurs when the following three conditions exist:

The server does 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 click Server > Application servers > server > Java and Process Management > Process Definition > 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.

  • Troubleshoot administration
  • Workload is not getting distributed
  • Workload management component troubleshooting tips