Re: [jetty-user] EOF exception after upgrade to Jetty 7?

The way I understand this, it looks like expected behaviour and not a bug  
at all:
1. request comes in
2. your code begins to generate a response
3. the client hits "back" or "stop" and closes the TCP connection before  
the transfer is complete
4. if your xml transformer tries to write more data to the OutputStream,  
an exception is thrown since the data has nowhere to go



On Tue, 30 Nov 2010 15:19:43 +0100, <[email protected]> wrote:

> Martin Strand wrote:
>> I've seen this myself (with Jetty 6) in a scenario similar to yours.
>> We could reproduce it manually by hitting "stop" or "back" fast enough.  
>> Perhaps you need to write a test to make it appear, I'm pretty sure you  
>> would see the exception if you could have the client disconnect while  
>> the transformation is running.
>>  We did what you suggest, unwrapped the thrown exception and ignored it  
>> if there was an underlying EOFException or SocketException.
>
> Okay, thanks for this. Clicking a link and then trying to click another
> link doesn't do it, but I'll try "stop" and "back" as well.
>
> Is this something that indicates an underlying problem with Jetty that  
> perhaps needs me to submit a bug report? (Difficult to produce something
> that demonstrates it when I don't really understand it, though!)
>
> Many thanks for your help,

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email