Troubleshoot: Access Web resources

Use the resources listed below to determine the cause of problems that occur when you are unable to access Web resources:

Unable to serve any Web resources

• See the installation of WebSphere Application Server - Express for iSeries topic. The topic will guide you through the system verification and serving of a Web resource.

• If you are using HTTP Server (powered by Apache), generate a trace on your HTTP Server instance and look for errors. See Use the application server trace service for more information.

• Web server plug-in trace.

  The plug-in log records HTTP server-side processing and servlet request routing between the HTTP Server and WebSphere Application Server - Express. (The plug-in connects the HTTP Server and WebSphere Application Server - Express together.)

  Manage this log by editing the application server plugin-cfg.xml file. The plugin-cfg.xml file contains a tag near the beginning named Log. Log has two attributes: LogLevel and Name.

  • LogLevel specifies the amount and type of information that is logged to a file. Valid values are Trace, Warn, and Error.

  • Name specifies the location and name of the file where logging information is written.

• Read the release notes. See WebSphere Application Server - Express Release Notes for more information.

Unable to serve a particular Web resource

• Check the application server standard output and standard error log files for errors. For information on the application server log files and where they are located, see WebSphere Application Server - Express log files.

• Read the release notes. See WebSphere Application Server - Express Release Notes for more information.

Servlet or JSP displays an error or Java exception instead of the expected output

• Check the application server standard output and standard error log files for errors. For information on the application server log files and where they are located, see WebSphere Application Server - Express log files.

• Add logging and tracing to your application with the JRas framework. See Use the application server trace service for more information.

• Add output to your servlet, JSP, or Java code in the form of System.out.println() statements to aid in debugging. The output from any System.out.println() statements is written to the standard output log file for the application server in which the code is running. For information on the application server log files and where they are located, see WebSphere Application Server - Express log files.

• If the failure occurs within a JSP, use the keepgenerated attribute to keep the generated servlet source file to inspect for errors.

• Read the release notes. See WebSphere Application Server - Express Release Notes for more information.