|
From: Greg W. <gr...@we...> - 2007-09-03 09:27:37
|
Johannes, this exception is thrown when a response stream is blocked for more that maxIdleTimeMs You should be able to reproduce it by having a client that starts reading a large image and then is blocked (ie suspened) for 30 seconds or so (depends on your config). Of course this could be your network rather than your client getting blocked.... or it could be a bug in Jetty detecting this condition when it should not :-) but you will need to provide more info before I suspect a bug (like it takes less than the timeout to produce this exception). cheers Johannes Zillmann wrote: > Hi jetty community, > > we have problems with following exception: > > org.mortbay.jetty.EofException: timeout > at org.mortbay.jetty.AbstractGenerator$Output.blockForOutput(AbstractGenerator.java:543) > at org.mortbay.jetty.AbstractGenerator$Output.flush(AbstractGenerator.java:567) > at org.mortbay.jetty.HttpConnection$Output.flush(HttpConnection.java:907) > at org.mortbay.jetty.AbstractGenerator$Output.write(AbstractGenerator.java:628) > at org.mortbay.jetty.AbstractGenerator$Output.write(AbstractGenerator.java:575) > at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105) > > while writing resource like jpgs to the response outputstream. > This happens every now and then in a production system but we can not reproduce this. > Does this happen if a client cancel a connection prematurely ? > > regards > Johannes > > PS: thanks for that great product ! > > > > > -- Greg Wilkins<gr...@we...> US: +1 3104915462 http://www.webtide.com UK: +44(0)2079932589 AU: +61(0)417786631 |