Thiago, thanks for the info
I don't want to turn off topic but, what jvm would you recommend instead of oracle's? ps: note that while just class reloading OutOfMemoryError takes a while to appear, but when reloading the application context it really blowns fast (2 or 3 reloads as I said). So for me tap5's class reloading works like a charm. Nicolás.- On Thu, Mar 15, 2012 at 2:22 PM, Thiago H. de Paula Figueiredo < thiag...@gmail.com> wrote: > On Thu, 15 Mar 2012 13:13:32 -0300, Nicolas Barrera <nbarr...@gmail.com> > wrote: > > I 'm having an issue using mvn:jetty (which can reload the context by >> pressing enter on the console)... after I press enter (reload context) >> let's say 3 times an outofmemoryerror turns out... >> > > This is a combination of live class reloading and the Sun (Oracle) JVM. > Live class reloading creates lots of classes on the fly. These classes are > stored in what is called the permgen space. In the Sun JVM, the permgen > space doesn't grow when needed (fixed limit) and the default limit value is > quite small. If you run the Sun JVM with a larger pergmen space, this > problem doesn't go away, but takes way more time to happen. Or just use > another JVM. > > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, Ars Machina Tecnologia da Informação Ltda. > http://www.arsmachina.com.br >
