Re: [Springframework-developer] CachedIntrospectionResults

[Seth L. <set...@gm...>]

This was discussed a few months ago:

http://thread.gmane.org/gmane.comp.java.springframework.devel/4546

The consensus at that time was it's not a Spring problem, but some of
the libraries used by Spring (eg, Hibernate).  Juergen, and others,
did a lot of profiling.  Apparently, the problems were either fixed or
identified as not a native Spring problem.

<rant>
I think it's sad that due to numerous reasons, we can't keep Tomcat
(or any webapp container) up and running over a day's development. 
Imagine if PHP users had to restart Apache after they change their
.php files > 20 times.

Last I checked, there is an 'E' in J2EE that stands for Enterprise. 
One requirement for Enterprise would be to run 24/7.  That means, to
me, to stay running even after redeployments of new versions of
webapps.

I am so surprised that we as Java developers are so silent on this
issue.  We should demand much more loudly for more robust application
servers and deployments.

I'm not pointing fingers, because I know there are many reasons why we
can't just start Tomcat when the machine starts and leave it running.
</rant>

*phew*

Seth


----- Original Message -----
From: Claudio D'Angelo <cla...@ob...>
Date: Mon, 19 Jul 2004 15:38:30 +0200
Subject: Re: [Springframework-developer] CachedIntrospectionResults
To: spr...@li...


I understend.

But how can I save the application server from OutOfMemory or memory
leak?

My first problem is that after 20 redeploy the sever must be
restarted.