Web container troubleshooting tips

 

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 appserver which hosts the problem Web modules, and look for messages in the JVM output file which indicate that 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 JavaServer Pages files not to be served, see 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:com.ibm.ws.wswebcontainer.*=all.

If appserver related calls fail during Servlet.init method, you 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

• You can choose not to make appserver related calls in the servlet's init method.

If the property to start servlets during appserver startup is enabled, part of its startup process calls the Servlet.init method on its servlets when you 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, appserver related calls may not work since all of the appserver components may not be ready yet. Once the appserver 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 you don't find your problem listed there contact IBM support.

For current information available from IBM Support on known problems and their resolution, see 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 tasks

Modifying the default Web container configuration

 

Related Reference

Web module or appserver stops processing requests

 

Reference topic