ahh it's a closed connection ... which version of Pax-Web are you using? And did you check if that bug is already been fixed with Pax-Web?
regards, Achim 2016-03-18 11:54 GMT+01:00 Benson Margulies <ben...@basistech.com>: > > On Fri, Mar 18, 2016 at 6:46 AM, Achim Nierbeck <bcanh...@googlemail.com> > wrote: > >> >> http://ops4j.github.io/pax/web/4.2.x/index.html#_advanced_jetty_configuration > > > For my particular application, zero java code is actually preferable. > Anyhow, why would configuring it that way prevent Jetty from try to write > to closed connections? > > -- Apache Member Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
