4 Replies Latest reply on Feb 10, 2009 6:38 AM by djr667

    4.2 to 5.0 upgrade: UNRESOLVED Demands 'jboss.ejb:service=EJ

    djr667
    djr667 Feb 10, 2009 5:05 AM

      Upgrading to 5.0.0.GA

      Changed EJB annotation package names etc, added xml:ns to persistance.xml

      Now get

      ** UNRESOLVED Demands 'jboss.ejb:service=EJBTimerService' **


      on all deployed .ear files.

      I have found various comments about ejb-jar.xml needing a definition of some sort, but we do not use that file (we use annotations) and the current setup works fine in 4.2.0

      I have found a
      TODO: the ejb deployer must depend on this
      comment in default\deploy\ejb3-timer-service.xml

      and
      TODO: check depends
      comment on Ejb3ClientDeployer in default\deployers\ejb3.deployer\META-INF\ejb3-deployers-jboss-beans.xml

      does this mean something is incomplete in JBoss 5.0.0.GA ?

      Dave


      • 11918 Views
      • Tags:
        • 1. Re: 4.2 to 5.0 upgrade: UNRESOLVED Demands 'jboss.ejb:servic
          jaikiran
          jaikiran Feb 10, 2009 5:20 AM (in response to djr667)

          jboss.ejb:service=EJBTimerService is deployed through %JBOSS_HOME%/server/< serverName>/deploy/ejb2-timer-service.xml. I would expect this file to be present in the AS. Is this a clean JBoss AS or has it been modified? Any idea if someone removed that file?

            • Actions
          • 2. Re: 4.2 to 5.0 upgrade: UNRESOLVED Demands 'jboss.ejb:servic
            djr667
            djr667 Feb 10, 2009 5:30 AM (in response to djr667)

            Do you mean ejb3-timer-service.xml? - we do not use EJB2

            The service is deployed - but deployed .ear files with no defined dependency on EJB3TimerService fail on it.

            Are there annotations that cause it to be 'sucked in'? Any reason why this would behave differently to JBoss 4.2?

            Dave

              • Actions
            • 3. Re: 4.2 to 5.0 upgrade: UNRESOLVED Demands 'jboss.ejb:servic
              jaikiran
              jaikiran Feb 10, 2009 5:46 AM (in response to djr667)

               

              "drichm" wrote:
              Do you mean ejb3-timer-service.xml? - we do not use EJB2


              Nope, i meant ejb2-timer-service.xml :)

              Currently EJB3 is not using the EJB3TimerService being deployed through ejb3-timer-service.xml.

              "drichm" wrote:

              Are there annotations that cause it to be 'sucked in'?


              Not annotations, but hidden within the code: 
              protected void registerEJBContainer(Container container) throws Exception
 {
 ObjectName on = container.getObjectName();
 String name = on.getCanonicalName();
 DependencyPolicy dependsPolicy = container.getDependencyPolicy();
 dependsPolicy.addDependency("jboss.ejb:service=EJBTimerService");


              To understand what exactly is going on with the deployments, you will have to tell us if you removed the ejb2-timer-service.xml :) And if possible please post the console logs.


                • Actions
              • 4. Re: 4.2 to 5.0 upgrade: UNRESOLVED Demands 'jboss.ejb:servic
                djr667
                djr667 Feb 10, 2009 6:38 AM (in response to djr667)

                No need to post logs

                I had removed ejb2-timer-service.xml

                Put it back, restarted, problem solved

                Thanks
                Dave

                  • Actions