WAS v8.5 > Reference > Administrator best practicesWeb container troubleshooting tips
IBM recommends using the HPEL log and trace infrastructure. With HPEL, one views logs using the LogViewer command-line tool in PROFILE/bin.
If you are having problems starting a web module, or accessing resources within a particular web module:
- View the JVM logs and process logs for the application server which hosts the problem web modules, and look for messages in the JVM output file which indicate the web module has started successfully. You should see messages similar to the following:
WebContainer A SRVE0161I: IBM WAS - Web Container. Copyright IBM Corp. 1998-2002 WebContainer A SRVE0169I: Loading Web Module: [module_name] ApplicationMg A WSVR0221I: Application started: [application_name] HttpTransport A SRVE0171I: Transport http is listening on port [port_number] [server_name] open for e-business in [profile_root]/logs/[server_name]/SystemOut.log
- For specific problems that can cause servlets, HTML files, and JSP files not to be served, refer to the topic, web resource (JSP file, servlet, HTML file, image) does not display .
- For a detailed trace of the run-time behavior of the web container, enable trace for the component com.ibm.ws.webcontainer using com.ibm.ws.webcontainer*=all.
If application server related calls fail during Servlet.init method, we can either:
- Initialize the servlet manually by making a single request to that servlet in your browser when the server is ready for e-business instead of starting the servlet upon startup or
- Choose not to make application server related calls in the servlet's init method.
If the property to start servlets during application server startup is enabled, part of its startup process calls the Servlet.init method on its servlets when we start the web container. Therefore, when the web container is starts and calls the init method, other components such as Naming and Work Load Management may not be fully started yet. As a result, application server related calls may not work since all of the application server components may not be ready yet. Once the application server is 'ready for e-business', it is completely ready.
If none of these steps fixes your problem, check to see if the problem has been identified and documented by looking at the available online support (hints and tips, tech notes, and fixes). If we do not find your problem listed there contact IBM support.
For current information available from IBM Support on known problems and their resolution, refer to the IBM Support page.
IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.
Related concepts:
Troubleshooting help from IBM
Related
View JVM logs
Reference:
Web module or application server stops processing requests
Process logs
>Web resource is not displayed
Diagnose and fixing problems: Resources for learning
Related information:
http://www.ibm.com/support/search.wss?rs=180&tc=SSEQTP&tc1=SSCMPDF