I've seen this too when using the early jetty-runner RCs after an OoM exception. However, I have not seen it with the latest RC6 - so I think it's an issue with how Jetty behaves when you run out of heap space.
Kalle On Wed, Oct 7, 2009 at 1:58 PM, Michael Gentry <mgen...@masslight.net> wrote: > I finally saw this yesterday (with Jetty during development/live class > loading). And not too long after I saw it I ran out of heap memory. > I had been running the app a while and just restarted it. > > > On Wed, Oct 7, 2009 at 4:32 PM, Sergey Didenko <sergey.dide...@gmail.com> > wrote: >> I saw this a few times. It was always after a live reloading. >> >> May be after I saved one new class/tml file and before I saved another >> dependent changes. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
