3 Replies Latest reply on Jul 1, 2003 9:00 AM by juhalindfors

    Delaying JMX: dependencies

    rdb55

      I've used the following keywords:

      delay, dependency

      I've read everything that I came across. I did not find a satisfactory answer. Here is my question:

      I have a .SAR file that contains a JMX service. JBoss tries to deply it before the entity beans it needs are deployed. I've read that renaming the JMX bean to follow the entity jar will help, but I've also read that SARs, are always processed first.

      I want to tell my JMX .SAR file to wait for the entity JAR to deploy before it tries. Is there an explicit way to do this? If not, what are the work arounds (besides renaming). Someone mentioned that by putting the SAR in the EAR with your entity JARs they cured the problem.

      I appreciate your help with this matter.
      RDB

      P.S. - I'm game for a simple shove in the right direction. If there is no direction, please be verbose.

        • 1. Re: Delaying JMX: dependencies

          There are several ways to do this:

          1) add an explicit tag that adds a dependency to the EJB deployment. This ensures your EJB is deployed before your SAR archive. EJB deployments can be found under the jboss.j2ee domain in the JMX kernel -- for instance jboss.j2ee:jndiName=MyJNDIName,service=EJB

          2) Nested deployment packages are deployed in the order innermost first, outermost last

          3) Enable prefixDeploymentSorter in jboss-service.xml and use nnn-mypackage.xar naming convention where is number that indicates the order of deployments.

          • 2. Re: Delaying JMX: dependencies
            rdb55

            Thank you, very much!

            That was the most concise, and completely on the nose, response I've read in a long time.

            My best!
            RDB

            • 3. Re: Delaying JMX: dependencies

              You're welcome ;-)