![]() |
![]() |
|
|
| |
Troubleshooting Common Problems
The following section describes how to troubleshoot common problems including:
Collecting Diagnostic Information
Before contacting BEA Technical Support for help with cluster-related problems, follow the steps in this section to collect the required diagnostic information for your system. The primary diagnostic information for cluster-related problems is a log file that contains multiple thread dumps (if applicable) from the clustered server. This log file can be helpful in diagnosing a variety of cluster-related problems, but it is especially important for addressing problems related to cluster "freezes" and deadlocks.
Note: If you experience a cluster problem that involves a deadlock between server instances or otherwise causes your cluster to "hang," a log file that contains multiple thread dumps is a prerequisite for diagnosing your problem.
To create the required log file, follow these steps:
% java -ms64m -mx64m -verbose:gc -classpath $CLASSPATH -Dweblogic.domain=mydomain -Dweblogic.Name=clusterServer1 -Djava.security.policy==$WL_HOME/lib/weblogic.policy -Dweblogic.admin.host=192.168.0.101:7001 -Dweblogic.management.username=system -Dweblogic.management.password=systemPassword weblogic.Server >> logfile.txt 2>&1
Note: If you are running the JRockit JVM under Linux, see Getting a JRockit Thread Dump Under Linux.
Getting a JRockit Thread Dump Under Linux
If you use the JRockit JVM under Linux, use one of the following methods to generate a thread dump.
To obtain the root PID, perform a:
ps -efHl | grep 'java' **. **
using a grep argument that is a string that will be found in the process stack that matches the server startup command. The first PID reported will be the root process, assuming that the ps command has not been piped to another routine.
Note: Under Linux, each execute thread appears as a separate process under the Linux process stack. To use Kill -3 on Linux you supply must match PID of the main WebLogic execute thread, otherwise no thread dump will be produced.
Providing Diagnostics to BEA Technical Support
After you have created a diagnostic log file (with thread dumps, if applicable), use the following guidelines when providing information to your BEA Technical Support representative:
% tar czf logfile.tar logfile.txt
Note: Always include the compressed log file as an attachment to the message. Do not cut and paste the log file into the body of the e-mail.
Addressing Common Problems
The following sections provide solutions to common cluster-related problems. They also provide information for how to diagnose non-specific problems, such as poor cluster performance.
Server Fails to Join a Cluster
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.
Other items which require troubleshooting include general configuration errors and communications errors, such as:
Note that each operating system has specific configuration requirements for configuring multicast; you should check your operating system documentation for help in correcting this error.
![]() |
![]() |
![]() |
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|