-
1. Re: Memory not released after undeploy
pmuir Feb 25, 2009 1:56 PM (in response to dallen6)On my box (Mac OSX) the artifacts do undeploy when we call deploymentManager.undeploy() so I don't think it is a problem with the artifacts remaining in the deploy dir to long (you can also verify this by watching the content of the deploy dir and see how many artifacts are there at any one time.
If people want to try to reproduce, it's quite easy as the TCK run is automated. -
2. Re: Memory not released after undeploy
dallen6 Feb 25, 2009 1:56 PM (in response to dallen6)A few other details left out:
The OS is Ubuntu Linux 8.04LTS with kernel version 2.6.24-23.
The JVM is the Sun Java SDK 1.6.0_07-b06. -
3. Re: Memory not released after undeploy
pmuir Feb 25, 2009 1:58 PM (in response to dallen6)See http://seamframework.org/WebBeans/JSR299TCKPortingPackage#H-RIPortingPackage for instructions to run the TCK.
-
4. Re: Memory not released after undeploy
pmuir Feb 25, 2009 2:04 PM (in response to dallen6)NB looks like a heapspace problem - the JVM runs out (with 512m allocated).
-
5. Re: Memory not released after undeploy
starksm64 Feb 25, 2009 2:18 PM (in response to dallen6)We do have some memory leak testing in the jbossas testsuite, but it just takes a little issue to pull in huge objects graphs that are not getting cleaned up across redeployments. I'll create a JBAS issue to look into the tck behavior.
-
6. Re: Memory not released after undeploy
brian.stansberry Feb 25, 2009 2:26 PM (in response to dallen6)Just an FYI, the testing Scott's referring to is described here:
https://www.jboss.org/community/docs/DOC-9294
As noted on the wiki, that testing covers a pretty limited number of basic code paths. -
-
8. Re: Memory not released after undeploy
brian.stansberry Feb 25, 2009 2:30 PM (in response to dallen6)Also FYI there is this known issue that seems to affect the Sun VM:
https://jira.jboss.org/jira/browse/JBAS-5959 -
9. Re: Memory not released after undeploy
pmuir Feb 25, 2009 6:26 PM (in response to dallen6)I'll also double check that I'm not causing the leak (doubtful I think).
In the meantime I will put in a "restart jboss every 50 tests" to test deployment impl for the profile service.
Thanks for the help.