It's also worth mentioning that for serious application tuning, there
is no substitute for a good profiling tool. In the past I have had
great results with JProfiler:
http://www.ej-technologies.com/products/jprofiler/overview.html
I've even gone so far as to take one node in a production
Adam Allgaier wrote:
I would plug jconsole into your resin instance and watch what's happening to
the JVM memory. Could be loose open threads (and large thread size) that
grows over time and eats up free memory. Restarting would kill all the
threads and free the memory.
From our years using Resin and other containers, even though
basically Resin, we have found basically 2 things that containers do
not like:
.- Swap memory. I know it's stating the obvious, but when your app is
running out of memory and the GC starts working like frenzy, the worst
it can
On Mar 21, 2009, at 14:59, Stargazer wrote:
Adam Allgaier wrote:
I would plug jconsole into your resin instance and watch what's
happening to the JVM memory. Could be loose open threads (and
large thread size) that grows over time and eats up free memory.
Restarting would kill all