Upgrading to 5.1 is going to require a lot of effort since we have hacked LinkFactory, RequestSecurityManager, etc to get functionality that did not exist. But we'll certainly do it if it will solve the problem. It's just that we don't know whether we can allocate the resources to do it unless we know whether that's a potential solution to the problem.
----- Original Message ---- From: Thiago H. de Paula Figueiredo <thiag...@gmail.com> To: Tapestry users <users@tapestry.apache.org> Sent: Friday, September 11, 2009 12:17:38 PM Subject: Re: [T5.0.18] Out of Memory Error / Potential Leak (doesn't reduce after forced GC) Em Fri, 11 Sep 2009 12:47:23 -0300, Dave Greggory <davegregg...@yahoo.com> escreveu: > I have T5.0.18 running in Tomcat 5.5 with Java 1.5 32-bit -Xms2048m > -Xmx2048m -XX:PermSize=128m -XX:MaxPermSize=128m. Have you tried 5.1.0.5? --Thiago H. de Paula Figueiredo Independent Java consultant, developer, and instructor http://www.arsmachina.com.br/thiago --------------------------------------------------------------------- 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
