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

I have a web app which generates XML which is then transformed by XSLT
into the final HTML for the page. This has worked fine for several
years.

Having recently upgraded to Jetty 7 from Jetty 5, I'm suddenly getting
errors like this from my XSLT filter:

XML transformation error: org.eclipse.jetty.io.RuntimeIOException:
   org.eclipse.jetty.io.EofException

or this:

XML transformation error:
   com.sun.org.apache.xalan.internal.xsltc.TransletException:
   com.sun.org.apache.xalan.internal.xsltc.TransletException:
   org.eclipse.jetty.io.RuntimeIOException:
   org.eclipse.jetty.io.EofException

This is only happening occasionally, not consistently. When I print out
the XML that the transformer is complaining about, it looks complete.

My suspicion is that it happens when users load a page and then change
their minds and go elsewhere before the output has all been sent to the
browser. However, I haven't managed to reproduce this yet. Obviously I
could catch this exception (not easy, since it's usually fairly deeply
wrapped by Xalan) and ignore it, but I'd prefer to do it the "right"
way by eliminating the cause of the error.

Is there something new in Jetty 7 that I need to know about?

TIA,

----------------------------------------------------------------------
  John English              | mailto:[email protected]
  Senior Lecturer           | http://www.it.bton.ac.uk/staff/je
  School of Computing & MIS | "Those who don't know their history
  University of Brighton    |  are condemned to relive it" (Santayana)
----------------------------------------------------------------------

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

    http://xircles.codehaus.org/manage_email