Thank you for your fast response Yes, i realize that so many reloading in a production server is bad practice. This is due 'the not very ideal' environment and policy in my company. I'm doing it because I have different platform for development and production. My company using Linux Redhat as production server, while I'm using win 2000 for development (yes, they would be mad if I change my system into Linux!).
Everything start goes wrong when dealing with file path and library dependencies (JasperReport is throwing lot of error because of some library is deprecated in Redhat, etc). That's why I need so many reload on production server, debugging purpose, major pain it is. Anyway, thats not the concern. The interesting part is when I reload my application the memory is keep growing in a certain increment. Should I keep using IntrospectorCleanupListener from Spring? is it bad one? I'm sorry if my question is stupid. I'm still trying to learn the best one with Struts. I love it since the first look. ;) Best regards On Tue, 22 Mar 2005 22:38:05 -0500, James Mitchell <[EMAIL PROTECTED]> wrote: > Struts does not provide this sort of thing. > > In the environments that I typically work in, production releases are > handled by a release manager(s). When a new release goes out, the server is > usually brought down and the new build is pushed out, then brought back up. > This being done after normal working hours of course. > > I'd be interested to hear if you are using it successfully in a production > environment. I'd also be interested in how many times and why you need to > reload a production application. Using something like this during > development is a no-brainer, but I was just wondering. > > -- > James Mitchell > Software Engineer / Open Source Evangelist > EdgeTech, Inc. > 678.910.8017 > AIM: jmitchtx > > ----- Original Message ----- > From: "Yuniar Setiawan" <[EMAIL PROTECTED]> > To: <user@struts.apache.org> > Sent: Tuesday, March 22, 2005 9:47 PM > Subject: Struts webapp caused out of memory after some reload > > > Hi, > > I'm running a server (Apache Tomcat 5.0.28 with 512 MB RAM) which > > hosting two webapps, one using Spring and other using Struts. The > > problem is, after i reload the Struts webapp for about 15-20 times i'm > > getting out of memory error. This is not happend with the Spring > > webapp. > > > > After some search, i found that Spring has IntrospectorCleanupListener > > http://www.springframework.org/docs/api/org/springframework/web/util/IntrospectorCleanupListener.html > > which can handle this kind situation. > > > > A post about this is: > > http://issues.apache.org/bugzilla/show_bug.cgi?id=26135 > > > > The question is, doesn't struts have its own solving? or do i have to > > use Spring's IntrospectorCleanupListener so i won't get out of memory > > error again?? > > > > Thank you very much for the help. I'm still new with struts. And last > > night I dont have a decent sleep because of this problem ;) > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]