|
| |
| Sun Java System Application Server 7 2004Q2 Update 1 Standard and Enterprise Edition Error Messages Reference | |
About This Guide
This guide describes error messages in the Sun Java™ System Application Server Standard and Enterprise Edition 7 environment.
This preface addresses the following topics:
Who Should Use This GuideThe intended audience for this guide is the person who develops, assembles, and deploys beans in a corporate enterprise.
This guide assumes you are familiar with the following topics:
Using the DocumentationThe Sun Java System Application Server Standard and Enterprise Edition manuals are available as online files in Portable Document Format (PDF) and Hypertext Markup Language (HTML).
The following table lists tasks and concepts described in the Sun Java System Application Server manuals. The manuals marked (updated for 7 2004Q2) have been updated for the Sun Java System Application Server Standard and Enterprise Edition 7 2004Q2 release. The manuals not marked in this way have not been updated since the version 7 Enterprise Edition release.
How This Guide Is OrganizedThis guide is a compilation of messages that you may encounter while running the Application Server. Each message begins with a message ID, which has a format like the following:
<Subsystem><4CharacterIntegerId>.
The subsystem is identified by the initial characters in the message ID. For example, in JMS0001, the subsytem is JMS.
The error messages in this guide are divided into chapters based on the subsystem prefix:
The messages defined in this reference guide also include the following information:
- Severity: Messages are assigned a severity level ranging from FINEST to FATAL. However, in this document all messages with a log level less than INFO (FINEST, FINER, FINE, CONFIG, and INFO) are not listed. For a description of what these log levels mean, see the Administrator’s Guide, “Using Logging”.
- Description: Meaning and likely cause of the message.
- Action: Instructions on how to address the condition that caused the message to be generated.
- See Also: Pointer to a relevant document or guide, where applicable.
Documentation ConventionsThis section describes the types of conventions used throughout this guide:
General Conventions
The following general conventions are used in this guide:
- Font conventions include:
- The monospace font is used for sample code and code listings, API and language elements (such as function names and class names), file names, pathnames, directory names, and HTML tags.
- Italic type is used for code variables.
- Italic type is also used for book titles, emphasis, variables and placeholders, and words used in the literal sense.
- Bold type is used as either a paragraph lead-in or to indicate words used in the literal sense.
- Installation root directories for most platforms are indicated by install_dir in this document. Exceptions are noted in Conventions Referring to Directories.
By default, the location of install_dir on most platforms is:
For the platforms listed above, default_config_dir and install_config_dir are identical to install_dir. See Conventions Referring to Directories for exceptions and additional information.
- Instance root directories are indicated by instance_dir in this document, which is an abbreviation for the following:
default_config_dir/domains/domain/instance
- UNIX-specific descriptions throughout this manual apply to the Linux operating system as well, except where Linux is specifically mentioned.
Conventions Referring to Directories
By default, when using the Solaris package-based or Linux RPM-based installation, the application server files are spread across several root directories. This guide uses the following document conventions to correspond to the various default installation directories provided:
- install_dir refers to /opt/SUNWappserver7, which contains the static portion of the installation image. All utilities, executables, and libraries that make up the application server reside in this location.
- default_config_dir refers to /var/opt/SUNWappserver7/domains, which is the default location for any domains that are created.
- install_config_dir refers to /etc/opt/SUNWappserver7/config, which contains installation-wide configuration information such as licenses and the master list of administrative domains configured for this installation.
Contacting SunYou might want to contact Sun Microsystems in order to:
Give Us Feedback
If you have general feedback on the product or documentation, please send this to:
http://www.sun.com/hwdocs/feedback/
Obtain Training
Application Server training courses are available at:
http://training.sun.com/US/catalog/enterprise/web_application.html/
Visit this site often for new course availability on the Sun Java System Application Server.
Contact Product Support
If you have problems with your system, contact customer support using one of the following mechanisms:
- The online support web site at:
http://www.sun.com/supportraining/
- The telephone dispatch number associated with your maintenance contract
Please have the following information available prior to contacting support. This helps to ensure that our support staff can best assist you in resolving problems:
- Description of the problem, including the situation where the problem occurs and its impact on your operation
- Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem. Here are some of the commonly used commands:
- Detailed steps on the methods you have used to reproduce the problem
- Any error logs or core dumps
- Configuration files such as:
- For an application, whether the problem appears when it is running in a cluster or standalone