2 Replies Latest reply on Sep 17, 2004 3:43 PM by dannyb23

    jboss3.2.5 + jboss-aop

    dannyb23 Newbie

      Hi

      I'm trying to run jboss-aop with jboss-3.2.5 so I have downloaded a clean installation of jboss-3.2.5 and used the instructions found on :http://www.jboss.org/wiki/Wiki.jsp?page=RunningWithJBossApplicationServer

      (
      Please note that one thing was different than the wiki said :

      original : From the jboss-aspects32 distribution you need to copy these libraries to the same directory jboss-aspects.jar

      but i found this jar : jboss-aspect-library.jar in this distribution : jboss-aspect-library-1.0RC1.zip
      )


      After starting jboss up I receive this error :

      18:07:08,185 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
      MBeans waiting for other MBeans:
      ObjectName: jboss.aop:service=AspectManager
      state: CREATED
      I Depend On:
      Depends On Me:
      ObjectName: jboss.aop:service=AspectDeployer
      state: CREATED
      I Depend On:
      Depends On Me:

      MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
      ObjectName: jboss.aop:service=AspectManager
      state: CREATED
      I Depend On:
      Depends On Me:
      ObjectName: jboss.aop:service=AspectDeployer
      state: CREATED
      I Depend On:
      Depends On Me:


      Anybody knows what to do ?

        • 1. Re: jboss3.2.5 + jboss-aop
          Bill Burke Master

          Seems like one of the aspect services failed to deploy. Is there any stack traces in bootup?

          Thanks,

          Bill

          BTW, I have not tested JBoss 3.2 integration with latest RC releases yet.

          • 2. Re: jboss3.2.5 + jboss-aop
            dannyb23 Newbie

            Hi!

            I have just moved the definitions of the mbeans AspectManager and AspectDeployer to the "beggining" of jboss-service.xml (just after classpath tag and jboss starts up fine!!! (i dont think this should have any effect the order of the mbeans but it seems like it has...) but anyway its now fine... (if i move the definitions of the mbeans to the bottom of the jboss-service.xml (just above the closing /server tag then i get this error (there is no stack trace there...)