Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <1062450727.1205339206350.JavaMail.jira@brutus>
Date: Wed, 12 Mar 2008 09:26:46 -0700 (PDT)
From: "Grzegorz Kossakowski (JIRA)" <jira@apache.org>
To: dev@cocoon.apache.org
Subject: [jira] Commented: (COCOON-2150) Error on resetting response
In-Reply-To: <32690290.1196053723048.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/COCOON-2150?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D125=
77905#action_12577905 ]=20

Grzegorz Kossakowski commented on COCOON-2150:
----------------------------------------------

@Joerg: See my response to Vadim who raised exactly the same concerns like =
some of you: http://article.gmane.org/gmane.text.xml.cocoon.devel/77006

I'll buffer only response if the response code has been set to 404 and will=
 set sane default (like 1MB) of a buffer to avoid OOMEs.  If you are genera=
ting more than 1MB response with 404 code then it's definitively a problem =
with your application and FATAL ERROR will be logged.

Does it sound fine?

> Error on resetting response
> ---------------------------
>
>                 Key: COCOON-2150
>                 URL: https://issues.apache.org/jira/browse/COCOON-2150
>             Project: Cocoon
>          Issue Type: Bug
>          Components: - Servlet service framework
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: J=C3=B6rg Heinicke
>            Assignee: Grzegorz Kossakowski
>             Fix For: 2.2-dev (Current SVN)
>
>
> This is the exception shown on the console:
> java.lang.IllegalStateException: Committed
>         at org.mortbay.jetty.Response.resetBuffer(Response.java:855)
>         at org.mortbay.jetty.Response.reset(Response.java:834)
>         at javax.servlet.ServletResponseWrapper.reset(ServletResponseWrap=
per.java:182)
>         at org.apache.cocoon.servletservice.ServletServiceContext$PathDis=
patcher.forward(ServletServiceContext.java:576)
>         at org.apache.cocoon.servletservice.ServletServiceContext$PathDis=
patcher.forward(ServletServiceContext.java:545)
>         at org.apache.cocoon.servletservice.spring.ServletFactoryBean$Ser=
viceInterceptor.invoke(ServletFactoryBean.java:230)
>         at org.springframework.aop.framework.ReflectiveMethodInvocation.p=
roceed(ReflectiveMethodInvocation.java:171)
>         at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(Jd=
kDynamicAopProxy.java:204)
>         at $Proxy2.service(Unknown Source)
>         at org.apache.cocoon.servletservice.DispatcherServlet.service(Dis=
patcherServlet.java:102)
>         at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>         at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.j=
ava:459)
> It seems to be thrown whenever the response object is reseted after the a=
ctual response has been sent by the sitemap error handler. In this case res=
et is no longer possible since the response has already been committed as s=
tated in the error message.

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.