Re: Dispatcher attempts to write on the response after it has been commited

2014-03-17 Thread Lukasz Lenart
2014-03-18 7:01 GMT+01:00 Jose L Martinez-Avial : > Well, that's a good thing, but anyway I think the default dispatcher should > avoid this kind of error. The problem is (as far I can recall) that it's a Weblogic specific situation. I mean, Tomcat doesn't throw exception when user aborts opening

Re: Dispatcher attempts to write on the response after it has been commited

2014-03-17 Thread Jose L Martinez-Avial
Well, that's a good thing, but anyway I think the default dispatcher should avoid this kind of error. JL Sent via BlackBerry from T-Mobile -Original Message- From: Lukasz Lenart Date: Tue, 18 Mar 2014 06:50:18 To: Struts Users Mailing List Reply-To: "Struts Users Mailing List" Subject

Re: Dispatcher attempts to write on the response after it has been commited

2014-03-17 Thread Lukasz Lenart
As from 2.3.17 you will be able to write your own DispatcherErrorHandler https://issues.apache.org/jira/browse/WW-3887 https://cwiki.apache.org/confluence/display/WW/Dispatcher 2014-03-18 6:06 GMT+01:00 JOSE L MARTINEZ-AVIAL : > Hi, > I'm using Struts 2.3.16.1 with Weblogic 10.3. I recently not

Dispatcher attempts to write on the response after it has been commited

2014-03-17 Thread JOSE L MARTINEZ-AVIAL
Hi, I'm using Struts 2.3.16.1 with Weblogic 10.3. I recently noticed some errors on the server log: java.lang.IllegalStateException: Response already committed at weblogic.servlet.internal.ServletResponseImpl.objectIfCommitted(ServletResponseImpl.java:1553) at weblogic.servlet.in