Exactly, what I was saying is that if you get OOMEs only after reloading the application several times is most likely to be related with some tomcat issues. That doesn't mean that you won't get OOME errors in production, it does mean that in production wou won't get the OOME errors caused by reloading applications in tomcat.
In all applications I've been involved we did some jvm adjustements to find out the right memory heap size, and it take a while to figure out the proper parameters. summing up... in most cases OOME errors in production are due to: - incorrect jvm adjustments: increase memory heap, etc. - coding erros: memory leaks, etc. I'm not trying to be an evangelist, just want to share my experiencies in a problem that developers should spend more time on, developing an application is not just coding but also tunning the application server and the server itself. --- Bryan Lewis <[EMAIL PROTECTED]> wrote: > I think the reason most people don't worry about it > in production is that > they don't do reloading or hot redeployment in > production. Not much anyway. > Development and testing are done on other servers > and the production servers > are updated much less frequently. Or they're > running in a clustered > configuration where the app server can be restarted > without interupting the > users. > > > ----- Original Message ----- > From: "Leonardo Quijano Vincenzi" > <[EMAIL PROTECTED]> > To: "Tapestry users" > <[email protected]> > Sent: Thursday, October 27, 2005 12:00 PM > Subject: Re: AW: Memory / Caching Issues > > > > ausias vives wrote: > > > It's a known issue that reloading an application > in > > > tomcat causes, in the short or mid term, OOME > errors. > > > In your case I woudn't bother so much, and I'd > focuse > > > in checking that the application runs correctly > > > without using the reload facility. It's very > useful to > > > write some load tests and using httpunit or > webunit. > > > > > I'm wondering why this problem isn't a critical > issue that has all > > commiters extremely worried. OOMEs - well, at > least IMO!! - are like > > threading errors - race conditions, etc.. they are > something that should > > get everyone worried. I'd expect my applications > to fail in a consistent > > way, not when 'heap runs out'. > > > > Of course, I understand it's more worrisome if it > happens in production > > environments rather than only in development. But > my point is that if it > > happens in development, can you guarantee it won't > happen in production? > > > > -- > > Ing. Leonardo Quijano Vincenzi > > Director Técnico > > DTQ Software > > > > > > > > > --------------------------------------------------------------------- > > 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 help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
