Deployment memory footprint

[nedster]

I am currently hot deploying to JBoss via an automated ANT build that runs every hour or so (with JUnit for test validation).

Periodically JBoss throws java.lang.OutOfMemory and I'm not sure if it's because the previously deployed instances of an ear (and associated library jars) are kept because of a previously used classloader. I've looked in the docs but can't find anything about undeployment whilst active, or some way to explicitly gc any classloaders.

Any information/solutions/comments about missing the obvious would be greatly appreciated, thanks in advance.

[schaefera]

Yes, this is a known bug see bug database #482875 on
source forge. It is also a hot topic on the developer mailing list therefore we maybe see a solution soon.

Andy

[hroark]

in which release did this bug get fixed?

[adrian.brock]

JBoss 2.4.4 and JBoss3.0RC1

Regards,
Adrian