myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dora Rajappan (JIRA)" <>
Subject [jira] [Commented] (MYFACES-4125) Response committed too early due to flush from StateWriter
Date Fri, 21 Jul 2017 10:31:00 GMT


Dora Rajappan commented on MYFACES-4125:

True in myfaces 2.2  drive request is not going to the error page and logs got in console
given below.
java.lang.RuntimeException: after Render Response.
--------------------- Resonse commited = true.
Trying to resolve. Pluto3/,myfaces 2.2 StateWrite app is deployed and simulated this bug.
Pluto3 lib requires commons-beanutils-1.9.2, commons-collections-3.2.2, commons-digester-2.1,commons-logging-1.1.1
in its lib to deploy StateWriter with myfaces 2.2 jars.

> Response committed too early due to flush from StateWriter
> ----------------------------------------------------------
>                 Key: MYFACES-4125
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 2.2.12
>            Reporter: Eduardo Breijo
>         Attachments: server.log, StateWriter.war
> We've found a problem where it seems that MyFaces is flushing output too early in the
RENDER_RESPONSE PHASE. As a result the response is committed before we have a chance to handle
an error in that phase. 
> This is because the renderView method from FaceletViewDeclarationLanguage calls writer.endDocument()
which ends up calling the flush() method from StateWriter. This commit behavior is different
between 2.0 and 2.2.  It looks like a flush() was empty on 2.0, and now a call was added,
which causes the issue we are seeing.
> Here's a sample app:
> 1) Drive a request: localhost:9080/StateWriter/index.xhtml
> 2) You should be able to see in the logs that response was committed, so redirect to
error.xhtml cannot be performed.

This message was sent by Atlassian JIRA

View raw message