Another way is to check if the application is getting reloaded while you are running - hopefully easily observable in the log. Each reload will cause more things to get generated and eat up perm gen space. There is some configuration you can also use to either increase your jvm permgens space or limit how classes get reloaded (eg due to a changed ts on disk).
Hope it helps some. /P CG-6 wrote: > > Hi all, I have used T5 to write an application , it works fine , > however, after using for a while , it will run into problem of > PermGem out of space (on Server) > > After doing some googling , i get to know that it may due to program > memory leak problem. > > I would like to trace in to code to but I have no idea how can do to > narrow down to the problematic code. > > Hopefully some experience Java/T5 developer can give me some guidance > in this case. > > Thanks .. > > CG > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > > -- View this message in context: http://www.nabble.com/-T5--How-to-tackle-memory-leak-problem-%28Perm-Gem-Out-of-Space%29-tp22510707p22524942.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
