You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@click.apache.org by "florin.g" <fl...@bytenotes.com> on 2009/06/01 03:21:16 UTC

Re: This output stream has already been closed?

Bob,

I suspect a change on my side that results in this. I don't know what
though. 

Click: click-2.0.1-incubating
Jetty: jetty-7.0.0.pre3

This jetty instance has been running for months with no incident. I noticed
this issue about 2 weeks ago. Would a dir of /lib/ be useful?





sabob wrote:
> 
> Also which version of Click is this?
> 
> 
> Bob Schellink wrote:
>> Hi Florin,
>> 
>> florin.g wrote:
>>>
>>> I thought it might be a character encoding mismatch yet the files work 
>>> fine
>>> on one machine (weindows/dev) yet this error appears in production 
>>> (centos). 
>> 
>> 
>> The GZip compression is only active in production modes which explains 
>> why you're not seeing this in dev.
>> 
>> 
>>> [error] handleException: java.io.IOException: This output stream has 
>>> already
>>> been closed
>>>         at
>>> org.apache.click.extras.filter.CompressionResponseStream.close(CompressionResponseStream.java:121) 
>>>
>> 
>> 
>> I'll have a look. Which version of Jetty are you using? Are you seeing 
>> this exception for every request or is it only for specific pages?
>> 
>> My feeling is that CompressionResponseStream should simply return if it 
>> is already close instead of throwing the exception.
>> 
>> kind regards
>> 
>> bob
>> 
> 
> 
> 

-- 
View this message in context: http://n2.nabble.com/This-output-stream-has-already-been-closed--tp3002771p3004067.html
Sent from the click-user mailing list archive at Nabble.com.


Re: This output stream has already been closed?

Posted by Bob Schellink <sa...@gmail.com>.
florin.g wrote:
> 
> I suspect a change on my side that results in this. I don't know what
> though. 


The error seems to occur when you do a forward from your Page.


> 
> Click: click-2.0.1-incubating
> Jetty: jetty-7.0.0.pre3


I'll have a look with this setup if I can produce the error. Have you 
tried a later version of Jetty to see if the problem persist?

You could also change CompressionResponseStream.close as follows and 
rebuild Click:

   public void close() throws IOException {
     if (closed) {
       return;
     }

     ...
   }

Perhaps do the same with the flush() method as that also throws the 
same exception. Let us know if that resolves the issue or if things 
break :)

kind regards

bob