FWIW, I just tested in Tomcat and it works fine. I'm going to assume it is something with the Maven Jetty plugin and not a Tapestry 5.4 issue.
Thanks! mrg On Fri, Aug 29, 2014 at 8:40 AM, Michael Gentry <mgen...@masslight.net> wrote: > H Lance, > > There were no exceptions and I was using VisualVM to monitor the > heap/GCs/etc and there was plenty of memory available, even when processing > both threads. (About 150-200MB used out of 1GB allocated.) > > mrg > > > > On Fri, Aug 29, 2014 at 3:17 AM, Lance Java <lance.j...@googlemail.com> > wrote: > >> Put a >> try {...} catch (Throwable t) >> Around the processing of this large file. Perhaps maven isn't giving jetty >> enough memory and it's throwing OutOfMemoryError or something? >> > >