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]
