The BeansDeploymentAopMetaDataDeployer takes the beans that result
from aop stuff inside a -beans.xml, i.e.beans resulting from stuff like:
<aspect xmlns="urn:jboss:aop-beans:1.0"
factory="org.jboss.test.microcontainer.beans.SimpleAspectFactory">
</aspect>
<bind xmlns="urn:jboss:aop-beans:1.0" pointcut="execution(*
org.jboss.test.microcontainer.beans.POJO->*(..))">
<advice
aspect="org.jboss.test.microcontainer.beans.SimpleAspectFactory"
name="advice"/>
</bind>
and deploys those into the MC controller as mentioned here
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=142960
. I doubt anything uses this functionality yet, so it should not
really be doing very much
On 17 Oct 2008, at 22:23, Scott Stark wrote:
If you run the config using the run.sh/run.conf default memory
settings this config starts up fine.
Scott Stark wrote:
> 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
>
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development