5 Replies Latest reply on May 29, 2003 11:58 AM by Laurence Smith

    DefaultJMSProvider dependencies problem

    Stephane Nicoll Master

      Hi,

      I have an EAR file containing two JARs. Some of the EJBs there uses JMS. When I start JBoss (3.2.1) and I drop my EAR in the deploy directory, everything runs fine.

      When I restart JBoss with the ear in the deploy directory, I got some fancy error:

      NameNotFoundException: DefaultJMSProvider not bound ...

      I noticed that JBoss tries to deploy my application *BEFORE* JMS. Is there a way to specify somewhere that my application needs JMS and thus it should be deployed first?

      Thanks

      Stephane

        • 1. Re: DefaultJMSProvider dependencies problem
          sys user Master

          I'm having the same problem when I upgraded my app to to 3.2.1 (this worked properly in 3.2.0) ....

          03:32:43,884 ERROR [JMSContainerInvoker] Starting failed
          javax.naming.NameNotFoundException: DefaultJMSProvider not bound
          at org.jnp.server.NamingServer.getBinding(Ljava.lang.String;)Ljavax.nami
          ng.Binding;(NamingServer.java:495)
          at org.jnp.server.NamingServer.getBinding(Ljavax.naming.Name;)Ljavax.nam
          ing.Binding;(NamingServer.java:503)
          at org.jnp.server.NamingServer.getObject(Ljavax.naming.Name;)Ljava.lang.
          Object;(NamingServer.java:509)
          at org.jnp.server.NamingServer.lookup(Ljavax.naming.Name;)Ljava.lang.Obj
          ect;(NamingServer.java:282)
          at org.jnp.interfaces.NamingContext.lookup(Ljavax.naming.Name;)Ljava.lan
          g.Object;(NamingContext.java:492)
          at org.jnp.interfaces.NamingContext.lookup(Ljava.lang.String;)Ljava.lang
          .Object;(NamingContext.java:471)
          at javax.naming.InitialContext.lookup(Ljava.lang.String;)Ljava.lang.Obje
          ct;(InitialContext.java:347)
          at org.jboss.ejb.plugins.jms.JMSContainerInvoker.getJMSProviderAdapter()
          Lorg.jboss.jms.jndi.JMSProviderAdapter;(JMSContainerInvoker.java:805)
          at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerCreate()V(JMSConta
          inerInvoker.java:386)
          at org.jboss.ejb.plugins.jms.JMSContainerInvoker.startService()V(JMSCont
          ainerInvoker.java:579)
          at org.jboss.system.ServiceMBeanSupport.start()V(ServiceMBeanSupport.jav
          a:192)
          at org.jboss.ejb.MessageDrivenContainer.startService()V(MessageDrivenCon
          tainer.java:220)
          at org.jboss.system.ServiceMBeanSupport.start()V(ServiceMBeanSupport.jav
          a:192)
          at COM.jrockit.reflect.NativeMethodInvoker.invoke0(ILjava.lang.Object;[L
          java.lang.Object;)Ljava.lang.Object;(Native Method)
          at COM.jrockit.reflect.NativeMethodInvoker.invoke(Ljava.lang.Object;[Lja
          va.lang.Object;)Ljava.lang.Object;(Unknown Source)
          at COM.jrockit.reflect.VirtualNativeMethodInvoker.invoke(Ljava.lang.Obje
          ct;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source)
          at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;
          I)Ljava.lang.Object;(Unknown Source)
          at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(Ljava.lang.St
          ring;[Ljava.lang.Object;[Ljava.lang.String;)Ljava.lang.Object;(ReflectedMBeanDis
          patcher.java:284)

          Is there something new in 3.2.1 that I have to configure ?

          Trev


          • 2. Re: DefaultJMSProvider dependencies problem
            Adrian Brock Master

            Don't post "me-to", it looks like somebody
            answered the question.

            3.2.1 was shipped with a wrong value in
            server/default/conf/jboss-service.xml

            It should be
            True

            Regards,
            Adrian

            • 3. Re: DefaultJMSProvider dependencies problem
              Laurence Smith Newbie

              Sorry I meant to say we are using 3.2.0, I was reading the same post just prior to writing mine, so I blame that for my lapse...

              The URLDeploymentScanner has no attribute 'RecursiveSearch' in Jboss 3.2.0 this only appears in JBoss 3.2.1. I don't believe it is implemented (though without checking the source...)

              It is not feasible to update the server to the latest version as Im not sure this would solve the problem.

              Some other points that may help are:

              Monday - Worked so 3000+ messages
              Tuesday - message queue failed so no messages
              Wednesday - Worked so 3000+ messages
              Thursday(today) - message queue failed so no messages

              If it works tommorow then I would suggest that it is the persistence manager. As I mentioned between 1:00am and about 5:00am the database connection is down. So lots of messages will fail. The server is rebooted at 5:30 (we had some problems with JBoss 2.4 regaining its connection - so this was introduced too much poilitics to change! It also overcomes NT's need to be rebooted reguarly:).

              Quite obviously there may well be a few hundred failed messages when JBoss starts up. Are these persisted to hsql? Could this be what is causing the persistence manager to fail to load?

              To be honest Im not really bothered about the failed messages as they are not created by any real users.

              So perhaps I can turn off hsql persistence? Or move over to using a differnet persistence manager implementation such as the rolling file one, any suggestions????

              • 4. Re: DefaultJMSProvider dependencies problem
                Laurence Smith Newbie

                Sorry I meant to say we are using 3.2.0, I was reading the same post just prior to writing mine, so I blame that for my lapse...

                The URLDeploymentScanner has no attribute 'RecursiveSearch' in Jboss 3.2.0 this only appears in JBoss 3.2.1. I don't believe it is implemented (though without checking the source...)

                It is not feasible to update the server to the latest version as Im not sure this would solve the problem.

                Some other points that may help are:

                Monday - Worked so 3000+ messages
                Tuesday - message queue failed so no messages
                Wednesday - Worked so 3000+ messages
                Thursday(today) - message queue failed so no messages

                If it works tommorow then I would suggest that it is the persistence manager. As I mentioned between 1:00am and about 5:00am the database connection is down. So lots of messages will fail. The server is rebooted at 5:30 (we had some problems with JBoss 2.4 regaining its connection - so this was introduced too much poilitics to change! It also overcomes NT's need to be rebooted reguarly:).

                Quite obviously there may well be a few hundred failed messages when JBoss starts up. Are these persisted to hsql? Could this be what is causing the persistence manager to fail to load?

                To be honest Im not really bothered about the failed messages as they are not created by any real users.

                So perhaps I can turn off hsql persistence? Or move over to using a differnet persistence manager implementation such as the rolling file one, any suggestions????

                • 5. Re: DefaultJMSProvider dependencies problem
                  Laurence Smith Newbie

                  Sorry I meant to post to this topic:
                  http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t= posted checked the topic it wasn't there, clicked back posted again still not there. Then eventually realised i had clicked on the wrong post message button! So had posted two to this topic, duh!

                  My apoligies, but it has been a long day:)