You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Bryan Hansen (JIRA)" <de...@myfaces.apache.org> on 2006/08/03 15:26:14 UTC

[jira] Commented: (TOMAHAWK-579) java.lang.IllegalStateException: getOutputStream() has already been called for this response error using the RI 1.2_01 and Tomahawk 1.1.3

    [ http://issues.apache.org/jira/browse/TOMAHAWK-579?page=comments#action_12425518 ] 
            
Bryan Hansen commented on TOMAHAWK-579:
---------------------------------------

I have read that this was solved in the past, but this is still occuring with the RI and Tomahawk 1.1.3.

> java.lang.IllegalStateException: getOutputStream() has already been called for this response error using the RI 1.2_01 and Tomahawk 1.1.3
> -----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TOMAHAWK-579
>                 URL: http://issues.apache.org/jira/browse/TOMAHAWK-579
>             Project: MyFaces Tomahawk
>          Issue Type: Bug
>          Components: ExtensionsFilter
>    Affects Versions: 1.1.3
>         Environment: OSX 10.4 Tomcat 5.5.17 JVM 5
>            Reporter: Bryan Hansen
>
> If I have the ExtensionsFilter configured in my web.xml it throws an error whenever a page is not found saying that the response is already committed instead of just displaying the 404 error page that I have created. 
> java.lang.IllegalStateException: getOutputStream() has already been called for this response
> 	at org.apache.catalina.connector.Response.getWriter(Response.java:599)
> 	at org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:195)
> 	at org.apache.jasper.runtime.JspWriterImpl.initOut(JspWriterImpl.java:124)
> 	at org.apache.jasper.runtime.JspWriterImpl.flushBuffer(JspWriterImpl.java:117)
> 	at org.apache.jasper.runtime.PageContextImpl.release(PageContextImpl.java:191)
> 	at org.apache.jasper.runtime.JspFactoryImpl.internalReleasePageContext(JspFactoryImpl.java:115)
> 	at org.apache.jasper.runtime.JspFactoryImpl.releasePageContext(JspFactoryImpl.java:75)
> 	at org.apache.jsp.errors._404_jsp._jspService(_404_jsp.java:67)
> If I comment out the ExtensionsFilter it works fine and displays the 404 splash page from my application as it should. Here is the snippet from my web.xml:
>       <filter>
> 		<filter-name>MyFacesExtensionsFilter</filter-name>
> 		<filter-class>org.apache.myfaces.component.html.util.ExtensionsFilter</filter-class>
> 		<init-param>
> 			<description>Set the size limit for uploaded files.
> 				Format: 10 - 10 bytes
> 				10k - 10 KB
> 				10m - 10 MB
> 				1g - 1 GB
> 			</description>
> 			<param-name>uploadMaxFileSize</param-name>
> 			<param-value>100m</param-value>
> 		</init-param>
> 		<init-param>
> 			<description>Set the threshold size - files
> 				below this limit are stored in memory, files above
> 				this limit are stored on disk.
> 				
> 				Format: 10 - 10 bytes
> 				10k - 10 KB
> 				10m - 10 MB
> 				1g - 1 GB
> 			</description>
> 			<param-name>uploadThresholdSize</param-name>
> 			<param-value>100k</param-value>
> 		</init-param>
> 	</filter> 
> 	<filter-mapping>
> 		<filter-name>MyFacesExtensionsFilter</filter-name>
> 		<url-pattern>*.jsf</url-pattern>
> 	</filter-mapping> 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira