Resolving The Problem
Servlet engine and web container specific MustGather information:
If possible, provide a simple test case that has no external dependencies. If a test case cannot be provided, collect the following data.
- Run genHistoryReport.bat or genHistoryReport.sh, which is located in the following directory:
- Stop the web server and delete all Web server logs and the http_plugin.log file on the web server system.
- If you suspect that the problem might be related to the WebSphere Application Server plug-in, or to the web server itself, enable a full plug-in trace. To perform a plug-in trace, see the Plug-in MustGather documents.
- Start the web server.
- Important: Synchronize clocks on all web servers and WebSphere Application Server systems.
- Enable and collect Application Server traces with the following trace string:
Note: There should not be any spaces or '.' between webcontainer and '*' for the trace strings shown.
For Remote Request Dispatcher issues, append this string as well:
For Async Request Dispatcher issues, append this string as well:
Make sure to increase the maximum trace file size to 100MB and increase the maximum number of the historical log files to 10.
7. Take backup and delete all Application Server logs:
The log files are located in the following directory:
Note: If you configured to write Application Server log files into a different location, then clear them accordingly.
2. Add the following <logging> element:
<logging traceSpecification="com.ibm.ws.webcontainer*=all:com.ibm.wsspi.webcontainer*=all:HTTPChannel=all:GenericBNF=all:HTTPDispatcher=all" traceFileName="trace.log" maxFileSize="100" maxFiles="10" traceFormat="BASIC" />
Note: When using Jakarta EE 10 feature or servlet-6.0 feature with Liberty use below <logging> element
<logging traceSpecification="io.openliberty.webcontainer*=all:com.ibm.ws.webcontainer*=all:com.ibm.wsspi.webcontainer*=all:HTTPChannel=all:GenericBNF=all:HTTPDispatcher=all" traceFileName="trace.log" maxFileSize="100" maxFiles="10" traceFormat="BASIC" />3. Clear and backup old log files within <LIBERTY_HOME>/usr/servers/<server name>/logs directory
4. Stop the application server then start the server with the following parameter added
server start <SERVER_NAME> --clean
5. Re-create the issue.
6. Run the following command from the bin directory:
server dump <SERVER_NAME>
(this creates a .zip file in the /usr/servers/<SERVER_NAME>/ directory)
When the problem is re-created, collect the following data:
- Capture a browser screen displaying the error with friendly HTTP Errors disabled. Press <Alt>+<PrtSc> to capture the current browser window into the clipboard. Paste that into a file.
- Collect the following documents and information:
- Were clocks synchronized?
- The Application Server logs:
- FFDC logs with the current date from the following directory:
- The server.xml file that is located in the directory:
- The http_plugin.log file.
- The plugin-cfg.xml file.
- The web server configuration files, such as httpd.conf for IBM HTTP Server.
- The web server logs, such as access and error logs for IBM HTTP Server.
- Screen capture.
- The historyReport.html file from running genHistoryReport.bat or genHistoryReport.sh.
- Run collector.sh/collector.bat tool from install_root/bin. Follow the instructions to run the collector tool and provide the hostname -ND-WASenv.jar or hostname -Base -WASenv.jar file.
- .zip file in the /usr/servers/<SERVER_NAME/ directory that are created by the server dump.
For a listing of all technotes, downloads, and educational materials specific to the servlet engine and web container components, search the WebSphere Application Server support site.
Was this topic helpful?
19 January 2023