Apologies for talking to myself... ;-)
Regarding Sun bug id 4167874, there is the possibility of turning of caching to avoid the problem. I'll investigate...
--kevan
On 11/8/05, Kevan Miller <[EMAIL PROTECTED]> wrote:
Just a quick update. There is an initial bump in memory usage after the
first d
Just a quick update. There is an initial bump in memory usage after the
first deploy (15 megs -> 19 megs). After 5 deploys, memory growth
levels off at around 20 megs. There is memory growth after that. A
number of Strings, some TimerTasks. However, the most serious problem
is that we're leaking su
Hi Jeff,
Yes, I had, but only for a few deploy/undeploy cycles. I just ran a
more extended test, with much better results. I'm not seeing unbounded
growth in memory. At least not at the rate I reported earlier. I'm
seeing growth of about 500 bytes per deploy/undeploy cycle. I think
there may be an
Have you run a profiler to see where the leaks are occurring?
Matt Hogstrom wrote:
Kevan,
Big thanks for tracking down these issues. I know they aren't easy.
Matt
Kevan Miller wrote:
I've been battling a variety of ClassLoader-based memory leaks that occur
during the deploy/undeploy of DayT
Kevan,
Big thanks for tracking down these issues. I know they aren't easy.
Matt
Kevan Miller wrote:
I've been battling a variety of ClassLoader-based memory leaks that occur
during the deploy/undeploy of DayTrader. With the patches for the following
problems, I no longer see MultiParentClassL
I've been battling a variety of ClassLoader-based memory leaks that
occur during the deploy/undeploy of DayTrader. With the patches for the
following
problems, I no longer see MultiParentClassLoaders being leaked:
http://issues.apache.org/jira/browse/GERONIMO-1125 (patch just posted)
http://issues
