I've now got a sort of repro of this mess in our system. On the server side, the log gets:
2012-06-13 10:52:14,783 [qtp1782440671-574] WARN org.eclipse.jetty.io.nio - java.io.EOFException No backtrace, no other explanation. On the client side, we get a 'socket closed'. On Tue, Jun 12, 2012 at 9:24 AM, Gary Gregory <[email protected]> wrote: > We use an embedded Jetty in our application server that we configure through > a standard jetty.xml file. > > Gary > > -----Original Message----- > From: Benson Margulies [mailto:[email protected]] > Sent: Tuesday, June 12, 2012 8:44 AM > To: [email protected] > Subject: Re: Anyone use embedded jetty in production out there? > > Yup, "in start! 2147483647." > > On Mon, Jun 11, 2012 at 4:15 PM, Daniel Kulp <[email protected]> wrote: >> SelectChannelConnector con = new SelectChannelConnector() { >> public void doStart() throws Exception { >> System.out.println("in start! " + getMaxIdleTime()); >> super.doStart(); >> } >> }
