Sun Java System Application Server Enterprise Edition 8.1 2005Q2 Troubleshooting Guide

- Previous: Verify System Configuration
- Next: Examine Log Files

## Evaluate Messages

Messages generally include information about the attempted action, the outcome of the action, and, if applicable, the cause of jeopardy or failure.

### Types of Messages

The log files contain the following general types of message entries:

- Error – These messages mark critical failures that cause status to be reported as Failed. Error messages generally provide detailed information about the nature and the cause of the problem that occurred.

- Warning – These messages mark non-critical failures. Warning messages generally contain information about the cause and the nature of the failure, and also provide possible remedies.

- Information – These messages mark normal completion of particular tasks.

### Error Messages

A problem is often accompanied by an error message that prevents the application from proceeding.

- In some cases, the message is very clear about what is wrong and what needs to be done, if anything, to fix it. For example, if you start a domain using the `asadmin start-domain` command, then inadvertently issue the same command again after the domain has started, the following message is displayed:

      userD:\\Sun\\studio5_se\\appserver8\\bin\>asadmin start-domain
      Domain already started : domain1
      Domain domain1 Started.

  In this case, the message gives clear guidance and the problem can be disregarded.

- Sometimes an error message gives only general information about the problem or solution, or suggests multiple possibilities. For example:

      [16/Jun/2003:22:20:50] SEVERE ( 2204): WEB0200: Configuration error
      in  web module [JAXBProjectStudio] (while initializing virtual server
      [server1]) com.iplanet.ias.config.ConfigException: Failed to load
      deployment descriptor for: JAXBProjectStudio cause:
      java.io.FileNotFoundException:

  In this case, the problem is not obvious, or there might be multiple things wrong. You might have to consider various possibilities and perhaps a number of solutions. If the proposed fix is time consuming or costly, take steps to ensure that the fix is likely to be correct before actually doing anything.

- Some error messages are either not helpful or provide little guidance; for example:

      [23/Jun/2003:16:50:45] WARNING ( 1972): for host 127.0.0.1 trying to GET
      /SupplierServiceClient1/SupplierServiceClient1_SOAP.html, send-file
      reports:  HTTP4144: error sending D:/Sun/studio5_se/appserver8/domains/
      domain1/server1/applications/j2ee-modules/SupplierServiceClient1_1/
      SupplierServiceClient1_SOAP.html (Overlapped I/O operation is in progress.)
      status=1:5

  In this case, there is very little information to go on. It is especially important to identify the exact situation that caused the error, and what the symptoms are before proceeding.

  For descriptions of all the Application Server error messages, refer to the Sun Java System Application Server Error Message Reference at the following location:

  `http://docs.sun.com/db/coll/ApplicationServer8_04q4`

- Previous: Verify System Configuration
- Next: Examine Log Files

- © 2010, Oracle Corporation and/or its affiliates