Dear Howard, Thanks for your answer. I use 5.1.0.5. I think I found it out only by inspecting the exception msg.
I was creating a large table and was creating two large java objects out of hibernate calls for every row I rendered (not creating the table data in someting like setupRender) but during rendering process of table. I optimized it by using hibernate native sql nd not creating so much java objects now. Thank you for your help. Oliver -- View this message in context: http://tapestry-users.832.n2.nabble.com/Tapestry-Application-produces-GC-overhead-limit-exceeded-tp6651594p6663722.html Sent from the Tapestry Users 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
