Web resource is not displayed

Use this information to troubleshoot problems that occur when attempting to display a resource in a browser.

If you are not able to display a resource in your browser, follow these steps:
  1. Verify that your HTTP server is healthy by accessing the URL http://server_name from a browser and seeing whether the Welcome page appears. This action indicates whether the HTTP server is up and running, regardless of the state of WebSphere® Application Server.
  2. If the HTTP server Welcome page does not appear, that is, if you get a browser message like page cannot be displayed or something similar, try to diagnose your Web server problem.
  3. If the HTTP server appears to function, the Application Server might not be serving the target resource. Try accessing the resource directly through the Application Server instead of through the HTTP server.

    If you cannot access the resource directly through the Application Server, Verify that the URL used to access the resource is correct.

    If the URL is incorrect and it is created as a link from another JSP file, servlet, or HTML file, try correcting it in the browser URL field and reloading, to confirm that the problem is a malformed URL. Correct the URL in the "from" HTML file, servlet or JSP file.

    If the URL appears to be correct, but you cannot access the resource directly through the Application Server, verify the health of the hosting Application Server and Web module:
    1. View the hosting Application Server and Web module in the administrative console to verify that they are up and running.
    2. Copy a simple HTML or JSP file (such as SimpleJsp.jsp in the WebSphere Application Server directory structure) to your Web module document root, and try to access it. If successful, the problem is with your resource.

      View the logs of your Application Server to find out why your resource cannot be found or served .

  4. If you can access the resource directly through the Application Server, but not through an HTTP server, the problem lies with the HTTP plug-in -- the component that communicates between the HTTP server and the WebSphere Application Server.
  5. If the JSP file and the servlet output are served, but not static resources such as .html and image files, see the steps for enabling file serving.
  6. If some kinds of resources display correctly, but you cannot display a servlet by its class name:
    • Verify that the servlet is in a directory in the Web module class path, such as in the /Web_module_name.war/WEB-INF/classes directory.
    • Verify that you specify the full class name of the servlet, including its package name, in the URL.
    • Verify that "/servlet" precedes the class name in the URL. For example, if the root context of a Web module is "myapp", and the servlet is com.mycom.welcomeServlet, then the URL reads:
      http://hostname/myapp/servlet/com.mycom.welcomeServlet
      
    • For servlets or other resources served by mapped URLs, the URL is http://hostname/Web module context root/mappedURL.

Accessing a Web resource through the application server and bypassing the HTTP server

You can bypass the HTTP server and access a Web resource through the application server. It is not recommended to serve a production Web site in this way, but it provides a good diagnostic tool when it is not clear whether a problem resides in the HTTP server, WebSphere Application Server, or the HTTP plug-in.

To access a Web resource through the Application Server:
  1. Determine the port of the HTTP service in the target application server.
    1. In the WebSphere administrative console, click Servers > Application Servers.
    2. Select the target server, then under Additional Properties click Web Container.
    3. Under the Additional Properties of the Web container, click HTTP Transports. You see the ports listed for virtual hosts served by the application server.
  2. Use the HTTP transport port number of the application server to access the resource from a browser. For example, if the port is 9080, the URL is http://hostname:9080/myAppContext/myJSP.jsp.
  3. If you are still unable to access the resource, verify that the HTTP transport port is in the "Host Alias" list:
    1. Click Application Servers > Your_ApplicationServer > Web Container > HTTP Transports to check the Default virtual host and the HTTP transport ports used by this application server.
    2. Click Environment > Virtual Hosts > default host > Host Aliases to check if the HTTP transport port exists. Add an entry if necessary. For example, if the HTTP port for your application is server is 9080, add a host alias of *:9082.



Related tasks
Deploying and administering J2EE applications
Related reference
Application startup errors
Reference topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 8:25:23 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=rtrb_pagedisplayprob
File name: rtrb_pagedisplayprob.html