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 followingWebContainer 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 [$WAS_HOME]/log/[server_name]/SystemOut.log
- For specific problems that can cause servlets, HTML files, and JavaServer Pages (JSP) files not to be served, seeWeb resource JSP(file, servlet, HTML file, image) does not display .
- Use the Log Analyzer tool to browse the service log (activity.log) file for clues.
- For a detailed trace of the run-time behavior of the Web container, enable trace for the component com.ibm.ws.webcontainer.*.
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, technotes, 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 IBM Support page.
IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see IBM Support page.
See AlsoTroubleshooting by component: What is not working?