We have a similar problem with WebLogic 8.1 SP2...I was told by an associate that there is a 1.4.2_02 bug related class loading that might associated with the OutOfMemory.
-----Original Message----- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Thursday, May 13, 2004 1:52 PM To: Struts Users Mailing List Subject: RE: java.lang.OutOfMemoryError after server app start/stop cycling At 6:07 PM +0100 5/13/04, Daniel Perry wrote: >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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
