InfoCenter Home >
8: Problem determination >
8.6: Diagnosing configuration and installation problems

8.6: Diagnosing configuration and installation problems

WebSphere Application Server uses a database to store and share configuration information across nodes. Problems configuring the database are described in the installation problems section.

Generally, if the database is not configured properly, the WebSphere Application Server installation process will fail. Configuration problems occur after the product is installed.

The following table describes common configuration problems. Select an entry for more information.

Problem description Cause of problem
Cannot retrieve application data Incorrect use of the database as a session store:
java.io.InvalidClassException occurs after bean is modified Serialized descriptor must be recreated
Web server problems:

Error 404 - URL not found occurs when accessing a servlet

HTTP Server hostname or port problem

Error 500 - Failed to load target servlet

Servlet missing from Web application classpath

FATAL - Could not bind to the administrative server error

Remote administration failure

Changes to clones not visible

Cloning failures

Nanny process fails to start administrative server

Verify all installation steps were successful

Administrative server fails to start

General installation setup problem

Go to previous article: Installation Problems Go to next article: Using Application Level Facilities

 

 
Go to previous article: Installation Problems Go to next article: Using Application Level Facilities