IBM Support

PM30435: WHEN EXTENDED DOCUMENT ROOTIS ENABLED, FFDC IS GENERATED WITH JAVA.IO.FILENOTFOUNDEXCEPTION.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When Extended Document Root is enabled, customer is getting
    FFDC log with java.io.FileNotFoundException. Customer would like
    this to be suppressed.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server version    *
    *                  7.0 users.                                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: FFDC logs a FileNotFoundException       *
    *                      when Extended Document Root (EDR) is    *
    *                      enabled.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The JavaServer Pages (JSP) engine is told to search for a file
    within an application by another component when the server
    starts up.  When EDR is enabled, the JSP engine extends its
    file search into the EDR workspace and logs the FFDC if the
    file can not be found.
    
    A sample of the FFDC log:
    
    FFDC log:FFDC Exception:java.io.FileNotFoundException
    SourceId:com.ibm.ws.jsp.webcontainerext.JspExtensionContext.getR
    esourceAsStream ProbeId:93
    Reporter:com.ibm.ws.jsp.webcontainerext.JSPExtensionContext@bdd0
    bdd
    java.io.FileNotFoundException: /WEB-INF/portlet.xml
        at
    com.ibm.ws.webcontainer.util.ExtendedDocumentRootUtils.handleExt
    endedDocumentRoots(ExtendedDocumentRootUtils.java:172)
        at
    com.ibm.ws.jsp.webcontainerext.JSPExtensionContext.getRealPath(J
    SPExtensionContext.java:81)
        at
    com.ibm.ws.jsp.taglib.GlobalTagLibraryCache.getGlobalTagLibMapFo
    rWebApp(GlobalTagLibraryCache.java:399)
        at
    com.ibm.ws.jsp.webcontainerext.AbstractJSPExtensionProcessor.<in
    it>(AbstractJSPExtensionProcessor.java:195)
        at
    com.ibm.ws.jsp.webcontainerext.ws.WASJSPExtensionProcessor.<init
    >(WASJSPExtensionProcessor.java:76)
        at
    com.ibm.ws.jsp.webcontainerext.ws.WASJSPExtensionFactory.createP
    rocessor(WASJSPExtensionFactory.java:251)
        ....................
    
    This does not affect any functionality of the server or the
    application.
    

Problem conclusion

  • The JSP Container code was modified to suppress the FFDC until
    the JSP trace string is enabled.
    
    The fix for this APAR is currently targeted for inclusion in
    fixpack 7.0.0.17
    Please refer to the recommended updates page for delivery
    information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM30435

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-01-13

  • Closed date

    2011-02-11

  • Last modified date

    2011-02-11

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM30435

Modified date: 11 February 2011