+

Search Tips   |   Advanced Search

Web container troubleshooting tips

IBM recommends using the High Performance Extensible Logging (HPEL) log and trace infrastructure . We view HPEL log and trace information using the logViewer .

If we are having problems starting a web module, or accessing resources within a particular web module:

If application server related calls fail during Servlet.init method, we can either:

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 our 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 our 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:

  • Troubleshooting help from IBM
  • View JVM logs
  • Web module or application server stops processing requests
  • Process logs
  • Web resource is not displayed
  • Diagnose and fix problems: Resources for learning
  • http://www.ibm.com/support/search.wss?rs=180&tc=SSEQTP&tc1=SSCMPDF