IBM Support

PM12657: WITH JSF 1.2 ON V7.0, RENDERING IS DONE AFTER FORWARD WHICH COMMITS THE RESPONSE AND RESULTS IN ILLEGALSTATEEXCEPTION

Fixes are available

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

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • An application exception which occurs after the JSF view is
    built during rendering of the response can result in an
    IllegalStateException being thrown because the response is
    already committed.
    

Local fix

  • a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Version 7.0 and JavaServer Faces     *
    *                  (JSF).                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: If an exception occurs after the JSF    *
    *                      view is built a                         *
    *                      java.lang.IllegalStateException can     *
    *                      occur.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After the JSF view is built during the render response phase,
    the wrapped response is committed.  If an exception occurs
    then a java.lang.IllegalStateException can occur because the
    response was committed.
    For example, an application can use the following JSF Widget
    Library (JWL) tag to perform some actions prior to rendering
    the view:
    
    <hx:scriptCollector id="mySC1"
    preRender="#{myBean.doMyPreRenderAction}">
    
    If an exception occurs while processing the preRender
    attribute and an error page is called in the application, an
    IllegalStateException can occur because of the committed
    response.  This will result in the error page not being
    displayed.
    Trace entry examples of the response committed are:
    com.ibm.ws.webcontainer.srt.SRTServletResponse isCommitted
    headersWritten=true
    W com.ibm.ws.webcontainer.srt.SRTServletResponse setStatus
    WARNING: Cannot set status. Response already committed.
    
    Also, if the error page attempted to get a writer, the
    following exception can be logged:
    
    java.lang.IllegalStateException: SRVE0209E: Writer already
    obtained
    at
    com.ibm.ws.webcontainer.srt.SRTServletResponse.getOutputStream(S
    RTServletResponse.java:698)
    at
    com.example.MyErrorPageServlet.doIt(MyErrorPageServlet.java:40)
    at
    com.example.MyErrorPageServlet.doGet(MyErrorPageServlet.java:27)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:718)
    

Problem conclusion

  • The JSF code was modified to not commit the response after
    building the view.  To enable this behavior, the following
    context parameter must be set to true in the application's
    web.xml file.
    com.ibm.ws.jsf.disableCommitDuringBuildView
    
    For example:
    
    <context-param>
    <param-name>com.ibm.ws.jsf.disableCommitDuringBuildView</param-n
    ame>
    <param-value>true</param-value>
    </context-param>
    
    Valid values for the context parameter are "true" and "false".
    The default value is "false".
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.13.  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

    PM12657

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-20

  • Closed date

    2010-04-28

  • Last modified date

    2010-04-28

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP

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

Document Information

Modified date:
25 October 2021