In my experience Tomcat eats memory when I do hot deployments regardless
of framework. So after 10-20 of them I usually need to start/stop Tomcat.
Ryan Phelan wrote:
Thanks for the quick Response!, Yes I'm well aware of the gc capabilites
of Java. (It was a nice refresher though :)... Anyway, while hunting for
such *leaks*, I need to target (or eliminate) Tapestry as the cause of
my OutOfMemoryErrors. Seems to work fine when disable-caching is set to
false, but when it is true, then I get OutOfMemoryErrors. Anyone else
run into this problem? Is it a common and known thing in the tapestry
world? Does Tapestry expect you to make a few changes, shutdown the
server, and then go at it again, when writing/debugging a web
application based on tapestry (when disable-caching = true, that is) ?
Thanks again! :)
-
--
Thanks,
Konstantin Ignatyev
http://www.kgionline.com
PS: If this is a typical day on planet earth, humans will add fifteen million
tons of carbon to the atmosphere, destroy 115 square miles of tropical
rainforest, create seventy-two miles of desert, eliminate between forty to one
hundred species, erode seventy-one million tons of topsoil, add 2.700 tons of
CFCs to the stratosphere, and increase their population by 263.000
Bowers, C.A. The Culture of Denial:
Why the Environmental Movement Needs a Strategy for Reforming Universities and Public Schools.
New York: State University of New York Press, 1997: (4) (5) (p.206)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
