3 Replies Latest reply on Apr 22, 2002 8:43 AM by Adrian Brock

    Deployment memory footprint

    sean capes Newbie

      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.