Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	e-docs   |   Site Map   |   Search   |   Contact   |   Glossary   |   WebLogic Server Documentation
Using WebLogic Server Clusters:   Previous topic   |   Next topic   |   Contents   |  Index

There are several reasons why a WebLogic Server does not join a cluster on startup, including general network availability and WebLogic-specific configuration problems. Use this checklist to check your configuration and startup process.

1. Check your command-line parameters for typos, misspellings, etc.

2. Verify that there are no physical problems with your network connection, etc. Network connections can be verified using the dbping utilities discussed in Testing Connections.

3. Verify that no other application is using the cluster multicast address.

4. Run the utils.MulticastTest utility to verify that multicast is working.

5. Run the utils.system utility to verify CLASSPATH consistency if you are not using a shared file system classpath.

Other items which require troubleshooting include general configuration errors and communications errors, such as:

1. Incompatible version numbers. All WebLogic Servers in the cluster must be the same version. If a server attempts to join a cluster with a WebLogic Server whose version does not match the other servers in the cluster, an error message will be generated.

2. Unable to find a license for clustering. Your WebLogic license does not include the clustering feature. Contact your sales representative.

3. Unable to send service announcement. This could indicate a general network problem, or a misconfigured DNS. Clustered servers communicate among themselves over multicast and must share the same (exclusive) multicast address.

4. Cannot set default clusterAddress properties value. This could mean that another server with the same IP address has already joined the cluster. Check to make sure you do not have duplicate IP addresses assigned to multiple machines.

5. Unable to create a multicast socket for clustering, Multicast socket send error, or Multicast socket receive error. These communications errors are most likely caused by an incorrect or bad multicast address.

   Note that each operating system has specific configuration requirements for configuring multicast; you should check your OS documentation for help in correcting this error.

Copyright © 2000 BEA Systems, Inc. All rights reserved.
browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.