Re: [Springframework-developer] CGLIB memory usage within class loader

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

On Tue, 19 Oct 2004 14:05:47 -0400, Rob Rudin <rob...@ur...> wrote:
> Juergen - we found ourselves having the same problem with
> creating contexts per test method, though we weren't using CGLIB
> proxies through Spring. CGLIB was still involved because of
> Hibernate, and we found that the JVM for the integration test
> would run out of memory after about 20-25 tests that each
> created a new context and then did some operations involving
> Hibernate. We ended up extending TestCase and TestSuite so that
> a single context is created and shared among test methods; this
> helped us get around the problem.
> 
> We also get this problem when restarting just the webapp in
> Tomcat. I know this was discussed before, and I thought we
> shouldn't be affected because we only use JDK proxies, but it
> still occurs for us.
> 
> Is there any chance that this will eventually be fixed in CGLIB?
> We can get by with one context for all test methods, but as you
> state, it would be nice for it not to be a problem when each
> test method does need to create its own context.

We also have experienced this problem.  We had to create one single
ApplicationContext for all tests.  Otherwise... BOOM... OOM.

And we still see OOM w/ redeployments in Tomcat.  The more I look into
it, the more it points to a CGLIB problem from Hibernate.  Only when I
include Hibernate into my deployments or somehow use CGLIB do I get
OOM after a few redeployments or test runs.

Seth