Troubleshoot multiserver environment errors

 

+

Search Tips   |   Advanced Search

 

1. When creating a new profile in a mixed cell environment, a mismatch of templates occurs
2. Cluster does not start. Logs show servers in the cluster are not found
3. Nodes do not display in the admin console
4. The addNode command fails
5. Application files are not present on all nodes
6. After downloading the ND plug-in to my system, my server does not start
7. In a clustered environment, a server with debug mode enabled does not start

If none of these problem solution descriptions fixes the problem:

1. Browse the logs of the problem dmgr and applications servers.

   View the JVM logs.

   1. 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 WAS-related class near the top of the stack (names beginning with...
      • com.ibm.websphere
      • com.ibm.ws

      For example, if the exception seems to be created by a class in the package...

      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 dmgr
   2. From the dmgr 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 appserver stops responding to request, or spontaneously fails (its process closes), review the Web module or appserver stops processing requests topic.

   4. If SOAP requests are not served by some servers, review the Application client sending SOAP request receives errors 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 the topology consists of a Windows-based dmgr 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).

 

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...

For Windows, run...

APP_ROOT\bin\ws_ant.bat -buildfile updateNDProfileTemplates.xml

For non-AIX platforms...

USER_INSTALL_ROOT=APP_ROOT/profiles/my_DM_profile_name/

For AIX...

USER_INSTALL_ROOT=APP_ROOT/profiles/my_DM_profile_name/
export USER_INSTALL_ROOT
APP_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 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 admin console and verify that the new cluster members are defined on each node.

 

One or more nodes do not display in the admin console

This problem can occur when a basic connectivity problem exists between the dmgr server and other servers in the topology. Look for the serverindex.xml file in the dmgr directory structure:

• If the problem node does not display in the list, review the steps for adding a node to the cluster.

• If the problem node does display in the list:

  • From the dmgr server, ping the server name as it displays in the list. If the ping command indicates no communication, verify that the host name is correct in the list, correct it if necessary, then restart the dmgr.

  • If the name that displays in the list is the short name, ping the fully qualified network name. If the corrected name works, update the list, and restart the dmgr.

  • If the problem server uses DHCP, try replacing the logical host name with the IP address and restart the deployment manager.

    Change the serverindex.xml file each time the problem server address changes, and potentially each time the problem machine is rebooted. To avoid this problem, consider assigning a static IP address to the server.

• If we still cannot establish communication between the servers, contact your network administrator to resolve the problem, and restart the deployment manager after the problem is corrected.

 

The addNode command fails

This error can occur when the dmgr 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...

/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 admin console, and is stored as a property in...

APP_ROOT/config/cells/mycell/applications/myapp/deployment.xml

To confirm this problem, check to see whether the enableDistribution flag is set. If it is already set to true, verify 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...

APP_ROOT/bin/EARExpander

...to expand the EAR file from the repository to the installation destination.

On remote nodes, the repository displays in...

config/cells/mycell/applications/myapp.ear/

 

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

If we experience this situation, the most likely cause is that the transport paths in the plug-in must be modified to work in the environment.

 

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

This problem occurs when the following three conditions exist:

• Multiple server processes are configured to run on the same node

• More than one server has debug mode enabled

• The debug arguments for more than one of the servers are left at the default values, so that more than one server in the node is trying to use the same debug port (port number 7777).

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 admin console click...

   Server | Application servers | server_name | 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.

---

 

Related tasks

Troubleshooting administration

 

Related

Workload is not getting distributed
Workload management component troubleshooting tips