IBM Support

PM06063: PROVIDE A JSP ATTRIBUTE TO DISABLE CERTAIN NEW V7 FEATURES

Fixes are available

7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • JSPs that were compiling under V6.1 fail compilation on V7
    because their size exceeds the 64k byte limit.
    .
    New functionality introduced in the V7 JSP engine caused the
    compiled method output to be larger than it was previously, so
    JSPs that were pushing the limit before might now fail.
    This can be avoided by creating smaller JSPs and merging them
    using <jsp:include> statements.
    

Local fix

  • Create smaller JSPs and merge them during the request using
    <jsp:include> statements.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM WebSphere Application Server version    *
    *                  7.0 users of JavaServer Pages (JSP)         *
    ****************************************************************
    * PROBLEM DESCRIPTION: A JSP that exceeds 65535 byte limit     *
    *                      in the translated service method        *
    *                      fails to compile.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The resource injection feature shipped with WebSphere
    Application Server 7.0 introduced a new way of accessing
    resources in applications.  For migrating applications from
    previous releases, the resource injection can cause an already
    large JSP to exceed the 65535 byte limit in the translated
    service method; thus it fails to compile.
    
    An example of the error:
    SRVE0293E: The code of method _jspService(HttpServletRequest,
    HttpServletResponse) is exceeding the 65535 byte limit
    

Problem conclusion

  • The JSP Container code was modified to disable the resource
    injection during the translation with one of the following
    properties is set:
    
    A WebContainer custom property
    com.ibm.wsspi.jsp.disableResourceInjection = true can be set
    to affect all the deployed applications or a JSP attribute
    "disableResourceInjection" can be set in the ibm-web-ext.xmi
    file to affect only the application for which the property is
    set.
    
    Please refer to the following technote for instructions on
    enabling WebContainer custom properties:
    http://www.ibm.com/support/docview.wss?rss=180&uid=swg21284395
    
    APAR PM06063 requires changes to documentation.
    
    NOTE: Periodically, we refresh the documentation on our
    Web site, so the changes might have been made before you
    read this text. To access the latest on-line
    documentation, go to the product library page at:
    
    http://www.ibm.com/software/webservers/appserv/library
    
    The following changes to the WebSphere Application Server
    Version 7.0 Information Center will be made available in
    June, 2010.
    
    The following description of the
    com.ibm.wsspi.jsp.disableResourceInjection Web container
    custom property will be added to the "Web container
    custom properties" topic:
    
    Disabling resource injection during the JSP translation
    process
    
    The resource injection feature accesses resources in
    applications differently then it did in earlier versions
    of the product, and causes the compiled method output to
    be larger than it was previously. If you have large JSPs
    that in earlier releases pushed the 65535 byte limit in
    the translated service method, they might now exceed this
    limit, causing the compile to fail
    
    If you encounter this situation, you can either break a
    large JSP into smaller JSPs, and use <jsp:include>
    statements to combine them after they are compiled, or
    you can add the com.ibm.wsspi.jsp.disableResourceInjection
    custom property to your Web container settings to disable
    the resource injection function during the JSP translation
    process. When the com.ibm.wsspi.jsp.disableResourceInjection
    custom property is set to true, the resource injection
    function is disabled for all applications.
    
    If you only want to disable the resource injection function
    for specific applications, you can add the
    disableResourceInjection JSP attribute to the ibm-web-ext.xmi
    files for those specific applications.
    
    The default value for the
    com.ibm.wsspi.jsp.disableResourceInjection custom property
    is false.
    
    Name                                      Value
    com.ibm.wsspi.jsp.disableResourceInjection  true
    
    
    APAR PM06063 is currently targeted for inclusion in Service
    Level (Fix Pack) 7.0.0.11 of WebSphere Application Server V7.0.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM06063

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-01-26

  • Closed date

    2010-03-26

  • Last modified date

    2010-07-02

  • 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 FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R700 PSY UK57722

       UP10/06/17 P F006

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021