Web Container errors

Generally we got errors like

• “HTTP 404 errors”
• HTTP 500 errors” on
• Incorrect information displayed on Web pages.
  If you do not know the type of error, continue with“Collect and analyze the Webserver log:
  We need check acces log files in web servers:
  _ From the access.log:
  127.0.0.1 - - [28/Mar/2007:19:52:31 -0400] "GET url HTTP/1.1" 404 304
  127.0.0.1 - - [28/Mar/2007:20:03:48 -0400] "GET urlHTTP/1.1"500 5348
  Note the URL the Web server was trying to serve when the error occurred.
  Indicate error:
  [Wed Mar 28 19:52:31 2007] [error] [client 127.0.0.1] File does
  not exist: file_location the error:

1. HTTP 404 errors:

• External factors, such as a problem in the Web server
•  Configuration problems, such as an incorrect Web server plug-in or virtual
  host configuration.
• Runtime problems, such as an application or application server not started
• User or application problems, such as an incorrectly specified URL.

Errors displayed by the browser:

• The page cannot be displayed
• JSP error or JSF error
• Failed to find resource
• File not found
• WebGroup/virtual host not defined.

JSP error or JSF error:

• incorrectly specified URL.
• is not available on the server.
•  Web server plug-in configuration problem.
• Verify that the Web server plug-in is working correctly.
• Verify that the Web server is responding
• Verify that the application is running

WebGroup / Virtual Host has not been defined:

• Verify that the virtual host configuration is correct(set the host aliases, each
• consisting of a host name and port number)

Verify that the URL causing the error is specified correctly

• Verify that the application is running

2. HTTP 500 errors

• HTTP 500 errors indicate that an internal server problem has occurred during theprocess of serving the requested page. Examples of the types of problems that can cause this in WebSphere Application Server include:
• _ JSP processor errors
• _ Application code (JSP, JSF, servlet) errors
• _ Session errors
  To verify that an application server is available to serve the file:
• 1. Determine the server or cluster that hosts the application.
• 2. Check the status of the application server.
• 3. Start the application server if it is not running
  Root causes
  Some root causes for HTTP 500 errors are:
• _ Code error
• _ Invalid session object
• _ Response generation errors

Code error

• The root cause of this problem is usually a programming error.
• Invalid session object
   
  Check the servlet or JSP code that threw the exception to make sure that the
  session is not being invalidated too early. If that is not the case, check the
  session timeout interval to ensure that it is not too short.
• The session manager component uses the HttpSession interface to create a session between an HTTP client and the server. When a new session object is
  created, a unique session ID is assigned to it.
• Session tracking is use to maintain state and user information for
  multiple request

3. A WEB GROUP / VIRTUAL HOST PROBLEM

 

SRVE0255E : URI not working when i hit first time . when i refresh browser again its working
SRVE0255E  A WebGroup/Virtual Host to handle /<contextroot> has not been defined

Resolution :

1. server –>Enterprise Applications–><your application>/Resource references –>click on Browse and choose the correct one
2.Update the plugin and propagate
3.restart the web/application server
4. Then try again URL.

 

4. Error 500 : Internal Server error : ERROR: lib_stream: openStream: Failed in r_gsk_secure_soc_init: GSK_ERROR_BAD_CERT(gsk rc = 414)

 

Cause:

The above error indicates  WAS SSL certificate was not trusted by the WAS plugin configured for IHS
 
Resolution:

Extract the default Personal Certificate:
1. Login to the WebSphere Application Server Administrative Console.

2. Select Security > SSL certificate and key management > Key Stores and certificates.

3. Select NodeDefaultKeyStore for a stand-alone deployment or CellDefaultKeyStore for a Network deployment.

4. Click Personal Certificates, select the default check box, and then click Extract.

5. Give the extracted file a path and name, such as: /root/defaultCert.arm. Note: The convention is to give the file a .arm extension.

6. Leave encoding set to Base64.

7. Click OK.

Locate your *.kdb file:

1. In the httpd.conf file, find the directory in which the plugin-cfg.xml file is stored by searching for the WebSpherePluginConfig line

example:

WebSpherePluginConfig “/opt/IBM/HTTPServer/Plugins1/config/webserver1/plugin-cfg.xml”
2. Find the directory in which the key database file (*.kdb) is stored by searching for the term “keyring” in the plugin-cfg.xml file.
For example:
<PropertyName=”keyring” Value=”/opt/IBM/HTTPServer/Plugins1/config/webserver1/plugin-key.kdb”/>
Note this location as you will need to use it later

4. ERROR : checkOptions: combination of options specified is correct (67)Address already in use: make_sock: could not bind to address 10.xx.xx.xx:10021 no listening sockets available, shutting down Unable to open logs

Cause : The port already in use by another process

Resolution
1. Check the port is running or not : netstart -an |grep <port number>
2. kill -9 pid <old pind which port is running>
3. To change the new port number
4. restart web server : /usr/local/apache /bin --- ./apachectl -k start.

5. StaleConnectionException
This exception (com.ibm.websphere.ce.cm.StaleConnectionException) indicates that the connection currently being held is no longer valid.
This can occur for numerous reasons, including the following:
1 . The application tries to get a connection and fails, as when the database is not started.
2 A connection is no longer usable due to a database failure. When an application tries to use a connection it has previously obtained, the connection is no longer valid. In this case, all connections currently in use by an application could get this error when they try to use the connection.
3 The application using the connection has already called close() and then tries to use the connection again.
4 The connection has been orphaned because the application had not used it in at most two times the orphan timeout; then the application tries to use the orphaned connection.

6.