Removing the legacy-conf-service.xml classpath did not change the
outcome. It looks like to me its the aop deployer that causes the extra
memory, and the gc is thrashing trying to run under the limited memory.
The last log msg before the test times out and shutsdown the server is
this this one:
2008-10-17 14:13:12,755 DEBUG
[org.jboss.aop.asintegration.jboss5.BeansDeploymentAopMetaDataDeployer]
(main) Extracting aop bean metadata factories for
AbstractVFSDeploymentContext@1075311{vfsfile:/Users/svn/JBossHead/jboss-head/build/output/jboss-5.0.0.GA/server/tomcat-webctx/deploy/jbossweb.sar/}
95 seconds later the server is shutdown:
2008-10-17 14:14:47,067 INFO
[org.jboss.bootstrap.microcontainer.ServerImpl] (JBoss Shutdown Hook)
Runtime shutdown hook called, forceHalt: true