Garbage collection and unit testing

[jlukar]

Hi ,

I am doing " new TreeCacheAOP()" followed but tree.start() and then after a unit testMethod runs, doing a tree.remove("/") followed by tree.stop().

I do this for every testMethod in my performance benchmarking test case.

This results in major memory consumption and full GC kicking in even when I thrwo a Gig at the test which subsequently results in my benchmark numbers getting thrown off.

Is there a way to ensure TreeCacheAOP gets fully cleaned out after the end of each testMethod invocation.

I would hate to break up my tests and run them in different VM's.

any other suggestions? thanks

[ben.wang]

Are you using putObject and removeObject apis?

-Ben

[jlukar]

Are you using putObject and removeObject apis?

-Ben

Just putObject and cache.remove("/");


I got around this anyways by ensuring that each test case runs in its own VM and in order.

thanks

[ben.wang]

Ok, try to use removeObject() instead of simply remove() as the former will properly disassociate the POJO from the interceptor. This is the proper way to do in pojo cache (TreeCacheAop) anyway.