9 Replies Latest reply on Feb 25, 2009 6:26 PM by Pete Muir

    Memory not released after undeploy

    David Allen Newbie

      When using the Web Beans (JSR-299) TCK test harness, many individual WARs and EARs are deployed individually, used, and then subsequently undeployed before the next is deployed. As each deployment is loaded, the amount of memory the JVM uses for JBoss 5.0.0.GA or 5.0.1.GA increases significantly. In the case of this TCK today, the memory usage rises quickly from 360MB after initial startup to over 1.3GB. This is likely to double in the coming weeks as new tests are added.

      The log does show that each of these deployments is eventually being undeployed. For instance, before the next deployment, a DEBUG line like the following appears:

      2009-02-25 00:30:32,015 DEBUG [org.jboss.deployers.plugins.deployers.DeployersImpl] (WorkerThread#0[]) Fully Undeployed vfszip:/home/dallen/JBossServer/jboss-5.0.1.GA/server/default/deploy/org.jboss.jsr299.tck.integration.context.passivating.PassivatingContextTest.war/

      Is there a known problem with not cleaning up after something is undeployed (vfs)? Any way to force the memory to be released?