Putting up the maximum memory Xmx does help as it gives it more memory to use up, but only delays the inevitable :)
Is this a struts issue? or does it happen with all tomcat apps?
It happens with every servlet container I've used. My understanding is that to redeploy a webapp, app servers generally discard the classloader they have been using and make a new one. For various reasons, this can leave orphan objects which are never garbage collected. If enough of these accumulate, you run out of memory.
Admittedly, I use Struts in all these cases, you might argue that it's a Struts issue, since that's the common feature, but I can't think of anyways Struts is being particularly careless in a way that would aggravate this problem.
I may have a completely wrong understanding of the problem too, but this is how we explain it to ourselves around here!
Joe
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining."
-- Jef Raskin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
