Yes, I think this is a known problem Markus. AFAIK, when you disable
caching Tapestry generates class on the fly every time you display a
page (allowing you to make changes to those classes / etc). Now... for
some strange reason those classes don't get unloaded from the Perm space
in Java, so it's just a matter of time before the server crashes down.
http://www.theserverside.com/news/thread.tss?thread_id=36743
Now... Tapestry is the only application I currently know it has this
problem (I wonder if this is a case of programmer ego saying "it's the
compiler's fault"). Increasing the PermGen space should buy you some
time (hours) before the problem shows up again.
These are my Tomcat settings (I have 1.2 Gb of RAM, of course):
-XX:MaxPermSize=128m -Xms512m -Xmx512m
-Dorg.apache.tapestry.disable-caching=true
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Markus Eberle wrote:
This all just extends the time until this error happens.
The only thing that really helps is enabling caching.
Cheers,
Markus
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
