Use this information to troubleshoot problems with setting up multiserver environments.
View the JVM logs.
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.
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 WebSphere Application Server. To Lift restrictions on a mixed cell environment, you can run a command from the bin directory of the WebSphere Application Server installation root to update the profile.
app_server_root\bin\ws_ant.bat -buildfile updateNDProfileTemplates.xml
For UNIX® and Linux® platforms, issue the following commands.
For non-AIX platforms, the default installation root is /opt/IBM/WebSphere/AppServer.
For AIX® platforms, the default installation root is /usr/IBM/WebSphere/AppServer.
USER_INSTALL_ROOT=app_server_root/profiles/your_DM_profile_name/
USER_INSTALL_ROOT=app_server_root/profiles/your_DM_profile_name/
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 you 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.
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.
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 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_name/applications/application_name/deployment.xml file.
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 profile_root/config/cells/cell_name/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_name/applications/application_name.ear/ directory.
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.
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.