(solved ?) tapestry 4.1.6 and pergmen question

I write this so it goes on web archives and maybe (even though is not probabile) one day someone will find it useful. The solution is to avoid this https://wiki.apache.org/tapestry/EasyBrowserRedirection never raise that exception. Instead use PageRedirectException in case you want to pass

Re: tapestry 4.1.6 and pergmen question

It seems I have found the glitch. Following this suggestion https://wiki.apache.org/tapestry/EasyBrowserRedirection I had implented redirection in a pageBeginRender method (I'm talking about T 4.1.6, sorry about that) Now it seems that when the excpetion is raised PermGen occupation is

Re: tapestry 4.1.6 and pergmen question

Thanks Kalle, I know the links you suggest, but I was exlcuding my code because it has not been chaned much from the one on the old server Anyway I will keep on investigating, I have no other choice. Thanks anyway Il 07/04/2016 17:37, Kalle Korhonen ha scritto: > On Thu, Apr 7, 2016 at

Re: tapestry 4.1.6 and pergmen question

Thanks Kalle, I know the links you suggest, but I was exlcuding my code because it has not been chaned much from the one on the old server Anyway I will keep on investigating, I have no other choice. Thanks anyway Il 07/04/2016 17:37, Kalle Korhonen ha scritto: > On Thu, Apr 7, 2016 at

Re: tapestry 4.1.6 and pergmen question

On Thu, Apr 7, 2016 at 12:33 AM, Ivano Luberti wrote: > Kalle, Chris, thanks for your answers. > Unfortunately the problem is not related to webapp reloading even > restarting the Tomcat service leads to out of PermGen in a few days, > PermGen itself is quite large and I

Re: tapestry 4.1.6 and pergmen question

Kalle, Chris, thanks for your answers. Unfortunately the problem is not related to webapp reloading even restarting the Tomcat service leads to out of PermGen in a few days, PermGen itself is quite large and I already use UseConcMarkSweepGC. Down here you can read the java settings :

Re: tapestry 4.1.6 and pergmen question

You could try "CMSClassUnloadingEnabled" to see if that helps -- Chris On Wed, Apr 6, 2016 at 11:24 PM, Kalle Korhonen wrote: > If you run out of permgen space very quickly, then it's indicative that the > allocated permgen space is simply too small. Perhaps the

Re: tapestry 4.1.6 and pergmen question

If you run out of permgen space very quickly, then it's indicative that the allocated permgen space is simply too small. Perhaps the new version of Tomcat requires more of it for itself, leaving less for your application. Is the webapp restarted at times? If so, that can easily cause permgen space

Re: tapestry 4.1.6 and pergmen question

Hey Tony, if you don't mind, can you send me all the configuration options of Java and Tomcat you are using? So tomcat6.conf and server.xml files? No one else on the list can share its thoughts? Il 05/04/2016 23:03, Ivano Luberti ha scritto: > Hi Tony thanks for the quick answer: > > Il

Re: tapestry 4.1.6 and pergmen question

Hi Tony thanks for the quick answer: Il 05/04/2016 21:50, Tony Nelson ha scritto: > I still have a Tapestry 4 app running with Tomcat 6.0.41, and it runs well > enough with: > > -XX:MaxPermSize=1024m with that setting it fails but... > > I also have > > -Xmx12g -Xms4g -XX:+UsseConcMarkSweepGC

RE: tapestry 4.1.6 and pergmen question

uberti [mailto:lube...@archicoop.it] > Sent: Tuesday, April 05, 2016 3:44 PM > To: Tapestry users > Subject: tapestry 4.1.6 and pergmen question > > I know I know, please don't shoot the pianist. > I have an old application written using Tapestry 4.1.6 and I can't get the > budg

tapestry 4.1.6 and pergmen question

I know I know, please don't shoot the pianist. I have an old application written using Tapestry 4.1.6 and I can't get the budget to rewrite in Tapestry 5. (BTW I have already and succesfully used Tapestry 5, so I know what I'm loosing here) The application run without issues for years on a