IBM Support

MustGather: JavaServer Faces (JSF) problems

Technote (troubleshooting)


Problem(Abstract)

Collecting data for problems with JavaServer Faces (JSF) in the WebSphere Application Server. Gathering this information before calling IBM® support will help familiarize you with the troubleshooting process and save you time.

Resolving the problem

If you have already contacted support, continue on to the component-specific MustGather information. Otherwise, click: MustGather: Read first for WebSphere Application Server.

For most of the JSF related problems, a simple testcase will speed resolution. Ensure that the testcase does not have any external dependencies and is easily re-creatable. If you cannot provide a simple testcase, then follow the instructions below.

Instructions for setting up the trace:

  1. In the WebSphere Application Server administrative console, expand the Troubleshooting section and click Logs and Trace.

  2. Click the link for your server.

  3. Click Diagnostic Trace.

  4. Make sure Enable Log is checked, Maximum File Size as 100 MB, Historical Files as 10, and specify a File Name. You might have to select different values for Maximum File Size and Historical Files as per the frequency of the problem or as suggested by support team.

  5. Click OK.

  6. Click on Change Log Level Details.

  7. In Trace Specification, enter the following string:
    • For V8 and V7 using Sun RI

      *=info:com.ibm.ws.jsf*=all:com.sun.faces*=all:com.ibm.ws.webcontainer*=all:com.ibm.ws.jsp=all

    • For V8 and V7 using MyFaces implementation

      *=info:com.ibm.ws.jsf*=all:org.apache.myfaces*=all:com.ibm.ws.webcontainer*=all:com.ibm.ws.jsp=all

    • For V6.x using Sun RI

      *=info:com.ibm.ws.jsf=all:com.ibm.ws.webcontainer.*=all:com.ibm.ws.jsp=all

  8. Click apply and save your configuration.

  9. Stop the Application Server.

  10. Clear all SystemOut.log and SystemErr.log logs for the Application Server.

  11. Start the Application Server.

  12. Recreate the error condition and document the steps taken.

  13. Collect the following information:
    • A brief description of what JSF implementation you are using and how it is configured.

    • Trace file from the diagnostic trace.

    • All files in the following directory:

      profile_root/logs/server_name

      If you have configured the Application Server to write the logs into a different location then, send them accordingly.

    • All files in the following directory:

      profile_root/logs/ffdc

    • The server.xml file located in the following directory:

      profile_root/config/cells/cell_name/nodes/node_name/servers/server_name

    • The faces-config.xml and web.xml files located in web-inf folder of the failing WAR file.

    • The failing .jsf file and any other dependent files.

    • The historyReport.html file generated by running the tool genHistoryReport.bat or genHistoryReport.sh located in the following directory:

      install_root/bin

      The historyreport.html file is generated in the working directory from where the genHistoryReport tool is being run.

  14. Follow instructions to send diagnostic information to IBM support.

For a listing of all technotes, downloads, and educational materials specific to the JSF component, search the WebSphere Application Server support site.

Related information
Submitting information to IBM Support
Steps to getting support
MustGather: Readme First
Troubleshooting guide
Recording your screen to share with IBM Support

Cross reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK

Document information

More support for: WebSphere Application Server
Servlet Engine/Web Container

Software version: 6.0, 6.1, 7.0, 8.0, 8.5

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Software edition: Base, Express, Network Deployment

Reference #: 1198110

Modified date: 29 August 2011


Translate this page: